AMX files not detected

[davidovv]

I installed application (PAWN_008.HEX) successfully, rebooted, started the application with fourth button pressed while booting. The application list was empty. I copied some of amx files downloaded from here, but the applications were not detected neither after button reset, nor after reboot, nor after file rename (to upper case) the application list was still empty. My DS203 is Hardware V2.72 SYS V1.60 Can you help me with this issue?

[PetteriAimonen]

When you connect the DS203 to computer, does it show up as 8MB or 2MB disc? The 8MB version is an unofficial clone and it is not currently supported. I've been working on support with some helpful people, but I do not have the hardware so it's a bit difficult.

[davidovv]

It is 8MB version, Since I have the device can I help? With few guidelines i could build/debug on this device.

[PetteriAimonen]

Would you object to opening the device and see if you can get the type of the flash chip? Probably a SMD chip with 8 legs. A bunch of photos of the 8MB device would be very welcome, both the case and the insides.

[PetteriAimonen]

Please try this one: http://kapsi.fi/~jpa/stuff/other/PAWN_8M.HEX

[davidovv]

chips with 8 legs (two lines for single chip) OACI 28XD (two on board) 5239B 20B (one on board) i will try new hex

[davidovv]

do you need more reading from board?

[PetteriAimonen]

photos would be nice if possible

[davidovv]

https://www.dropbox.com/sh/uw4prca2dqqew95/VO7VlBszrH

[davidovv]

hard to read chips without magnifying glass

http://kapsi.fi/~jpa/stuff/other/PAWN_8M.HEX doesn't read amx files also

[PetteriAimonen]

thanks

[davidovv]

it probably doesn't matter but (on windows) 8MB drive gets mounted by name DSO in your video tutorial the name of drive is DSO QUAD

[davidovv]

do you need "eye" reading from board, so i can close and solder back the device?

[davidovv]

missed one (bigger) 8legs chip winbond 25q64bvsig 1215

[PetteriAimonen]

thanks, that 25q64 is the flash chip actually

no more needed from the board, you can close it.

please try this one to get some debug info, it should stop when booting to quadpawn and show some red text: http://kapsi.fi/~jpa/stuff/other/ALT_8M.HEX

[davidovv]

alter bios 0.3: fatfs fail dfu ver 0x080031d0 dfu ver 0x56332e31 disk init ver 0x00000138 dev info 0x00384d42 flash type 0x00000001 read 0x00000001

[PetteriAimonen]

nothing else?

[davidovv]

updated again

[PetteriAimonen]

ok, another try: http://kapsi.fi/~jpa/stuff/other/ALT_8M_2.HEX

[davidovv]

fmount 0x00000000 ... same as previous ... fopendir 0x0000000d

[PetteriAimonen]

do you have linux available?

[davidovv]

yes, ubuntu 12.04 64bit

[davidovv]

sorry, wrong click (what is with me today)

[PetteriAimonen]

Boot the device normally (to default APP) and take a dump of the flash like this:

1) Find out the name of the device (usually /dev/sdc or similar), for example from "dmesg" output 2) Run this command: sudo dd if=/dev/sdc of=flash.bin
3) Post the flash.bin somewhere.

[PetteriAimonen]

Also, try this to get more debug data on the read:

http://kapsi.fi/~jpa/stuff/other/ALT_8M_3.HEX

[davidovv]

sudo fdisk -l /dev/sdd Note: sector size is 4096 (not 512)

Disk /dev/sdd: 8 MB, 8388608 bytes 1 heads, 16 sectors/track, 128 cylinders, total 2048 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x6f20736b

This doesn't look like a partition table Probably you selected the wrong device.

Device Boot Start End Blocks Id System /dev/sdd1 ? 778135908 1919645538 271071228 72 Unknown /dev/sdd2 ? 168689522 2104717761 3449145664 65 Novell Netware 386 /dev/sdd3 ? 1869881465 3805909656 3449145472 79 Unknown /dev/sdd4 ? 0 3637226495 1664004096 d Unknown

Partition table entries are not in disk order //--------------------------------------------------------------------- file 8M.dd 8M.dd: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", Bytes/sector 4096, root entries 512, sectors 2048 (volumes <=32 MB) , Media descriptor 0xf8, sectors/FAT 1, heads 1, serial number 0xfc1226bb, unlabeled, FAT (12 bit)

//--------------------------------------------------------------------- 8M.dd disk dump https://www.dropbox.com/sh/1e3ygouh0mbatv6/T1OQn1F7yi

[davidovv]

more debug info ... ... read result1 0x14c36fb2 read result2 0xaa55ffff read result3 0xffffffff fopendir 0x0000000d

[PetteriAimonen]

Ok, getting closer.

http://kapsi.fi/~jpa/stuff/other/ALT_8M_4.HEX

[davidovv]

... signature 0x000014c3 read 0x00000001 read result1 0xeb3c904d read result2 0x55aa0000 read result3 0x00000000 fopendir 0x00000000 success 0x00000000

[PetteriAimonen]

Ok, looks good now.

This one is without debug, hopefully the .amx files show up now: http://kapsi.fi/~jpa/stuff/other/ALT_8M_5.HEX

If reading work, try to save something from a e.g. frequency response to see if file writing works also.

[davidovv]

this one didn't return .RDY file it seems to work...

[PetteriAimonen]

yeah, the .RDY was missing for me also.. bootloader acting up or something.

So file saving works also?

[davidovv]

how can i try file saving?

[PetteriAimonen]

Load for example: https://github.com/PetteriAimonen/QuadPawn/wiki/Frequency-Response

save a BMP screenshot and see if it opens correctly.

[davidovv]

to see the file i need to disconnect, connect DSO saving works

[PetteriAimonen]

Yeah it is normal that you need to reconnect; the PC caches the filesystem contents and there is no way for the USB device to tell that the data has changed.

Great that it works, thanks for your help. I'll bundle up a real release some day soon.

[davidovv]

thank you also, glad that i could "contribute"