SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

[porio]

Yes, please update the bootloader before reporting problems with booting.

Thanks! Should I compile it from source or there is another way to get it?
(as I told before, my first attempt at compiling was unsuccessful, though I can try again...)

EDIT: I just compiled the bootloader from source version 21610. My Clip freezes at boot. Also, it can't boot to OF unless I plug it to the computer. May I have done something wrong?

UPDATE: My bootloader from version 21610 is working, just the dualboot is wrong (I must have done something wrong, I will try to read again the documentation but any help will be apreciated).
As for Rockbox itself, version 21506 runs fine but 21610 does not. After the boot screen, it goes black and the only way to get out of it is holding up the power switch for 10-15 seconds.

[Hillshum]

UPDATE: My bootloader from version 21610 is working, just the dualboot is wrong (I must have done something wrong, I will try to read again the documentation but any help will be apreciated).
As for Rockbox itself, version 21506 runs fine but 21610 does not. After the boot screen, it goes black and the only way to get out of it is holding up the power switch for 10-15 seconds.

The next step is to narrow down which specific revision it was that broke it. Figure it out by trying the revision halfway between 21506 and 21610, then if it works, try a revision halfway between that and 21610...

Hold down the left/prev button when turning it on to get the OF

[funman]

BTW, the playback crashes happen more on higher bitrates.

The bug seems to be related to small buffer size, like when at some time the buffer needs to be filled but there is not enough room available.

This will happen on Clip/m200v4 and c200v2 because they only have 2MB of RAM.

[porio]

The next step is to narrow down which specific revision it was that broke it. Figure it out by trying the revision halfway between 21506 and 21610, then if it works, try a revision halfway between that and 21610...

Build 21572 gets past the bootloader and works fine; builds 21583-21610 don't. I don't know how to get revisions between daily builds, but I don't think it's necessary because there was only one change for the Sansas that day.

Maybe the fix for FS#10344 didn't work for me?

Hold down the left/prev button when turning it on to get the OF

Yes, I didn't notice that the button had changed and was stubbornly doing it with the home button!!

[Messerjocke]

I've build and installed a fresh SVN checkout (r21619) on my E260 / 4GB SDHC; and for me everything seems to work stable and snappy. Even video playback.. superb!

You have done a great job 

Is there anything left where I could assist in testing/debugging?

[funman]

Maybe the fix for FS#10344 didn't work for me?

You're right, FlynDice is working on it.

Is there anything left where I could assist in testing/debugging?

Not really, just report when you see a problem with storage (internal and/or µSD)

[sko]

I've build and installed a fresh SVN checkout (r21619) on my E260 / 4GB SDHC; and for me everything seems to work stable and snappy. Even video playback.. superb!

You have done a great job 

Thats my opinion too. I'm very happy with my e250v2, everything works fine! Really a great job! I'm currently testing everything, but nearly no issues so far. I had one data abort with the following conditions:

• playlist with mp3 files followed by ogg files
• last mp3 was on the last 10 % of time
• I skipped the track and instead of playing the ogg file the player showed data abort

[Hillshum]

Thats my opinion too. I'm very happy with my e250v2, everything works fine! Really a great job! I'm currently testing everything, but nearly no issues so far. I had one data abort with the following conditions:

• playlist with mp3 files followed by ogg files
• last mp3 was on the last 10 % of time
• I skipped the track and instead of playing the ogg file the player showed data abort

Have you been able to reproduce it at all?

[sko]

Have you been able to reproduce it at all?

Yes, but I have not tried other ogg files (didn't have more for testing), so I don't know if the file was corrupted. Imo this should be tested by someone else too, to make sure whether it is an rockbox issue or not. The mp3 files had 320 kBit/s and the ogg files 128 kBit/s.

[funman]

I had one data abort

When you see a data abort, you should write down the address written on screen, and disassemble your current rockbox.elf (or the codec you use if the data abort is in the codec), to see which code does produce it.

Or you can come on irc to give the elf file + faulty address to a developer (it's a bit big to be attached to the forum thread)

[sko]

When you see a data abort, you should write down the address written on screen, and disassemble your current rockbox.elf (or the codec you use if the data abort is in the codec), to see which code does produce it.

Or you can come on irc to give the elf file + faulty address to a developer (it's a bit big to be attached to the forum thread)

Yes, I'll do that next time. I'll try it again if I am at home, maybe it was related to the sd-bug and it has been fixed with the last commits (it happened before these fixes).

[fragilematter]

Hey guys! Just a quick follow-up on the micro sd not working problem on (some of) the e200s. If it wasn't clear already, this problem is induced by FlyingDice's low core voltage patch.
I reverted system-as3525.c to r21282 (pre FS#10344) and the sd is working just fine.

I may come back with a week's worth of data aborts (if any) during this holiday. Cheers!

[FlynDice]

Yes that's the same as MC2739 reports also.  I have had what seems to be the same problem in the past but I'm not experiencing it now.  Just to clarify, we're talking 8GB microsd on an e200 right?

[fragilematter]

Nope, it's just a 1gig Kingmax micro-sd on an e200 (e250 to be precise). Dunno, some sd cards might need a more precise timing and the voltage switch is throwing the timing a bit off, just guessing here...

[Hillshum]

My 2gb SanDisk (plain ole SanDisk, nothing fancy) uSD isn't working in my e260v2.

Also, test_disk has given me a couple of
*PANIC*
flush_fat_sector() - Could not write sector 321 (error -101)

with two different sectors on write & verify. I have gotten plenty of clean runs as well, though I suspect hardware issues.

Additionally, the database isn't updating itself like it should. I unplug from USB having transferred a bunch of files, boot into rockbox, and then need to reboot again to get the database updated.