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

[hex]

@ funman:  I'm thoroughly confused.  I searched the forums for ecrips, and the only thing that came up was your post.  How can I PM (or otherwise contact) this user?

[saratoga]

hex:  http://forums.rockbox.org/index.php?topic=14064.930

[FlynDice]

I just postedFS#10344 which lowers the core voltage of the processor when it is running at less than 200 Mhz.  I got just under 18 hours on the battery bench.  Here's a graph for comparison.  This patch is in purple marked Lower Voltage.

[bertrik]

I experimented a bit with the memory layout of my sansa clip, in particular with the location of the stacks. I moved them from DRAM to IRAM (in firmware/target/arm/as3525/apps.lds) and decreased the CODEC_SIZE a bit to make room (in firmware/export/config-clip.h). I have not seen any playback stops anymore (I played and skipped around for several hours).
This probably isn't a proper fix, but at least it may give a clue on what could be causing these playback stops.

[notlistening]

Side note on the FM receiver on the E200 Europe sold as non radio version. Following the wiki on how to upgrade the firmware i got a dual boot system for rockbox and wanted to test the OF to see if what i had read earlier in the forums the all e200's have radio capabilities was accurate.

The menu was there in the OF and I could access it, but no sound. It would tune to the frequency of known stations but still no sound. Then loaded rockbox and it just hungs when i try and run radio, bar the once when it got into the radio menu but t hung soon after.

This all ended up with me (i think being in radio mode in the OF) and having the player plugged into the wall using a wall charger and pushing the power buttons so that it reports going into standby mode. After switching the player back on radio now works in the OF always but not rockbox.

Just thought i should report this behavior even if it is irrelevant. Seems it might be a feature of the OF maybe only when using radio for the first time?

Tom

[funman]

notlistening have you checked FS#10267 ?

Now you should update your forum signature (perhaps change it to "not listening to any radio")

ej0rge sent me a c200v2 and i could get lcd to work (still buggy : sometimes there's no output in the bootloader), and it looks like it has the same problem than e200v2 for the radio, and the same problem than clip for playback.

Hopefully it will help fixing those ..

[sko]

Hi, back again, had not much spare time last two weeks. I updated FS#10284 with my actual attempt of an unified driver for fuze and e200v2.

[aaron424]

the fuze v2 does not even have a development version yet, right?
"Fuze v2
Sansafix at the Sansa forums has announced that a v2 of the Fuze has been released. There are no noticeable differences, but there is a different firmware version that is incompatible with V1 Fuze firmwares. Presumably based on an AS353x CPU like the ClipV2.

The v2 devices are in the wild. Attached are photos of the upperside of the board and the underside."

[saratoga]

the fuze v2 does not even have a development version yet, right?

Correct.  See this page for an overview of whats done on each AMS device:

http://www.rockbox.org/twiki/bin/view/Main/SansaAMS

[funman]

Hi all,

I have committed r21550 which fixes a problem in SD bank selection (also used at startup to enable access to the whole 1st bank).

If you still experience problems after updating to this revision please tell us, and precise if you see filesystem corruption or deadlock at startup.

To rule out problems with previous filesystem corruption, please format your player and reinstall rockbox before reporting.

P.S. I hope nobody will report any problem

[notlistening]

Hate to be the bearer of bad news. r21550 has not fixed the issues for me. I am using a e260v2 and I am getting file corruption on every disk write. I have tested with a brand new rockbox build, formatted using the OF and reloaded everything.

Firstly Database initialization hangs but speech continues to give uodates and back light etc are functioning.

Saving of setting changes are being kept but there are problems being made att he time of the filesystem. I also haveed my sound and theme settings in a .cfg file to disk.

I ran fsck before ruuning rockbox again and no wrrors and after testing the above features I got this output from fsck:

 fsck 1.41.4 (27-Jan-2009)
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 2
/SANSA E2.60
  Contains a free cluster (3). Assuming EOF.
/SANSA E2.60
  File size is 8 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/SYS_CONF.SYS
  Contains a free cluster (4). Assuming EOF.
/SYS_CONF.SYS
  File size is 316 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/MUSIC
  Contains a free cluster (5). Assuming EOF.
/##MUSIC#
  Contains a free cluster (6). Assuming EOF.
/RECORD
  Contains a free cluster (7). Assuming EOF.
/AUDIBLE
  Contains a free cluster (10). Assuming EOF.
/PHOTO
  Contains a free cluster (11). Assuming EOF.
/VIDEO
  Contains a free cluster (12). Assuming EOF.
/##PORT#
  Contains a free cluster (13). Assuming EOF.
Reclaimed 48 unused clusters (1572864 bytes).
Free cluster summary wrong (120838 vs. really 123443)

[kugel.]

I've similar issues on my clip (the FS is totally broken after *very* few writes), but they're not related to rockbox (it's broken after using the OF too). So it might be as well a hardware issue as with my clip.

I'm going to test myself a bit too (my fuze functioned fine so far).

€dit: I just got the same fsck output as in the above post. But actually, those folders are created by the OF and I didn't touch them ever. I suspect the OF is just doing it's magic hackery with the filesystem, and that it's not a Rockbox issue.

PS: WTF is /SANSA E2.60 (or /SANSA FU.ZE respectively) for a folder. Did the OF mess up nameing the partition (could that be why linux doesn't see the Dap's name after a fresh reformat?).

[funman]

I have seen those names in the OF code but not sure what they mean.

The partition created by the OF has no label, I think linux has a builtin list of USB VID/PID to give a name.

[werich]

I have committed r21550 which fixes a problem in SD bank selection (also used at startup to enable access to the whole 1st bank).

OK - at least I can only report good things:
I'm using the actual r21572 build, and it works like a charm on my Fuze 8GB including 8GB microSDHC.

No disc corruption so far (2hours of excessive testing across internal mem and microSD including mp3, ogg, mod and flac mix, crossfade, coverflow, mpegplayer video, radio etc.) and no broken filenames anymore. I didn't even had to reformat my fuze, just replaced the .rockbox folder. Aside from very few random freezes (once the radio after scan&save, once after inserting mod file into playlist) it seems quite stable to me.

Note: I checked the file system with chkdsk /f under windows, but "no errors" imply an intact FAT32, or?!

[funman]

Looks good!

I'll look at adding some code to see if freezes are related to SD driver.

Yeah I think "no error" imply an intact FAT32 filesystem