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

[saratoga]

Please remember that asking for help installing rockbox is off topic in this forum. 

[ClevelandTony]

Gentlemen! Just Rockboxed my Fuze v1.
You guys fecking own! This thing went from mediocre to flat out amazing.
(My first experience with RB)
LONG story short I used to have a v2 Fuze. I acceidentally plugged it into a bad USB port and it became superheated. Didn't totally fry though, just fried the battery. Battery life is very short.

Wound up gettiing a refurb Fuze on Ebay and it just hapened to be a v1. So I RB'ed it.

As a thank you, I would like to offer my Fuze V2 to any developer here that wants it. I will pay shipping in the US.I don't know how much help it will be with the borked battery life, but if it will, it's yours.

Let me know.

[MartyLK]

Another update to the functionality of RB on the c200v2. Playback stops after one song. Once the first playing song finishes, the next song is queued but it won't play. I don't know it the issue is with only my c250 or not. I have formatted the MSC side and installed music on the MSC mode as well as the MTP. But neither mode makes any difference. The menu system and options all seem to function normally.

[rock_c250]

My c200v2 stopped many times after two songs. Some times after one. But it played 20 mins mp3 without stopping. Once stopped some times it won't play until restart. Some times it plays after stop and start a new mp3 again. May be a random playback crash as known.

Album art, Menus, EQ, database looks working perfect.

[kugel.]

1-in settings..recording..clear recording directory does not delete them
2-manual does not describe how to record (start, stop etc)
Q?:is there a way to set the recording 'to' directory?

1. The clear recording directory does not delete recordings, it resets the recording save directory back to the root directory.

2. The manuals are updated nightly and should now have the recording sections included.

A. Yes.  In the file browser, highlight the directory you wish to use for recording and bring up the context menu (long select).  Scroll down to "Set As Recording Directory" and press select.

This thread isn't for support questions.

[mc2739]

This thread isn't for support questions.

Sorry.

@TimNixon - Recording questions moved here: http://forums.rockbox.org/index.php?topic=23245.0

[OldOne]

FlynDice,

I have installed a cygwin environment and built 23131 with newer versions of ata_sd_as3525.c as well as pl180.h (for needed includes) but nothing else changed and they worked with all my cards.  Even newer versions of ata_sd_as3525.c after voltage scaling. (I don't believe voltage scaling is taking place with the old system_as3525.c)

The newest version 23745 will work with any card if I boost the CPU frequency before inserting the card.  My Pqi 8gb class 6 cards ( the ones I wished worked) will work with CPU boosted.

If I unboost the card stops working( attempting to go to  Files | microsd1 |   goes to first screen and system  usually freezes and requires a hard power off. 

Is there some way to be sure the voltage is boosted before we access the microsd card.  I am trying to read system_as3525.c  to better understand.  I think some cards just overclock better than others.  Is there a way for me to turn off reduce the amount of voltage scaling and build my own new version?  Will we ever be able to run the cards at 50 instead of 62?

PS  All my cards work fine in original firmware or card reader.

Thanks to all.   I am happy to build and try any suggested changes if that will help.

[FlynDice]

@OldOne:

Yes, I have been working on getting the cards to run at lower frequencies along with enabling 4-bit widebus but I have been unsuccessful on both so far.  I had the cards running at 31 MHz at one point but not reliably, and that is not woking right now anyway.

The voltage and frequency scaling actually happens in system-as3525.c so if you're interested, that's the place to look, see

 void set_cpu_frequency(long frequency)

near the end.

We do, in fact boost both voltage and frequency when a uSD card is present during a disk access.  You can find that in ata_sd_as3525.c

 void sd_enable(bool on)

near the end also.

If you've got a build environment set up I would suggest changing line 379 of system-as3525 from CVDD_1_10 to CVDD_1_20 which will keep the voltage scaling code in place but will not actually reduce the voltage.  ie it "changes" from 1.20v to 1.20v...

Please let me know your results!

[OldOne]

FlynDice,

Built latest with the change you suggested on voltage.  My PQI cards work fine.  i will read some more and let you know if I have any ideas.

Thanks

[ClevelandTony]

Just an FYI for the devs.
When I installed Rockbox I had some DRM audiobooks on my player. Bootiing back to the Sansa OF and they still worked. But I wanted to test that I could still load new DRM files.
Went to the library website and was able to download, copy, and play a new DRM title.
So DRM is not broken on m Sansa. Thanks.

(Saratoge, this is Peregrine from the Sansa forum. Wantd to wait to post result here until I tried a new title.)


//edit// As for the offer for my Fuzev2... I should have been more specific. The battery still works but it only lasts for 3 or 4 hours at best.

It's not totally dead.

[johnc60]

I installed the latest build of Rockbox (r23773) on an m250v4 per the instructions and things seem to work pretty good.

One problem that I came across is that the audio is very low, as installed.  When I raise the volume up beyond the -2dB setting, the music will play at the higher volume for a short time (seconds) and then the player just turns off.  There are no warning messages.  It just dies.  Restarting the player returns it to the previous volume level.  The original firmware plays very loud with no problems across the entire range of volume settings.

Any ideas?  Any additional info needed?

-John

[saratoga]

edit:  Sorry, read "m200v2" as "e200v2". 

FWIW, its less confusing if you call it an m200v4, since the m200v2 is probably not what you have

[mc2739]

When I raise the volume up beyond the -2dB setting, the music will play at the higher volume for a short time (seconds) and then the player just turns off.

If you check the Current Status chart on the SansaAMS wiki page you will see that this is a known problem on the m200 "v4" port (OF v4.xx.xx).

[johnc60]

Right.  I corrected it to say v4.  I was just following the title which says (v2).     I actually have a v2 also.  Thanks for the pointer to the chart.  I've read that chart before but it didn't stick in my head.

I think it might be a power issue.  If I disable the backlight, the volume can be raised up a few dB before it dies.

The Rockbox code must be setting up the audio amp or pre-amp in some strange manner on this platform or the codec is not delivering the correct input levels to the audio amp.   Even at low to moderate volume, the audio is distorted.  With the original firmware, the audio is clean even at ear-deafening volume levels.

Is it possible that the audio level is too low at the input of the final audio amp?  Therefore, we have to crank it way up just to get a decent volume causing huge power draw and the power regulator shuts down?

-John

[saratoga]

I took a quick look at line out.  According to this thread:

http://www.head-fi.org/forums/f6/sansa-fuzes-diylod-v1-v2-guide-56k-421318/

The Fuze OF pulls one of the dock pins high (3v).  I have confirmed this on my Fuze.  A dock then connects this to another pin  We currently do not know how to pull this pin high, but its probably one of the handful of unassigned GPIO pins.

According to this thread:
http://forums.rockbox.org/index.php?topic=22942.0

DBOP_DIN9 changes when a fuze dock (which uses external power to pull the dock pin high so scanning isn't needed) changes.  But thats also GPIOB7, which apparently did not change according to that thread, so I'm a little confused.

Edit:  I tried manually putting 3v on the dock pin and looking for a change in debug menu, but I didn't see anything.  Looking more carefully at the debug menu output, I see that the GPIOB7 pin is configured as output currently, so I suppose I shouldn't see anything.  On the upside, assuming I did this right, I was able to rule out GPIOA0, and GPIOC0/1.  That only leaves some of the shared GPIO/DBOP pins unaccounted for.