Rockbox Technical Forums
Rockbox General => Rockbox General Discussion => Topic started by: SheepCake on June 18, 2010, 10:28:30 PM
-
r26946
older builds worked fine with my microsd card, this one refuses to see it.
build r26865 is the most current version i have thats working, I didnt make backups of each ver, so not sure when this started :(
I NEED my msd card, its got all my audio books on it!!!
ok, if i load a version from a .sansa file the microsd card re-appears and is accessable, kind of a pain but for some reasion this works.
All i can think is that it must be either a display issue or a load order issue or something im testing with r26951 and reloading from its .sansa file dumped into the root of the player, wish i could tell you why this is going on, but the fact that reloading from the file works tells me it should be pretty easy to fix!!!
-
Works for me
-
appears to track back to build r26937, 26933 still works fine.
if you would like i could revert to 26937 and send you a picture of the microsd card not being auto mounted.....or mounted on insertion after boot either.
-
Same issue here: on my Fuze v2 with this morning's daily build my micro SDHC card was not recognised. I reverted to r26901 (yesterday's daily) and that works fine.
-
This happens for me as well. No SD card shown in Files Browser and Database discards all entries for music on the SD card. Checked with r26959. Reverting to r26933 works fine for me as well.
-
so it seems to be caused by r26937
could you change DRAM_FREQ in firmware/target/arm/as3525/clock-target.h from 41333334 to 62000000 and see if it fixes the bug?
The pclk frequency would be an integer number of MHz
-
Have updated from svn then made the edit to firmware/target/arm/as3525/clock-target.h and built. No change.
-
could you give 26936 a test, I cant get it to compile >.<
-
Just built 26936 and same problem. 26935 to follow....
My mistake....starting over with 26936
26936 built and installed: no problem with micro sdhc.
-
thanks, so we do now know what killed microsd support at least :)
-
It also seems to be the last thing my Fuze will ever do.....it just died.
-
fully died or what? any chance of recovery?
-
i reverted the offending commit so the bug should not be present anymore
-
fully died or what? any chance of recovery?
It seems to be dead as in deceased, expired, kaput. So back to my iRiver H140 and H340, players that refuse to quit. The Fuze lasted one year, the iRivers are still going strong - both > 5 years old, one battery replaced so far. I just wish they were smaller.
-
fully died or what? any chance of recovery?
It seems to be dead as in deceased, expired, kaput. So back to my iRiver H140 and H340, players that refuse to quit. The Fuze lasted one year, the iRivers are still going strong - both > 5 years old, one battery replaced so far. I just wish they were smaller.
Is this what you're referring to:
http://www.rockbox.org/wiki/SansaAMS#Specific_problems
(last item)
-
Actually some good news.....it was apparently just unresponsive, no sound, no USB, no display, nada. It should have powered down having not been used for a few minutes but instead had hung(?). Realised it was still powered up when hearing some noise removing and inserting the phones and was able to power it off......back to life! Whew! Anyway I'm conscious that bricking it is always a possibility and am prepared to risk it because it's infinitely more useful with RB on it than otherwise. Time to try out latest svn......
-
fully died or what? any chance of recovery?
It seems to be dead as in deceased, expired, kaput. So back to my iRiver H140 and H340, players that refuse to quit. The Fuze lasted one year, the iRivers are still going strong - both > 5 years old, one battery replaced so far. I just wish they were smaller.
good news, but i gotta say, i would take that iriver h300 over the fuze, despite size, I been trying to get a buddy to trade me his for 2years!!!
-
And keep away from my iRivers too! They are mine mine all mine! I'm normally happy to share and help but nobody gets to use those except me and I'm not selling either ;D
Actually the H340 feels terribly slow after a modern flash storage player so I guess a lot of people wouldn't like it, and the monochrome screen of the H140 looks like a piece of history these days. Both now look huge compared to modern players. But I do see both these selling for big prices when they turn up on ebay or similar.
edit: built and installed r26979 and seems all OK.
-
yeah, i would still love a h300, a friend of mine managed to replace his 320's drive with one thats 120gb and a good bit faster then the orignal, not sure where he got it, he also put a better batt in it.
they are a beastly little player for their day, im so sad i missed out on the referb sale of them a few years back 85bucks for the h320!!!!
now im gonna try and figuar out how to use saratoga's volume patch, should be a fun lesson in fighting with cygwin :P
-
SheepCake, sorry to hear I didn't work for you. Please keep in mind that the fuze v2 is still in development, so specific things may break sometimes when trying to move the port as a whole forward.
The idea of the commit that was reverted was 1/ to use the same clock frequencies as we do on the ams v1 sansas and 2/ fix playback rate error (it is now 1.1% too slow again).
Personally, I'm not convinced yet that the change to 248 MHz was the root cause of the uSD problem on the fuzev2. uSD worked fine for me on my clip+ and you said it worked on your fuzev2 when you reloaded ("rolo"-ed) the .sansa file. The fuzev2 is a bit of a special case because of its larger display (so we need to increase the display clock to make sure we have sufficient frames-per-second, for example).
-
that build fixed it(the one that changed clock)
if you can figuar out how to boost the clock without the sd card issue that will rock.