Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
Finixlives:
(Fuze V2)
Well i got home from school today to be delightfully surprised that memory is no longer read only :D
I've done very very little testing (only the rockboy plugin) and i can save games on the game, but not with the save state. Another thing to note is that when i shut down rockbox and then turn it back on the save is erased. Ill be testing more things out and give more feed back later.
PS: Thanks for the great work you Developers are doing!
bilditup1:
So I tried the official build of 25799, as well as a few of my own changing the udelay params in sd-as3525v2.c.
The official build (which I'm assuming has udelay at 1000) hangs forever at boot with an 8gb uSDHC. The same behavior occurs with every build I've made, including sleep(1), udelay (5000), and udelay(3750) which all worked with the earlier revision 25791. These builds also failed to recognize the card on insertion after startup, except for (3750). However, this support was very glitchy - flashing click wheel, slow loading of next folder (like a .5-1.0 sec delay), freezes on trying to access, etc. This only happened once - when I tried to put this build back on (25799/3750), I could not replicate results (other than the hang at startup). So I reverted back to 25791/5000 for now, which seems the most stable.
What is there to be done...?
Jennifur:
Using a FuzeV2 with an 8GB Kingston Class 4 uSD card. It freezes with the build r25799-100503 when the uSD card is inserted. It will not detect the uSD after it is inserted while Rockbox is running. The builds with read only support will not see the uSD card either. The OF can read/write to both the internal memory and uSD. The previous version that I used was r25758-100429 from SVN.
bilditup1:
Yeah jennifur - the last ready-made build this works with is 25733. If you modify the file I wrote about above (funman/kugel's suggestion) and make your own build, you could work with 25791. (I'm also using an 8gb Kingston Class-4). Read the thread in the middle of the last page for more info.
Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?
-e
saratoga:
--- Quote from: bilditup1 on May 03, 2010, 09:22:28 PM ---Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?
--- End quote ---
'M' = 'modified'
Just means you edited the source code.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version