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

[tessarakt]

I installed rockbox on an e200v2 yesterday. Works fine, except for a very high energy consumption. I could not find anything on the Wiki page, so I am asking here: Is this known? Do you have an idea as to the reason? Anything I can do as a layman?

Cheers,

Jens

[saratoga]

http://www.rockbox.org/wiki/SansaRuntime

[BlueHazzard]

Hallo,
i just updated my sansa e250v2 to the actual rev r24195. Now i get a lot of *Panic* always i made something on the sd card.

The error:
"*PANIC*
SD Xfer read err:0x8 Disk1"

my SD Card: kingston 4GB microSD HC
in the rb disk info is written that the speed is 50MBit/s

thanks

[FlynDice]

@BlueHazzard

Do you have another card to try?  That error is a data timeout while trying to read from the uSD card, I would suggest running chkdsk or fsck on your uSD card to see if the filesystem is damaged.  There aren't any recent changes to the SD driver that I can pin that on.  If you can see that the speed is 50MBit/s I'm guessing that the card initializes alright and you're getting the panics while playing or trying to play?

[TimNixon]

Congrats to the team, especially for fixing the mpeg playback.
Probably not the right place to ask, but I see the remaining needs as USB support, and perhaps enabling line-out on the griffin dock.
Is there any action planned on these items? I know there's a thread about the griffin docks lineout (http://forums.rockbox.org/index.php?topic=22942.0)

Thanks again

[saratoga]

Is there any action planned on these items? I know there's a thread about the griffin docks lineout

We don't plan anything, but as far as I know no one is actively working either.

[BlueHazzard]

@BlueHazzard

Do you have another card to try?  That error is a data timeout while trying to read from the uSD card, I would suggest running chkdsk or fsck on your uSD card to see if the filesystem is damaged.  There aren't any recent changes to the SD driver that I can pin that on.  If you can see that the speed is 50MBit/s I'm guessing that the card initializes alright and you're getting the panics while playing or trying to play?

Hello,
no i haven't a other card to try... And yes, I get the error while playing. I can play a few seconds and then cames the panic...
I don't think, that the file system is corrupt, because the original firmware has no problem....
My first version is very very old. I don't remember anymore the revision... But i think that was a rev before the tries with voltagescaling and so on....

thank's

[OldOne]

I have posted before that some cards have problems with the voltage scaling.

My solution has been to have second build of rockbox with the voltage scaling set to 1.15 rather than 1.10 to use for my problem cards.

You can try going from the main menu to system then debug then CPU frequency.  Rotate the wheel counter clockwise a click or 2 and CPU from 62000000 to 248000000 and boost counter 1.  Press left button to return to menu and try playing from card again.  This raises the voltage as well as cpu speed.   If boosting  solves your playback from card then your card is one that needs a little higher voltage to work properly. 

To undo the boost go back to CPU Frequency and turn wheel to right until it returns to boost counter 0.   

The voltage scaling helps with battery life and is desired but I have 2 PQI cards that dont work properly at the 1.10 level. 

I wonder if the 1.125 level is a possible choice.  FlynDice would know.

Let us know if boosting as described above makes any difference.

[tomers]

I have posted before that some cards have problems with the voltage scaling.

Is it possible that the driver will have some sort of internal database of different cards, to help it decide the proper voltage to use?

[FlynDice]

@BlueHazzard

Since you've updated from a much older build I would tend to agree with  what OldOne posted above.  There is no 1.125 setting, you can use 1.05, 1.10(current), 1.15, or 1.20.  If you can build it's a rather simple adjustment to line 396 of system-as3525.c from CVDD_1_10 to CVDD_1_15.

Does anyone have any thoughts on perhaps disabling voltage scaling again?  It appears right now it only adds about 30 mins runtime.  I have tried to reproduce the results I was getting back in June(17 hrs) but have been unable to do so. 

[kugel.]

We do it wrong if the OF handles those cards and also has voltage scaling.

Also, we boost on any microSD access (and thus raise the voltage), so in theory all cards should work if they work without voltage scaling. It looks like the switching doesn't work right yet.

[BlueHazzard]

I have found that sometimes i can access the card in the "explorer" and play the files.
The manual boosting is working, when i boost then i can access the card without any problems...

So i think also that the problem is the correct boosting on card access.

At the moment i have slight problems with cygwin, so i can't compile, but I' m working on it....

thanks 

[mc2739]

Does anyone have any thoughts on perhaps disabling voltage scaling again?  It appears right now it only adds about 30 mins runtime.

It looks like voltage scaling is causing problems with recording to the microSD card. See FS#10810

I think it would be a good idea to disable the voltage scaling and see if the microSD problem reports decrease.

[saratoga]

Has running the core at 200MHz max and keeping voltage low been tried?  I wonder if that also has SD issues.

[FlynDice]

Has running the core at 200MHz max and keeping voltage low been tried?  I wonder if that also has SD issues.

Yes I've tried it but my player/uSD card are not particularly fussy it seems....