Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
RockRabbit:
--- Quote from: funman on December 09, 2008, 05:54:59 AM ---Hello, some time has elapsed without updates, so I'll give you the status on the SansaV2:
* KEYMAP : The e200v2 uses the same keymap than e200v1, but other models will need reflexion on a good keymap to use. Note : this is a point where non programmers can help too
--- End quote ---
I might be able to help, provided I am given clear instructions what to do. I have been able to compile Rockbox, and am running it on a c250 version 1 (its great by the way - though of course you all know that already). I have a version 2 I might be willing to risk, providing I don't have to guess my way thru any of it.
I am willing to bet the player on the fact that the keymap is more or less the same as the e200 (excepting the wheel?). Perhaps someone can supply code that specifies the most obvious button that will be the same (the menu button ?).
funman:
@ hillshum : I don't know exactly since I don't own such a device, but I record the reported size was a bit less than 1000000000 (so less than 1GB AND 1GiB)
@RockRabbit : you must first revert utils/AMS/hacking to revision 18663 to get the old basic mkamsboot (which inserts a delay)
Then if you are not familiar with assembly, you should come on the IRC channel and see if someone (like me if i'm present) can give you the steps
Llorean:
Alright, finally got my Clip. I'm looking at the keymap now, and I'll probably post two patches later (in the next few days) one "low-controversy" one where I try to fix the real problems, and a more controversial one where I try to make available the full functionality of Rockbox while still being what *I* consider usable (which may not be the same for everyone).
Alongside that, I'll try to look at the m200v4's keymap as well. I suspect though that it should just have the same keymap as the c200 in 95% of cases since the Recording button isn't often used, I think.
As a note, sound doesn't seem to be working again. At least, when I attempt to play something, it says at 0:00 on the Clip, and doesn't progress, this is with r19386
funman:
--- Quote from: Llorean on December 10, 2008, 06:19:55 PM ---Alright, finally got my Clip. I'm looking at the keymap now, and I'll probably post two patches later
--- End quote ---
Nice!
--- Quote from: Llorean on December 10, 2008, 06:19:55 PM ---As a note, sound doesn't seem to be working again. At least, when I attempt to play something, it says at 0:00 on the Clip, and doesn't progress, this is with r19386
--- End quote ---
Playback is quite buggy on the Clip/m200v4; you should try to apply FS#9332 (flash buffering) which gives better results.
Without it rockbox crashes because of corrupted data (we suspect that buffering.c has some overflows since replacing this file gives better results; but we are not sure yet)
You can also try FS#9611 which is FM radio support (The FM output is directly mixed on the headphones output, so it doesn't use the pcm driver)
smdas:
I just got a brand new AMS Sansa e260 in the mail today. I've done a bit cross-arch embedded before, and I'd like to see that RB boot screen come up on my Sansa...
I've got a small amount of RB experience as a user, in that I own a fourth-generation ipod that was given to me (which was broken, and I fixed). I've been using RB on that for a bit over two years, but that port is prone to frequent lock-up/crashes, which is super annoying. I was inclined to help there, but I really don't like the Apple hardware that much, so, I went and bought a Sansa, but it's the second-gen AMS-based hardware... so I figured that I aught to finally give back.
I have a bit of firmware experience bringing up audio hardware (bootloader work, initialization & driving of DACs/ADCs, loading DSPs but not coding them, etc), and working with various busses. Is there any work in those areas that I could help with? I don't have a micro sd/sdhc card, so probably not there. Perhaps I2C to the buttons? I dunno ???
At any rate, my question is, has anyone had any further progress with rescuing bricked non-e200's, JTAG or otherwise? If I kill my Sansa then that will basically end my ability to help develop in a hurry. If there is a (reasonably) safe way to contribute to the firmware, then I'd love to do so.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version