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

[funman]

EDIT: backlight brightness fixed, bootloader updated
EDIT2: this means you shouldn't follow these directions

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

[FlynDice]

Well I have tracked the write errors down to what I believe is a FIFO problem but I haven't been able to fix it yet.  SD writes fail because we keep getting a FRUN error (FIFO over/underrun).  I have tried changing the FIFOTH values but have had no luck yet.

[funman]

Just throwing random ideas:

Could it be that we need different DMA settings when doing writes?
Have you tried PIO mode instead of DMA for writes?

[FlynDice]

Have you tried PIO mode instead of DMA for writes?

Funny that you bring this up as i just found a spot in the disassembly where it chooses dma or pio depending on a 1 or 0 value.

I haven't actually tried too much the past couple of days as my laptop screen died when i was off at work on a trip.  Researching a replacement now.

I have played with the fifoth settings a bit and different dma settings with no luck.  If I'm reading the controller "info" correctly(I can't call it a datasheet...) this fifo is actually 4096 words deep and we actually "roll our own" FIFO depth by setting the MCI_FIFOTH watermark values.   There is a macro in the linux patch that describes how to find the FIFO depth.

I don't think I'm going to get much done in the next few days besides finding a new laptop but I'll dive back in after that!

[fpsvash]

EDIT: backlight brightness fixed, bootloader updated

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

This worked fine for me and I'll gladly be a tester if you need me.

[luca]

My FuzeV2 is working really well  I put some music on the uSD and it has been playing for more than half an hour with absolutely no glitches. The only thing I could notice is that the clock is offset by a constant: at 14:41 local time, it showed 05:10, but I've no idea of whether RB was using 12-hrs or 24-hrs mode for display. The offset is constant since at 15:24 it shows 05:53, the difference (about 9hrs 31mins) is the same.
Congratulations for the great work

[keland44]

EDIT: backlight brightness fixed, bootloader updated

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

hey just wanted to let you know I got it going on one of my v2 fuze's i have with me now and it comes up when I get home if i remember i'll get it going on my other one
like you said the buttons don't function but it does display the rockbox software and I can go back and forth between the of and rockbox
if there is something else I can help out with let me know do I have two of these I can use to test for you at least till possibly this weekend

[dsimcha]

My FuzeV2 is working really well  I put some music on the uSD and it has been playing for more than half an hour with absolutely no glitches. The only thing I could notice is that the clock is offset by a constant: at 14:41 local time, it showed 05:10, but I've no idea of whether RB was using 12-hrs or 24-hrs mode for display. The offset is constant since at 15:24 it shows 05:53, the difference (about 9hrs 31mins) is the same.
Congratulations for the great work

I'd like to help with testing this thing.  I've got RB on my FuzeV2, and it boots and all, but I can't figure out how to navigate the menus given that the scroll wheel doesn't work yet, blocking further testing.  Tips?

[mate]

@dsimicha

wait until kugel figures out how to use it;)

[keland44]

EDIT: backlight brightness fixed, bootloader updated

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

hey just wanted to let you know I got it going on one of my v2 fuze's i have with me now and it comes up when I get home if i remember i'll get it going on my other one
like you said the buttons don't function but it does display the rockbox software and I can go back and forth between the of and rockbox
if there is something else I can help out with let me know do I have two of these I can use to test for you at least till possibly this weekend

just wanted to let you know I was able to get it going on my v2 fuze and the visual was able to come up and let me see rockbox and going back to the OF pressing the left button works also.
Keep up the great work.

[sierra2kilo]

I'm having trouble getting it working on my clipv2. The bootloader installs and boots fine, but it doesn't want to load the patched firmware (and I've tried patching and loading it twice), due to the checksum not matching.

It's supposed to be this: 2A4F256
But it's getting this: SA4F26A

Length is 6BDC0, if that's helpful, and I used 2.01.32.

Any ideas?

Thanks!

[funman]

Download current build and unzip it on the player

[sierra2kilo]

Download current build and unzip it on the player

Now I'm getting a mismatch of -255 and -269.

[kaps]

EDIT: backlight brightness fixed, bootloader updated

Looking for fuzev2 testers, the LCD started working today

There seems to be 2 different LCD types, at least me and kugel have the same type, so I would like to know if other people have the (hypothetical) other type of LCD on their fuzev2.

To test:

• download this patched OF version 2.3.31 and a current build
• unzip both archives on the root of the fuzev2
• unmount/eject and disconnect: firmware update starts, player powers down itself
• Keep pressing Left and power on : OF start (it'll work as before, you can shut it down at this point)
• Power on without touching left : you should see the rockbox bootloader and then the rockbox menu
• Since buttons do not work yet, you must force a power off by keeping power button pressed for ~20 seconds

If your fuzev2 doesn't display anything when booting rockbox code, power it off by keeping power pressed for ~20 seconds, then power it with left key pressed to boot the OF and update with an unmodified OF.

Then come to us on the forum or irc so we can try custom code on your player

Just booted both OF and Rockbox perfectly fine.  Was able to browse all menus on Rockbox, play music, skip, pause, etc.  Powered off easily.  I'm willing to help with whatever testing needed.

[kugel.]

My FuzeV2 is working really well  I put some music on the uSD and it has been playing for more than half an hour with absolutely no glitches. The only thing I could notice is that the clock is offset by a constant: at 14:41 local time, it showed 05:10, but I've no idea of whether RB was using 12-hrs or 24-hrs mode for display. The offset is constant since at 15:24 it shows 05:53, the difference (about 9hrs 31mins) is the same.
Congratulations for the great work

I might add that there's the possibility of losing the DRM-capabilities of the OF when you set correct time for the time. We had this on the v1 devices IIRC.