New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMX files not detected #11

Closed
davidovv opened this Issue Oct 12, 2013 · 36 comments

Comments

Projects
None yet
2 participants
@davidovv

davidovv commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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.

Owner

PetteriAimonen commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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.

Owner

PetteriAimonen commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen
Owner

PetteriAimonen commented Oct 12, 2013

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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 commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

do you need more reading from board?

davidovv commented Oct 12, 2013

do you need more reading from board?

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

photos would be nice if possible

Owner

PetteriAimonen commented Oct 12, 2013

photos would be nice if possible

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

hard to read chips without magnifying glass

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

davidovv commented Oct 12, 2013

hard to read chips without magnifying glass

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen
Owner

PetteriAimonen commented Oct 12, 2013

thanks

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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 commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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

Owner

PetteriAimonen commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

nothing else?

Owner

PetteriAimonen commented Oct 12, 2013

nothing else?

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

updated again

davidovv commented Oct 12, 2013

updated again

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen
Owner

PetteriAimonen commented Oct 12, 2013

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

do you have linux available?

Owner

PetteriAimonen commented Oct 12, 2013

do you have linux available?

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

yes, ubuntu 12.04 64bit

davidovv commented Oct 12, 2013

yes, ubuntu 12.04 64bit

@davidovv davidovv closed this Oct 12, 2013

@davidovv davidovv reopened this Oct 12, 2013

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

sorry, wrong click (what is with me today)

davidovv commented Oct 12, 2013

sorry, wrong click (what is with me today)

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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.
Owner

PetteriAimonen commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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

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

Owner

PetteriAimonen commented Oct 12, 2013

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

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

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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 commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen
Owner

PetteriAimonen commented Oct 12, 2013

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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.

Owner

PetteriAimonen commented Oct 12, 2013

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 comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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

So file saving works also?

Owner

PetteriAimonen commented Oct 12, 2013

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

So file saving works also?

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

how can i try file saving?

davidovv commented Oct 12, 2013

how can i try file saving?

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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

save a BMP screenshot and see if it opens correctly.

Owner

PetteriAimonen commented Oct 12, 2013

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

save a BMP screenshot and see if it opens correctly.

@davidovv

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

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

davidovv commented Oct 12, 2013

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

@PetteriAimonen

This comment has been minimized.

Show comment
Hide comment
@PetteriAimonen

PetteriAimonen Oct 12, 2013

Owner

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.

Owner

PetteriAimonen commented Oct 12, 2013

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

This comment has been minimized.

Show comment
Hide comment
@davidovv

davidovv Oct 12, 2013

thank you also,
glad that i could "contribute"

davidovv commented Oct 12, 2013

thank you also,
glad that i could "contribute"

@davidovv davidovv closed this Oct 12, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment