Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
jago:
Hello!
Nice work until now. Thanks :).
I own a sansa e260 (4Gb) and I have big problems with revisions higher than r20922.
With r20923 started the trouble. My sansa freezes every few minutes or I get error messages like this: *panic* flush_fat_sector() - could not write sector xxxx (error -101)
There must be something problematical with this commit, at least for my sansa.
I am back on r20922 now and all is fine.
funman:
Can you update to last svn again, and change AS3525_IDE_FREQ in firmware/target/arm/as3525/clock-target.h to 90000000 ; and see if this fixes your problem ?
I suppose that the problem is the change from 90MHz to 66MHz , perhaps we need to adjust it a bit.
We used 248/((248/90)+1) = 82.666MHz and now 248/((248/66)+1) = 62MHz IDE clock
When using PLLA at 384MHz, the OF uses 384/((384/66)+1) = 64MHz clock (perhaps not always since there is more than one PLLA setting in the OF)
FlynDice:
Need some help if anyone has had this happen. I can't access my internal memory through usb and the OF anymore. I can access the microsd card just fine though and I can copy from it to the internal memory ok using rockbox. Tried a different cable no luck. Different computer, no luck Copied a new copy of a rockbox bootloader to the internal card and it went through the firmware upgrade process just fine but same results with usb. Anyone got any ideas for me?
EDIT: Nevermind, I took a chance and reformatted with the OF and it restored my connectivity with the internal disk, Whew ;D
I'm attaching a patch that puts some clock debug info on the debug view hardware page. I believe the sd numbers are out of whack but the rest work I think. The assumption is that PLLA is at 248MHz and I've tried to pull the actual divider values out to see what the clock values are ending up as for the various peripherals. Your mileage may vary of course...
stray:
--- Quote from: funman on May 15, 2009, 08:31:36 AM ---Can you update to last svn again, and change AS3525_IDE_FREQ in firmware/target/arm/as3525/clock-target.h to 90000000 ; and see if this fixes your problem ?
--- End quote ---
This fixed my Fuze. Before i had to try several times to get the database to build, got some *panic* errors etc.
jago:
--- Quote ---change AS3525_IDE_FREQ in firmware/target/arm/as3525/clock-target.h to 90000000
--- End quote ---
I have just tried.
Seems to solve the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version