Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
tobi-lu:
That's what I thought as well...
In the end, we'll HAVE to use things that are in this document, because that's just how the SD communication works, no matter how we find it out.
funman:
Hey guys
Now with the help of the LCD I'm sure that I can issue commands to the SD, but the protocol is still quite confusing to me.
I attach the code I use to power the device and send commands, but without my buggy commands ;)
P.S. I uploaded a nicer HD picture of the lcd
daniel_at:
WOW! Congrats to funman, atomikpunk and all other helpers! This is really great news.
I am just looking at the current GIT-Tree and feeling somehow unsure, how I cleanly get to a rockbox.bin file which i can stuff into the mkamsboot-makefile. Any Hints?
Now as we can print out more informations i would eagerly want to know where the interrupt-vector points, which handles the power-button. Because, if the "power-off" it is software driven, this vector would point to a region which is executed befor the OF (and now our rockboxloader) is executed from flash. Which will be the mask-ROM mentioned in the datasheet. According to the pdf this ROM can be mapped onto 0x00000000, but that seems unreasonable in our case, because here lies RAM which gets loaded with data from flash. So Sansa has maybe modified the Address which the mask-ROM maps to. Or the power-off is hardware driven - then forget about all i wrote :)
Daniel
funman:
--- Quote from: daniel_at on October 07, 2008, 08:10:16 AM ---I am just looking at the current GIT-Tree and feeling somehow unsure, how I cleanly get to a rockbox.bin file which i can stuff into the mkamsboot-makefile. Any Hints?
--- End quote ---
You can use tools/configure and use the Clip target, bootloader only.
But before you should be sure to disable the lcd driver, because it is specific to the Clip: I don't think it will work on the E200.
--- Quote from: daniel_at on October 07, 2008, 08:10:16 AM ---Now as we can print out more informations i would eagerly want to know where the interrupt-vector points, which handles the power-button. Because, if the "power-off" it is software driven, this vector would point to a region which is executed befor the OF (and now our rockboxloader) is executed from flash. Which will be the mask-ROM mentioned in the datasheet. According to the pdf this ROM can be mapped onto 0x00000000, but that seems unreasonable in our case, because here lies RAM which gets loaded with data from flash. So Sansa has maybe modified the Address which the mask-ROM maps to. Or the power-off is hardware driven - then forget about all i wrote :)
Daniel
--- End quote ---
I think the power-off is software driven, because on the Clip I see a logo animation before it shutdown.
You can access the ROM at 0x80000000 (it is an alias) but I think it's useless because before being able to dump its content we need flash driver :/
Also I looked at the NAND / SD registers, because I supposed the ROM bootloader would leave them initialized, but they are reset to 0 .. so nothing useful here.
The LCD controller for the Clip is very similar if not identical to controllers for other rockbox targets, and it may be the same for the E200: check the controller model on the wiki page for E200 port
atomikpunk:
Hi,
--- Quote from: funman ---The LCD controller for the Clip is very similar if not identical to controllers for other rockbox targets, and it may be the same for the E200: check the controller model on the wiki page for E200 port
--- End quote ---
Hmm I really doubt it, if I remember correctly, the display controller on the e200 serie is an ILI-something. Anyway, it is a color display so it wouldn't work with the SSD1303 ;)
--- Quote from: funman ---I think the power-off is software driven, because on the Clip I see a logo animation before it shutdown.
--- End quote ---
Oh that's some news, I didn't noticed. Though I think there is an hardware "recovery" power-off if you hold the power button long enough (about 4-5 seconds). I often used it with infinite loops broken test firmware ;)
Gitorious is back, yay! (See ya later peeps)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version