Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
saratoga:
--- Quote from: DonDan on May 27, 2010, 01:57:31 PM ---
Why is the File Allocation Table is only written at the end of recording process?Would it not be better if it is done at the beginning to ensure you find the file without a fdisk procedure in case of a power down or crash?
Am I missing something?
--- End quote ---
Yes, that its not the 1970s and none of us is Bill Gates. Go ask him why he designed FAT the way he did.
Xanikseo:
I've noticed that since r26335 (it may have been introduced earlier) I have to wait for "Refreshing your media" to finish in OF, after whenever I have used Rockbox (even when just switching on rockbox, and powering off again).
Also I can't charge anymore with a wall-charger, without it booting into OF (yes, ok you can hold down select). Surely I should be able to use a wall-charger without booting into OF, since I can't really transfer any data with a wall-charger? Or is it because we don't know how to detect if someone is just using a charger or is in fact connecting to a computer?
Rob2222:
Hello,
my brand new FuzeV2 doesnt want to flash a patched firmware, however the original fuze02.03.33 FW he flashes flawlessly.
I tried 02.03.33 from http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&thread.id=38046
with mkamsboot.exe from http://forums.rockbox.org/index.php?topic=14064.msg167356#msg167356
and output was http://pastie.org/981998
I also tried 02.02.26 from http://daniel.haxx.se/sansa/amsfw.html
with mkamsboot.exe from http://download.rockbox.org/bootloader/sandisk-sansa/mkamsboot/win32/
outpus reported success, also.
Renamed output.bin to fuzpa.bin. After disconnecting mass-storage-usb the player doesnt start the flash process.
With original fuzpa.bin he starts flash process after disconnecting mass-storage-usb.
30 minutes ago I flashed my also new Clip+ with the same mkamsboot.exe without problems.
Any hints? I can upload the output.bin if wanted.
If I don't need to set up a own compile chain it would be very nice.
EDIT: Same problem by 2 user here: http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&message.id=42952#M42952
You can only flash 03.31 and 03.33. Hmm...
EDIT2: It doesnt want to flash the original 2.1.17, 2.2.26, 2.2.28, too.
It only flashes The 2.3.31 and the 2.3.33.
Looks like it has an additional check.
BTW, here is a dirlist:
Datenträger in Laufwerk G: ist SANSA FUZE
Volumeseriennummer: 0CF5-6F32
Verzeichnis von G:\
01.01.1980 00:00 <DIR> MUSIC
01.01.1980 00:00 320 SYS_CONF.SYS
01.01.1980 00:00 <DIR> RECORD
01.01.1980 00:00 <DIR> AUDIBLE
01.01.1980 00:00 <DIR> PHOTO
01.01.1980 00:00 <DIR> VIDEO
01.01.1980 00:00 <DIR> PODCASTS
01.01.1980 00:00 <DIR> AUDIOBOOKS
01.01.1980 00:00 51.237 RES_INFO.SYS
01.01.1980 00:00 83 version.sdk
01.01.1980 00:00 7.800 VIDEO_BM.SYS
01.01.1980 00:00 114 DID.bin
01.01.1980 00:00 1.862.468 MTABLE.SYS
6 Datei(en), 1.922.022 Bytes
7 Verzeichnis(se), 7.675.346.944 Bytes frei
Any new file maybe?
BR and thanks in advance
Robert
csavery:
--- Quote from: Xanikseo on May 28, 2010, 11:42:22 AM ---I've noticed that since r26335 (it may have been introduced earlier) I have to wait for "Refreshing your media" to finish in OF, after whenever I have used Rockbox (even when just switching on rockbox, and powering off again).
--- End quote ---
I've had this same behavior with r26251.
I don't think it's Rockbox causing this since it is the OF that is deciding to refresh media.
It may be the 02.3.33 OF as it was about the same time I rebuilt my firmware file. I wonder if Sansa set it to detect changes it didn't used to and which files it may now be detecting?
Update - I reverted back to firmware based on 2.2.26 and it does the same thing now. I think this means that Rockbox is now altering some file that the OF detects as needing a media refresh...
It's quite annoying when doing development as it means having to wait for refreshes at least twice as many times. I don't think the OF has any smart key presses for bypassing the refresh - only cool rockbox devs can think of that it seems.
FlynDice:
--- Quote from: Rob2222 on May 28, 2010, 12:22:17 PM ---EDIT2: It doesnt want to flash the original 2.1.17, 2.2.26, 2.2.28, too.
It only flashes The 2.3.31 and the 2.3.33.
Looks like it has an additional check.
--- End quote ---
That's what it seems like to me also. I had no problem updating with OF V02.03.31A with current SVN mkamsboot. The OF must now be doing some kind of additional check on this file before commencing the update process.
It seems V02.03.31A will indeed use a Patched fuzpa.bin though. If you can flash 2.3.31 back onto your player you may be able to use that to flash a patched firmware.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version