Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
RockRabbit:
--- Quote ---We actually have enough now for building a bootloader, so I wouldn't focus too much on this any more. Our bootloader will already have system initializations and hardware setup (kernel_init(), system_init()) that is already nicely implemented for the other AMS targets.
--- End quote ---
I'll wait till someone else is able to do that - its beyond my capabilities (at least at the moment) - and i'll pick up again when its done. I'll be glad to do whatever I can once there is a proper dual boot setup for the c200.
In the meantime i'm building a test bootloader that has subroutines that will flash the button light a set number of times (almost complete) that will enable multiple conditions to be tested in a single pass. It might actually be useful but if not its good practise for me with arm assembler (getting to grip with subroutine linkage and stack handling).
If anyone out there wants me to try something out on my c200, please let me know.
atomikpunk:
Hi peeps,
its been a while, but I finally got some spare time to look back at the OF and investigated the buttons for the e200/fuze/c200 targets. As I previously said, the OF reads those buttons using DBOP. But we are also able to read some using GPIOs. It tickled me for some time but now I got an explanation for this and it is a shame I didn't notice before: some GPIO pins are shared with the DBOP data lines! ;D
This basically means that it "should" be possible to read the buttons using either the GPIO or the DBOP. However, DBOP also controls some control lines which could theorically be wired to devices chip select pins and such. This leads me to recommend using DBOP as in the OF for reading the buttons on those targets. This is only a couple of lines of code really, but it needs to be carefully put together. And as a bonus, maybe using DBOP will correct some of the current LCD/whatever bugs some people see with those targets.
I already sent a (commented) disassembly source to kugel which will look into and probably create a test code with it. If anyone is seriously interested in it, I could also send it through PM, but sadly (for legal reasons), I won't post my disassembly here.
I still read and contribute this thread but I don't have much time these days to write so feel free to comment/write to me if you need more help, I'll be glad to do what I can :)
kugel.:
RockRabbit: I put up http://www.rockbox.org/tracker/task/9679 so that the c200v2 is integrated into the source. Note that most is guess work (which is fine for now), but we need to know the particular memory size.
Please patch your c200v2 with a stock OF named "c200pt.bin", this will hopefully enable the diagnosis mode, in which the memory size is stated.
Play around with my patch, but beware that it is completely untested. It may or may not brick (one of) your c200v2.
It'll at least build a bootloader with loops after doing init stuff.
I've made dualboot.S so that it boots the OF if USB is inserted or RIGHT is pressed. That's based on the information your findings.
atomicpunk: Thanks again!
Hillshum:
Could some folks who have loaded modded firmwares on AMS sansas please see if DRM still works? I seem to have broken my Sansa's DRM support by doing so. If this is really the case, then e200s are not fully recoverable.
RockRabbit:
--- Quote from: kugel. on December 19, 2008, 12:58:15 PM ---RockRabbit: I put up http://www.rockbox.org/tracker/task/9679 so that the c200v2 is integrated into the source. Note that most is guess work (which is fine for now), but we need to know the particular memory size.
Please patch your c200v2 with a stock OF named "c200pt.bin", this will hopefully enable the diagnosis mode, in which the memory size is stated.
Play around with my patch, but beware that it is completely untested. It may or may not brick (one of) your c200v2.
It'll at least build a bootloader with loops after doing init stuff.
I've made dualboot.S so that it boots the OF if USB is inserted or RIGHT is pressed. That's based on the information your findings.
atomicpunk: Thanks again!
--- End quote ---
You'll have to explain further about c200pt.bin. Where do i get it, and where did it come from?
Is there a way I can mod my bootloader code to ascertain how much memory the thing has? I really dont want to risk bricking it at this early stage if possible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version