Rockbox Development > New Ports
Sansa Fuze+
Molot:
I want to buy Fuze+. But I will do that only if one of the following is meet:
1) Rockbox will be available quite soon, at least in an unstable version.
2) There will be any way for me to contribute to making rockbox available.
Sadly, I hardly know anything about microcontrollers. I can debug, can write in C, can test. Can learn coding. Can try to buy particular subversion of the device.
So should I buy it?
[Saint]:
At this stage I probably still wouldn't buy a Fuze+ in the hope that Rockbox might one day be available for it.
No one can, or ever will, give a projected release time as there are just too many variables.
It could look promising today, and tomorrow a roadblock could be found that completely stalls development.
Also, what is your definition of "quite soon"?
Quite soon, relative to some other ports starting to unstable, could easily be a year or more.
[St.]
Molot:
I was not expecting any promises. Sometimes a project needs just few minor tricks to get basic functionality - I only wanted to know if it's the case. But I really do not expect it is (sorry if I sounded like I was - language barrier, it seems), so there was point 2 - is this work at a point I might be in any way useful? Or get useful in a month or two?
pamaury:
From now on it's hard to tell. LCD is working which is good point, USB can easily made to work, the physical keys work. The storage code is standard SD and the on-disk layout is documented so normally it shouldn't be difficult to get it work. The unknowns are still:
* Touch pad: I've started to reverse engineer what I think is the touch pad code but I have no doc and I'm really not sure that it follows the synaptics MEP protocol. Looking at the synpatics website, there build lots of custom modules so this module might even be specific to the Fuze+ !
* Sound: although the SoC includes a DAC and ADC, there might be some technical details so we'll seeThe sad point is that I will not have too much free time starting from mid-may until the beginning of June (except for DevCon), after that I'll have much more time I hope.
pamaury:
I have some news regarding the touchpad code. I think it uses the RMI protocol from Synpatics. On there website one can find two specification: http://www.synaptics.com/developers/manuals
But on the internet there is another difference PDF ! I still can't tell what is the difference (probably more device types). I'll try to write some code to read the interesting registers.
EDIT:
I made some tests and it's indeed a RMI device. It reports itself as "1533", RMI version 0.1 but rmi specification 3 matches.
It has one function: 2-D TouchPad sensor (0x10) with 3 sensors. It's quite late so I did not dumped all the registers yet to see its capabilities.
A funny fact: the fuze+ OF has both a software and hardware implementation of i2c but it uses the software one with the hardware pins! I don't exactly know why but I myself used the generic rockbox i2c software implementation since it's not worth using the hardware in this case.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version