Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
funman:
Hello !
I was accepted into the committers, and I have committed the SDRAM code in rockbox SVN.
Next step: commit the SD driver embryo so people who hadn't noticed our git tree yet can look at it.
Once it's done, everything will be in SVN and there will be no need to commit code in the git repository.
If you want to work on the SVN tree just ask the developers or send me your patches!
By the way you can work on the rockbox SVN from a git-svn repository, there are instructions in the wiki on how to do so.
ChiefAlex:
hi together.
I own a Sandisk Fuze and e260 (V1, with rockbox running on it) .
I would love to see Rockbox on the Fuze as well. If i can help you with my player (but without risk to "kill" it) let me know it. :)
(edit: i'm german, so any commands in simply english)
kugel.:
Hey, I'd gladly accept help on creating a feedback mechanism for testing on the Fuze.
As of now, neither LCD nor button light nor backlight works (i.e. no visual response at all). Buttons are unknown too. The only feedback mechanism is the 5s delay loop which tends to be annoying and time intensive to work with.
Anyone with greater experience in OF disassembling than me have a look at the Fuze OF and help me getting at least the button light to work; of course LCD would be nice too :)
I've really not enough time to spend much time on the port (which means I cannot really catch up to your knowledge at this time), so I'd really need help to get the Fuze further.
saratoga: How's your JTAG going? Did you already receive the correct hardware (the first one you got was too big IIRC).
linuxstb:
There are still things that people not involved with the low-level hacking can do to help the ports along:
1) Add the Fuze (and c200v2) to the build system. This would just be a matter of copy/paste of the existing code for targets already in SVN (clip, e200v2, m200v2).
2) Start work on all the UI simulators for these targets.
The UI sims will all need a photo/scan of the externals of the device (resized so that the area of the LCD is the real LCD's resolution) for use as the background image (or possibly just copied from the V1 targets, where applicable).
The e200v2 sim should be the easiest to get working, as this uses the same keypad definition as the e200v1. Other targets may need keymaps defining for the Rockbox apps/ code, plus all the plugins.
Making the UI simulators work means doing the majority of the work needed in getting the main Rockbox code working (after the low-level drivers).
Patches welcome (on Flyspray)...
ChiefAlex:
Fuze could use the same keypad because buttons and wheel are the same just "menu" button is top right (botton left on e200).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version