Support and General Use > Hardware
Sansa Clip+: bricked by rockbox
saratoga:
--- Quote from: johnnyz86 on February 14, 2012, 04:12:13 PM ---
--- Quote from: saratoga on February 10, 2012, 03:38:27 PM ---If it crashed and holding power doesn't work (and you've tried it a few times for up to a minute), you might have to wait for the battery to die.
--- End quote ---
Thanks, this was indeed the case.
Is there like a core file or anything that can help figuring out what happened?
--- End quote ---
Nope. Once there is a crash the storage isn't even available, so nothing gets saved.
johnnyz86:
--- Quote from: saratoga on February 14, 2012, 04:13:43 PM ---
--- Quote from: johnnyz86 on February 14, 2012, 04:12:13 PM ---
--- Quote from: saratoga on February 10, 2012, 03:38:27 PM ---If it crashed and holding power doesn't work (and you've tried it a few times for up to a minute), you might have to wait for the battery to die.
--- End quote ---
Thanks, this was indeed the case.
Is there like a core file or anything that can help figuring out what happened?
--- End quote ---
Nope. Once there is a crash the storage isn't even available, so nothing gets saved.
--- End quote ---
How do you recommend getting started with debugging and fixing it? After I've set up a development environment and compiled? I've been looking at using some of my signal processing experience in embedded environments anyway.
saratoga:
--- Quote from: johnnyz86 on February 14, 2012, 04:50:36 PM ---
--- Quote from: saratoga on February 14, 2012, 04:13:43 PM ---
--- Quote from: johnnyz86 on February 14, 2012, 04:12:13 PM ---
--- Quote from: saratoga on February 10, 2012, 03:38:27 PM ---If it crashed and holding power doesn't work (and you've tried it a few times for up to a minute), you might have to wait for the battery to die.
--- End quote ---
Thanks, this was indeed the case.
Is there like a core file or anything that can help figuring out what happened?
--- End quote ---
Nope. Once there is a crash the storage isn't even available, so nothing gets saved.
--- End quote ---
How do you recommend getting started with debugging and fixing it? After I've set up a development environment and compiled? I've been looking at using some of my signal processing experience in embedded environments anyway.
--- End quote ---
My guess is that this bug is already fixed in newer builds by reenabling the ROM clock on power down, so the first thing I would do is update and then see if there anyway to make it happen again.
johnnyz86:
--- Quote from: saratoga on February 14, 2012, 05:41:29 PM ---
--- Quote from: johnnyz86 on February 14, 2012, 04:50:36 PM ---
--- Quote from: saratoga on February 14, 2012, 04:13:43 PM ---
--- Quote from: johnnyz86 on February 14, 2012, 04:12:13 PM ---
--- Quote from: saratoga on February 10, 2012, 03:38:27 PM ---If it crashed and holding power doesn't work (and you've tried it a few times for up to a minute), you might have to wait for the battery to die.
--- End quote ---
Thanks, this was indeed the case.
Is there like a core file or anything that can help figuring out what happened?
--- End quote ---
Nope. Once there is a crash the storage isn't even available, so nothing gets saved.
--- End quote ---
How do you recommend getting started with debugging and fixing it? After I've set up a development environment and compiled? I've been looking at using some of my signal processing experience in embedded environments anyway.
--- End quote ---
My guess is that this bug is already fixed in newer builds by reenabling the ROM clock on power down, so the first thing I would do is update and then see if there anyway to make it happen again.
--- End quote ---
Ah ok, I see that patch. Is there any other use for the ROM clock?
kholto:
My old clip+ did exactly this running stock firmware. So it could be completely unrelated to Rockbox.
In other news, I now have two functioning clip+'s. Thanks for mentioning the battery thing before i threw the old one out :D
The old one has a broken power button though (turn it on with USB, off with timer) so not sure if I will have it other than as a backup perhaps.
I will probably be putting Rockbox on one or both now, my only concern is how well it handles audiobooks? I saw that you put in some resume feature a bit like the original sansa FW. Not sure I completely understand how it works though. I could just boot it in the normal firmware for audiobooks I guess.
EDIT: Now the new one wont start, this can only get better by going for Rockbox!
EDIT2: Sorry to be thread-ninjaing, but I might aswell write what happens next.
I played doom on the old clip+, then found out you need the power button to exit it. oops.
I managed to open up the old clip+ and I am now going to attempt soldering the power button back on the PCB, wish me luck.
EDIT3: SMD is so small! but the operation was a success anyway.
I have been fiddling with Rockbox for the last 2 hours and comparing it to the stock system (since I now sit with 2 fully functional clip+'s) It is awesome!
My only problem is how it handles audibooks, is there a way to have the database permanently ignore a set folder? It is a bit anoying that I can't just "play all"
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version