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

[izzy84075]

Just flashed my Fuzev2 with the patched .31 OF from a few pages ago and started playing around with it.

Not sure whether this is a known thing or if it's on purpose, but with r25811-100504, the scroll wheel light flickers while building the database. Default settings on everything except the "Wheel Light Timeout" is set to "Off".

It's actually kind of nice if it's on purpose, but if it's not, what else is it doing?

[bilditup1]

I just tried 25811, and still have SD problems: hangs at boot, and doesn't load SD if inserted after booth, this is for several different values for udelay()/sleep(). Reverted to 25791 for now.

-e

[Jennifur]

I just tried 25811, and still have SD problems: hangs at boot, and doesn't load SD if inserted after booth, this is for several different values for udelay()/sleep(). Reverted to 25791 for now.

-e

I'm also still experiencing this. Anything else that could cause this?

[FlynDice]

@Those having uSD problems:

Would you please check that your file system is not damaged by running either chkdisk or fsck depending on your OS.
If you still have the same symptoms please post the following info;

• Card Manufacturer
• Card Capacity
• Card Speed Class(2,4,6 usually has a small circle around it on your card)

I was actually having the problem where boot hangs if the uSD card is present but running fsck cleared that up.  And yes the card worked just fine in the OF.

Thanks!

[MasterFen]

Do you think we could reinstate the Clip+ port as an unstable port, rather than an unusable one?

[Jennifur]

Did a chkdisk and it came out clean. Still won't work with rockbox. Hangs on boot with it in, and won't see it after inserting it. The odd thing is, it detects both the internal memory and the external uSD in the disk info under the debug menu after inserting it. I'm using an 8GB Class 4 card from Kingston.

@Those having uSD problems:

Would you please check that your file system is not damaged by running either chkdisk or fsck depending on your OS.
If you still have the same symptoms please post the following info;

• Card Manufacturer
• Card Capacity
• Card Speed Class(2,4,6 usually has a small circle around it on your card)

I was actually having the problem where boot hangs if the uSD card is present but running fsck cleared that up.  And yes the card worked just fine in the OF.

Thanks!

[funman]

on my clipv2, r25799-100503, everything works fine, unless "pitch" function; if modified frequently, it leads to great unstability.

Thanks for the info, I will try to reproduce.

Button light now flashes like crazy while switching tracks

the scroll wheel light flickers while building the database

Yes it does that, just ignore it until someone fixes it.

i'm currently 10 hours into a battery bench on my clip v2/r25799/database enabled/ogg q5. i'll post full results when complete. still 40% battery left so i'm aiming for around 16 hours i think.

playback is running fine although cpu frequency has to be boosted. i can barely last 20 minutes without it.

edit: i haven't tested this build unboosted but all recent builds have been problematic for me and i have no reason to think the new addition of write support is going to fix that?? absolutely no problems boosted though.

It's still not fixed although it is a bit better now (i got 10 hours on Clip+ before it crashed, 2 or 3 hours on Clipv2).

Ideally the bench should operate in normal conditions but a bench with the CPU boosted will be nice to have anyway.

The Fuzev2 worked all the 18h20, perhaps the difference with PCLK (40MHz on Fuzev2, 24MHz on Clips) plays here?

Do you think we could reinstate the Clip+ port as an unstable port, rather than an unusable one?

Yeah I think we could, dunno what the other devs think

If you still have the same symptoms please post the following info;

• Card Manufacturer
• Card Capacity
• Card Speed Class(2,4,6 usually has a small circle around it on your card)

Please post the infos of your card

[Jennifur]

I did, it was my last line in my post. It is a 8GB card, manufactured by Kingston, and it is a class 4 card.

If you still have the same symptoms please post the following info;

• Card Manufacturer
• Card Capacity
• Card Speed Class(2,4,6 usually has a small circle around it on your card)

Please post the infos of your card

[funman]

Oops didn't see it sorry

battery bench for fuzev2 attached (it starts at 94% but the OF said charge was complete)

[pbow9]

@Those having uSD problems:

Would you please check that your file system is not damaged by running either chkdisk or fsck depending on your OS.
If you still have the same symptoms please post the following info;

• Card Manufacturer
• Card Capacity
• Card Speed Class(2,4,6 usually has a small circle around it on your card)

I was actually having the problem where boot hangs if the uSD card is present but running fsck cleared that up.  And yes the card worked just fine in the OF.

Thanks!

I have some different uSD cards to try. The 2gb non-SDHC card I have does not hang up.

Two cards that do:

Kingston  4gb Class 4 SDHC, labeled as C04G (I think it's actually Toshiba flash from what I'm seeing in search results).
Toshiba 16gb Class 2 SDHC, labeled as C16G

I've run chkdsk on the 16gb, but it made no difference.

[marc2003]

i'm currently 10 hours into a battery bench on my clip v2/r25799/database enabled/ogg q5. i'll post full results when complete. still 40% battery left so i'm aiming for around 16 hours i think.

playback is running fine although cpu frequency has to be boosted. i can barely last 20 minutes without it.

edit: i haven't tested this build unboosted but all recent builds have been problematic for me and i have no reason to think the new addition of write support is going to fix that?? absolutely no problems boosted though.

It's still not fixed although it is a bit better now (i got 10 hours on Clip+ before it crashed, 2 or 3 hours on Clipv2).

Ideally the bench should operate in normal conditions but a bench with the CPU boosted will be nice to have anyway.

i'm more than happy to try another benchmark (unboosted) when this has finished. should i try again on r25799 or try the latest?

[bilditup1]

Chkdsk found no problems and did not help issues with the new build.

My card is an 8GB Class-4 Kingston. It is marked "CO8G JAPAN" and "SDC4/8GB 07".

A non-HC 2GB card, also Kingston Class-4, was recognized without problems. It is marked "SD-CO2G JAPAN" and "SDC/2GB 29".

EDIT:

I just tried again. While the Fuze hung-up when the card was present at startup, it was successfully recognized when inserted afterward. However, clicking through and opening folders are now a mite sluggish in comparison with 25791. Also - this behavior is not consistent: I've tried turning on and off the Fuze several times, and then inserting the card.

EDIT 2:
This only happened twice so far, and the second time, it was after popping the card in and out several times on the same boot without success. Thrice, I got a "*PANIC* microSD init failed: -3" and then a reboot. One time, the thing decided to reboot on card insertion without any message at all. Oh, and all of this is with udelay set to 5000, which is probably not the optimal number, but there is no reason to believe that 1000 will work, and I don't want to keep doing trial and error before the startup issue is fixed.

When I tried to build a db, I likewise got the flickery scroll light at the beginning of the scan, but it stopped at some point, and is only present when the screen backlight is on (e.g. it returns when I push a button during the db build).

EDIT 3:
This PANIC seems to relate to this do-while in sd-as3525v2.c:

Code: [Select]

    do {
        /* this timeout is the only valid error for this loop*/
        if(TIME_AFTER(current_tick, init_timeout))
            return -2;

        /* app_cmd */
        send_cmd(drive, SD_APP_CMD, 0, MCI_RESP, &response);

         /* ACMD41 For v2 cards set HCS bit[30] & send host voltage range to all */
        if(!send_cmd(drive, SD_APP_OP_COND, (0x00FF8000 | (sd_v2 ? 1<<30 : 0)),
                        MCI_RESP, &card_info[drive].ocr))
            return -3;
    } while(!(card_info[drive].ocr & (1<<31)) );

Of course, I couldn't tell you what that means exactly. Some bit is being set for SDHC (v2). I was getting -2 errors back when udelay was 1000 with the older build 25791 (timeouts). So is the problem here, or in send_cmd()? I really dunno Just curious, askin' questions...

[Jennifur]

EDIT:
After reading bilditup1's post. I tried for myself. It will still hang with the card inserted when you turn the player on. Inserting the card right after start does not work either. What does work is, turning on the player without the uSD card, play a track from the internal memory, and then insert the uSD card. It will detect it and play from it just fine.

[bilditup1]

Yep, Jennifur is right: it seems to work if you play a file, but not before then. Thanks for figuring it out

-e

[marc2003]

right, my battery test has just finshed. 14h21m in the end.

sansa clip8gb v2
r25799
ogg q5, 11 track album, avg 143kbps
cpu boosted (i'll try again unboosted when it's charged again)
volume -14 (i had to put player in another room because that's quite loud indoors :p)

edited with attachments instead of external links.