Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
RockRabbit:
Thanks kugel.
I have mapped the MicroSD present pin -> A2 (high), and the USB present pin -> A1 (low). I have write access to the twiki so I will update the hardware mappings myself tomorrow, but you can do it if you want to.
I have run tests now against almost all the pins (all but two). The only button I can detect apart from the power button is the right button which is detectable on pin C6. It looks to me like this model might have the row/column scanning structure like the clip and the m200. I am guessing that perhaps the right button is detected because of default values on the row driver pins. I note that the button mappings are the same for the clip and m200. The ports are different but the row/column arrangement is the same. If so that might mean that the input pins are C5 thru C7, with the right button showing on C6, the middle pin, as with the clip and m200. But this is pure speculation.
Any suggestions about what to do next will be greatly appreciated. I would very much like to be able to disassemble the OF, but arm-elf-objdump objects to the format of the OF bin file. Any ideas?
thanks ;)
kugel.:
Great news!
What to do next? Integrate the c200v2 into the Rockbox tree, so that we can use bootloaders, which are save and where we can use C code.
It could well be that it's using a keyscan matrix. But it could also be direct connections. Note that e200v2/Fuze also have Right on C6.
Oh, and we should bug linuxstb to edit mkamsboot to support c200v2.
gabe565:
Kugel: Are you sure that the Fuze and the e200v2's right keys are on C6? On the hardware mappings page, it says down is C6 and right is C5. I also have write permissions to the Twiki, so I can update it if you want!
kugel.:
Not anymore :) I just misread sorry.
RockRabbit:
--- Quote from: kugel. on December 18, 2008, 07:46:53 AM ---Great news!
What to do next? Integrate the c200v2 into the Rockbox tree, so that we can use bootloaders, which are save and where we can use C code.
It could well be that it's using a keyscan matrix. But it could also be direct connections. Note that e200v2/Fuze also have Right on C6.
Oh, and we should bug linuxstb to edit mkamsboot to support c200v2.
--- End quote ---
Can you tell me where the experimental Rockbox code is? Or is it simply the latest version in trunk?
I might like to attempt this for the fun of it, even if my code is not used. However is there a proper way to do this, e.g. is there someone who is delegated to do this kind of thing?
I have a copy of the current version of mkamsboot, and it looks fairly straightforward (peels of laughter sound from around the world) to add some c200 code to detect the USB cable. Presumably I could mod that and test it even without anything else rockboxy being on the player.
One last question - is it possible that the other buttons are hooked up to GPIOC and I simply stuffed up the code when I was looking for them? Or in other words, is there a possibility that some other setting is interacting with the port that stopped the other pins working?
One even laster quesrion - Is it possible to dissassemble the OF (C200PA.BIN) using arm-elf-objdump?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version