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

[FlynDice]

Well, you can't download it you would need to build it.

You said you tried chkdsk, did you also try formatting?


EDIT:
RE: MCLK for internal SD = IDECLK

I believe I've proved this hypothesis wrong now or at least not completely correct.  While trying to change the references to CGU_NAF_CLOCK_ENABLE to IDE_CLK_ENABLE I found that the MCI_CLOCK register(MCI_NAND on p2 of View HW info) was not being disabled(ie 0x00000000) while there was no disk access.  I think I was lucky and the CGU_NAF_CLOCK_ENABLE is enabled in the bootloader so when I took out the references to it I just kept it from being shut down during sd_enable(false).  This seems to confirm that MCLK does indeed come from PCLK for the internal disk also.

I will revert r23350  shortly as that assumes IDECLK is used as MCLK for the internal disk..

[NaFIann]

Hi, I don't know if this is the right place, but I just wanted to inform you guys that there is a new OF for sansa fuze out in the wild, that mkamsboot doesn't want to work with.
(link)

Also, thanks for all the hard work - I am installing rockbox on my V1 fuze now (was a big fan of it on my V1 e270) and going to give it a test run. I'll post my findings here

[edit]
Preliminary findings:
- also having problems with a horizontal line right underneath the status bar in the main menu 'flickers'; it sometimes turns to black or some colour.
- a few lines of pixels at the top of the screen are eclipsed by some of the lacquer when you look straight at the screen. This is not really the fault of rockbox itself, but does present a ui problem: if you leave it to theme developers to workaround, some of the plugins (games for example) will have a few 'hidden' pixels, but the only other obvious fix is to have some pixels on always off and pretend the screen is smaller than it really is. I don't have a good solution to this, but just thought i'd throw it in the group here.

All else: music playback, sd card, fm tuner, scrollwheel etc. work fine for me so far.

[funman]

Hi,

We don't plan to make new releases of mkamsboot for every new OF release, so mkamsboot 1.1 will reject Fuze OF *.28, you'll have to wait for the next release.

Alternatively you can build mkamsboot from SVN (this OF has been tested and its checksums committed), or wait the next release of the rockbox utility (which will accept this Fuze OF), or use *.26 version or older.

About the missing pixels, this can change between different models because of bad case design : I can see all the pixels on my own Fuze, but previous Fuzes I had exhibited this problem.

[OldOne]

Hello,

My experience with recent releases concering sdhc card.

I have a E260v2 with a PQI 8gb microSDHC card that has worked very well with most versions until about 091016.  After that my microSDHC card will not read properly.  I have tried 091027 along with several in between and it still does not read sdhc properly. Reverting to the 091012(newest that I have that works) version works fine.   

The PQI brand class 6 sdhc card has seemed to work better than a previous A-Data card although it also works fine with the 091012 version.

[funman]

can you define "not read properly" ?

have you tried formatting the card ?

[OldOne]

Funman,
Thanks for quick reply,  I thought I would pass on my experience with recent daily builds.

Properly means to allow view, access, and playing  directories and files.

With the release of 091012 I can can select Files | < microsd> | and see a listing of the directories and files and select any directory or file.  With later releases, ( I haven't tried them all), Main menu | Files | <microsd> shows only the First directory( no other directory or files in the root on microsd> on the disk and if I select it, Rockbox locks and requires a hard( 5 second or more) turnoff.

I think it was somewhere around 091015 or so when I had problems and 091012 was the last working one I had.

Browsing the main disk seems to work fine on any release.    I have formatted the main and microsd  twice.  Everything works great right now with the 091012 release.

[funman]

The voltage change was committed between the 12nd and the 16th so that could be a reason.

FlynDice what do you think ?

[FlynDice]

I'm thinking voltage scaling.  I did remove the BUSWIDTH and BLOCKLEN commands on the 12th but besides that voltage scaling is the only significant change during that period. Since this only seems to affect the uSD and not the internal SD I really suspect it's voltage scaling.

OldOne, are you able to build your own from SVN?  It sounds as if you've just been using the daily builds.

EDIT:  After thinking about this for a bit I'm slightly puzzled now as the voltage should be raised to normal(1.20v) during disk accesses now that we boost on disk access.

OldOne, can you go into System/Debug/CPU frequency and scroll counterclockwise.  The frequency should go from 62000000 to 248000000 and then go back and try to browse your uSD files.  We're manually boosting both the frequency and voltage by doing this.

[OldOne]

FlynDice

I have tried several microSd cards with the latest release and some work fine.

The Adata 8 gb card that occaisionally would panic and would not read is working fine with the new release .  A Transcend 2 gb card also seems to work ok.

The PQI 8gb cards that seemed better on earlier releases don't work any better with the debug procedure you asked me to try.   

The AData card failed on one of the releases about 091021 but is working now 091027.

I have the most music on the PQi cards.  So the problem seems to be only on PQI cards with the current release and boosting does not seem work.  They work fine on 091012.

Thanks for the reply

Edit:

After some more testing with the newest release and 091012:

Going to Debug | Disk info shows 25 mhz for microsd0 in both releases
info for microsd1  shows 25 mhz in the 091012 release but 50 mhz in the 091027 release.  Some microsd cards must not like the added clock speed.

I haven't setup to build my own releases but would like to try a new build with voltage scaling but with 25 mhz speed for sd1.

So for now I am running the 091012 release.  When there is an update to daily build that changes the speed, I will try it.  Are the patches and bugs the best place to monitor changes in daily builds?

[FlynDice]

@OldOne:

The cards are all running overclocked right now at PCLK frequency(62 MHz).  The internals are v1 cards that should use a maximum of 25 MHz, but they don't really give us problems.  If the uSD card is a v2 card we assume it is high-speed capable and switch it to HS timings. HS timings are good from 0 - 50 MHz.  Unfortunately we cannot get either card to function at a different frequency than PCLK right now and are searching for a reason why.  There is no difference in the clock speeds for the two builds you have mentioned.  In both builds you can look on the View HW debug page and see the card frequencies.  It needs a disk access to get a reading  so just insert/eject a card and you should see 62 MHz.  The speed value for the card is not a MHz value but instead a Mbit/sec  value for the transfer speed on 1 data line  (which is all we can use right now also although there are 4 available).  On the 12th I rearranged the HS timing code to be run before the code which checks on the card data so the disk info display would show us 50 MBits/s if we indeed did get a switch to HS timings.

If you can browse the files on your card I'm thinking the problem happens sometime after the init phase and is more likely to be related to when the disk is transferring data.

I think you said you already tried chkdisk. 

I've run into some problems if i've ejected the card while the OF was refreshing the database, that tends show up as  an init problem though.

Formatting the card sometimes works but if your card is working with the Oct 12 build I wouldn't think it was necessary....

[OldOne]

Thanks for the reply FlynDice.  I remembered that the cards were running oveclocked at one time. While viewing the debug info I noticed the difference in info shown between the releases and the cards.  Thanks again for your knowledge and time.  Rockbox is a great improvement over the original Sansa.  I guess I like the option of choosing from the file menu as well as the database.  Video playback is better and the files are smaller than the ones needed for the Sansa firmware.

I will continue to monitor the changes and test releases as I have time. As you continue development,  I will be reading this topic to see if I need to try a new daily build.  I have started reading the bugs and patches too.

No more posts til I have more info.

[funman]

Hi,

Some news on recording: it now works on my Fuze although there are occasional panics (unhandled IRQ with unknown source).

Entering rec screen crashes on Clip (with source == microphone since FM is broken)

Could you test on e200v2 and m200v4/c200v2 please?

EDIT: reported to work on e200v2

I suspect small buffer will be a problem but you never know ..

Use the last patch on FS#10371

[mitch_de]

WARINING :
The newest build r23498-091103 for SANSA V2 , (website newest builds) DL is linked WRONG !
Means if you click SANSA V2 you get complete other firmware (never had that before).
Named of z.ip as it should (sansa...) but : I looked in the info text (.rockbox ) and found:

Target: ondiofm
Target define: -DARCHOS_ONDIOFM
Manufacturer: archos
Version: r23498-091103
Binary: ajbrec.ajz
Binary size: 258300
....
I was a bit ?? about an file ajbrec.ajz in the roor of the unzipped  so i take a look closer.
Normaly i didnt do that and drag& drop the .rockbox to my SANSA .
I believe archos fimrware would be an bad idea ...
I now dl the dialy build (always some builds back to the newest) and wait for an fix of that link.
But i dont complain! Its up to us to take the brain +time first take a look whats in the dl.
So perhaps an hint to look into that dl before putting it on the player - at least with dl of the high frequnty newest builds.

For that closer look ,the sansa V2 builds shoudl have in info.txt as :
Target: e200v2
Target id: 51
Target define: -DSANSA_E200V2
Binary: rockbox.sansa

[Narann]

Alternatively you can build mkamsboot from SVN (this OF has been tested and its checksums committed)

I've done it! Damn I'm too happy! (I'm not a dev )
It take me littles hours but it work! Now I have Rockbox with 1.2.28F OF

The link with all:

Just renamme the "patched.bin" in "fuzeA.bin" and copy it in the root directory of your sansa fuze.

But, if you don't thrust me (I can understand), you can patch yourself with the give mkamsboot.exe

Enjoy!

Edit:  Link removed.

[saratoga]

Please don't distribute software on the forums you don't have permission to distribute (the OF bin file).

Just post the mkamsboot binary instead.

Edit:  heres a link to just the mkamsboot binary if anyone wants it:

http://duke.edu/~mgg6/rockbox/mkamsboot.exe