Rockbox Development > New Ports
Sandisk C100 series
shotofadds:
Marc,
On other Telechips devices, uploading a firmware file (.bin) using tcctool just runs that firmware from RAM, so nothing is flashed to the device. It should be safe to 'preview' firmware updates in this way.
I can't have a look at that service program right now, as .ru domains are blocked here (but I suspect it's the same FWDN program that has cropped up elsewhere).
MarcGuay:
Howdy,
So I successfully uploaded v2.0.008A using tcctool and it ran fine, then I rebooted back into v2.0.007A. I tried the same procedure using v1.0.005a and first it tried to connect in MTP mode (presumably the default setting), then upon unplugging I was presented with a firmware interface without strings. All of the images displayed fine, but no words were present in the menus, etc. I read about this on one of the many forums I scanned today, so they must have changed something between the v1 and v2 versions that doesn't gel well when you switch versions. Anyway, this is probably unrelated to porting.
As for the FWDN program, shotofadds, I think you're right, it's the same program that's been around for a bit. I'm going to see if it can be used to extract the Production Test Mode code from the player, though I have no idea even where to begin. I've got some reading about memory to do. Update: The production test mode strings exist in the player.rom file so presumably the code lives there as well.
Oh, and I also read that, at least with the v2 firmwares, they made it possible to perform a firmware upgrade simply by placing the "player.rom" file in the root directory in MSC mode and unplugging the unit, but have yet to try it myself because I want to see if I can preserve the 2.0.007A firmware I have on there first. Update: I found the string "UPDATE F/W?" in the .rom file and figured it was safe to try this update method, and indeed, placing a player.rom file in the root and rebooting is a method of loading code to the device. Again, no idea how if this is relevent to porting.
As for the LCD, I've disassembled the firmware in the same fashion that tarsius had and can't really make heads or tails of it, but will skim through it and see if I can find anything.
shotofadds:
--- Quote from: MarcGuay on May 08, 2008, 08:33:46 PM ---Oh, and I also read that, at least with the v2 firmwares, they made it possible to perform a firmware upgrade simply by placing the "player.rom" file in the root directory in MSC mode and unplugging the unit, but have yet to try it myself because I want to see if I can preserve the 2.0.007A firmware I have on there first. Update: I found the string "UPDATE F/W?" in the .rom file and figured it was safe to try this update method, and indeed, placing a player.rom file in the root and rebooting is a method of loading code to the device. Again, no idea how if this is relevent to porting.
--- End quote ---
Ok, looks like you can upgrade the firmware in the same way as other Telechips players. On the D2 we use this to flash a patched version of the original firmware, which is used to dual-boot with the Rockbox bootloader. But, during initial development there's no need to flash anything and tcctool should be sufficient.
Given that most of the C100 hardware looks pretty much identical to the M200 (v1), the most important thing now is to identify the LCD model and try to write a driver for it. Good luck!
MarcGuay:
This is the only marking I could find on the LCD in the scans. I searched for every possible combination of letters & numbers it could be and came up empty, but maybe someone else has a clue. It's on the bottom of the LCD in the "flipped away" scan in the wiki.
B@SS:
If this help
On the front of screen
GPM580B0 0603
A-NB650218.50.N1 -1
Mark on the plastic thing around the screen
EV-BL-0130
65-04535
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version