Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
mc2739:
@funman
I have tested your bank switching patch on my e260v2.
I can now read sectors below 0x798800 (actually sector 0x7A7800 including the offset). Without the patch, I can only read sectors below 0x1DAE00 (actually sector 0x1E9E000 including the offset).
This appears to be the full capacity of the 4gb e260v2.
The test_disk plugin still fails the write & verify test with a compare error.
michaelc5047:
There's been a bit of talk on the Sansa forums about a pitch issue on the Clip v2 and the Fuze v2, where playback of files with a sampling rate of 44.1KHz is 2% slower than it should be due to a clock problem. I personally have an 8GB Clip and a 4GB Clip (of the v1 variety) and have compared playback between the two, and noticed that the 8GB does play slightly more slowly. A couple of the threads are here (indicating that fixes are in the work in upcoming firmware upgrades, but at the expense of power consumption): http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&thread.id=11835 and http://forums.sandisk.com/sansa/board/message?board.id=clip&message.id=16478#M16478.
Would the clock issue be a problem, power consumption-wise, for eventual Rockbox builds on these units? Or is it completely too early to tell and/or hypothetical at this point?
Thanks.
yelped:
Hypothetical at this point. ;)
kugel.:
--- Quote from: funman on March 19, 2009, 09:45:44 AM ---This is why I always test code removal bit per bit ^^
I have made significant progress now:
I can read my watermark past the 0x1E9E00th sector.
I needed some initialisation, which enables the access to 0x1E9E00*4 (just like e200v1) sectors on the first bank.
I suppose bank switching works but I can't test rigorously since without USB access I can not modify/dump the whole disk structure of my Fuze. I even ignore if it's a 4 or 8GB.
The OF code seems to handle only 1 or 2 banks (4 or 8GB) : do you know if a 16GB model exists ?
Next step is to find the number of banks dynamically to know the exact size of each model, and also test if it needs bank switching or not (2GB and less models don't).
I attach my current patch, I'd appreciate if you can test it and play with it on e200/Fuze/Clip
--- End quote ---
The patch seems to work fine, I didn't test deeply (most of my music is mp3, which crashes anyway), but under the assumption, that MediaMonkey sync's alphabetically, it seems I can access albums near to A as well as those near to Z, which indicates successful access over the bank borders.
The capacity is reported correctly too.
Given that the capacity is reported correct, bank switching could be enabled upon checking the capacity, right? If >= 4GB, then enable banks.
funman:
@Hillshum
I don't know how to verify if the cable is fine, but that could very well be the case.. I'll ask my friends to see if I can find a Sansa + a cable to see which one of the cable or the Fuze is damaged.
For now, I continue working with the microSD ;)
@mc2739
Did the test fail before using this patch ?
@kugel
How come the capacity is reported fine ?
The CSD reports 0x1E9E00 sectors on my Fuze and I remember that it was identical bit per bit for all e200 and Fuzes (even with different capacities).
Are you reading it from debugging > disk info ?
I'm still looking at how to find the number of banks (4GB or 8GB), and if they are needed or not.
If you can give me different CSDs with their model & capacity I could compare them with the one I have (I was reading the function which parses the CSD and I noticed some 'out of spec' fields!!)
By the way I tried to enable the MMU and noticed some problems:
- if I enable caching & buffering (flag 0xC) on IRAM I see crashes quickly after boot
- if I enable it on SDRAM I can not boot : the 1st sector (partition table) is incorrectly read
Flyndice: I looked (quickly, because I don't know anything about this stuff..) at the MMU code in the OF of Clip and Fuze and I see a strange thing:
- Clip OF enable caching only for the 1st MB of SDRAM (out of 2)
- Fuze OF enable caching onyl for the first 5 MBs of SDRAM (out of 8)
weird.. !
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version