Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
fragilematter:
I restored the sansa (worked perfectly), then patched mkamsboot and tested. This is the output:
--- Code: ---gcc -o amsinfo -W -Wall amsinfo.c
gcc -o mkamsboot -W -Wall mkamsboot.c
arm-elf-as -o test.o test.S
test.S: Assembler messages:
test.S:0: Warning: end of file not at end of a line; newline inserted
arm-elf-ld -e 0 -o test.elf test.o
arm-elf-objcopy -O binary test.elf test.bin
./mkamsboot e200pF.bin test.bin patched.bin
Original firmware size - 0x0001d81c
Padded firmware size - 0x0001da00
New firmware size - 0x00020000
Bootloader size - 0x00000074
New padded size - 0x00020000
Calling memmove(buf + 0x00020400,buf + 0x0001de00,0x00edfc00)
original firmware entry point: 0x00000128
New entry point: 0x0001d820
--- End code ---
The firmware starts OK, our code works, but I can't see any text. Maybe the string addresses are hardcoded. I'll drop some screenshots on http://drop.io/sansahack as soon as i copy them from the camera.
Edit: after playing one song there probably was a write at a wrong address on the nand, because now I get corrupted graphics on the boot logo and then it locks up. After a few more starts and forced shutdowns it just lights the leds and the display illumination...
sucitrams:
@fragilematter:
Thats my problem too. I think we can forget it. :(
EDIT: Now if I read out my NAND wit dd, dd stops at 14MB because of "readout errors". But I opened the firmware that was on the flash with a hex editor.
From 00000000 - 004FFEC7 everything is "00". But then the firmware begins.
I think my NAND is damaged, because many times I tried to delete the corrupted Firmware, /dev/zero, but its still there.
fragilematter:
Okay, I tried to restore it with the small image and it was writing everything correctly, but after unplugging and connecting it back to the usb it went into the recovery mode again. So I dd-ed the big (119MB) image I dumped the first time, and that solved the problem.
I think it wasn't booting because the fat was probably damaged, but I can't test my theory because I didn't think of making a dump of the bad firmware from the nand. And I wouldn't like to brick it again just to test that theory.
Guys, anytime you've got something else to test, I'm (and my sansa) still up for the job.
Sucitrams: I don't know what happened exactly to your e200, but I managed to restore mine 3 times by now, and I didn't encounter any write errors in the recovery mode. Don't try to zero the nand, I don't think that would be a very wise idea. Try to get to a usb 1.1 machine and dd the big image nicely. I'll look for a place to upload it and give you the link in a pm. I hope you'll be able to restore it :)
andva:
--- Quote from: fragilematter on September 03, 2008, 07:47:00 AM ---Try to get to a usb 1.1 machine and dd the big image nicely.
--- End quote ---
For the record, you can force Linux to use all devices in USB 1.1 mode by rmmod'ing the ehci-hcd module, so there is no need to hunt for an ancient machine.
Great job, guys!
gevaerts:
--- Quote from: andva on September 03, 2008, 08:04:10 AM ---For the record, you can force Linux to use all devices in USB 1.1 mode by rmmod'ing the ehci-hcd module, so there is no need to hunt for an ancient machine.
--- End quote ---
You can do something similar on windows : disable the EHCI controller(s) in the device manager
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version