Rockbox Development > New Ports
Sandisk Sansa View
midgey:
Just to add to that, I recently bought a View and can confirm that the OF will take our firmware and the bootloader will indeed attempt to load it. I compiled the e200 bootloader and resigned it with the dummy key then encrypted it with the View key. After the Sansa logo, the LCD will go white then purple and fade to black. This suggests that nothing is controller the LCD and our code is running.
I'll poke around with the bootloader and disassemble it over the next week. No promises because I know very little about disassembling and other projects have priority.
zman977:
ok ill see what i can help out with. This will be a little of a learning experience for me so...
hey by the way i wonder how close the fuse is with the view? ive read that a few people tryed the e200 boot loader just to try it on the view and could get some where with it and i wonder if the v2 and fuse have any thing similar with the view. if the devs have a boot loader out yet for the fuse that is.
edit**
never mind they dont lol it was a thought though
saratoga:
--- Quote from: zman977 on February 20, 2009, 04:01:49 PM ---hey by the way i wonder how close the fuse is with the view?
--- End quote ---
Theres basically nothing in common except the DAC. The View is based on an updated PP chip, the Fuze an AMS chip.
--- Quote from: zman977 on February 20, 2009, 04:01:49 PM ---if the devs have a boot loader out yet for the fuse that is.
edit**
never mind they dont lol it was a thought though
--- End quote ---
There is a bootloader out there for the Fuze, but since the Fuze has essentially nothing in common, you might as well expect an Ipod or Cowan bootloader to work.
obo:
I recently got a "broken" View from ebay, which just needed recovery. I've added documentation to the wiki describing the hidden partition layout - there are a few differences from the e200. The firmware section starts with the magic "CPUI" followed by 0x60000 instead of "PPMI" followed by 0x20000. If enough progress is made, Sansapatcher will need changing to cope with this (plus a little re-arrangement to allow for a third type of mi4 Sansa).
I'm struggling trying to run custom code on the View (a modified e200 bootloader)
I can modify an existing firmware file (editing plain.bin in this case):
--- Code: ---mv firmware.mi4 firmware.orig.mi4
./mi4code decrypt -s firmware.orig.mi4 plain.bin
./mi4code build plain.bin plain.mi4
./mi4code encrypt plain.mi4 plain.enc.mi4 view
./mi4code sign plain.enc.mi4 firmware.mi4
--- End code ---
but doing something similar with bootloader.bin:
--- Code: ---./mi4code build bootloader.bin bootloader.plain.mi4
./mi4code encrypt bootloader.plain.mi4 bootloader.enc.mi4 view
./mi4code sign bootloader.enc.mi4 firmware.mi4
--- End code ---
fails, the recovery screen displays "Bad File copied" as it loads the files from the 16Mb RAM disc. Does anyone have any ideas what I am missing?
j8048188:
was the new checksum calculated correctly and inserted into the file?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version