Rockbox Technical Forums

Rockbox General => Rockbox General Discussion => Topic started by: tom` on June 01, 2010, 09:18:08 PM

Title: Fuze V2: recovering from a crash
Post by: tom` on June 01, 2010, 09:18:08 PM
I recently installed Rockbox on a Fuze v2 -  r26367. The install proceeded normally and Rocbox was running well. After using it for a short period of time, the player appeared to abruptly shut off, and was subsequently unresponsive. I assumed that Rockbox had locked up with the screen off, and I followed the procedure outlined in the FAQ, holding the power switch in the 'on' position for 30 seconds. This did not work. I tried holding the switch for various lengths of time, up to around five minutes, and in conjunction with pressing various other buttons. Still the player did not restart.

I ended up waiting for the battery to drain completely, which took around three days. I was then able to charge the player and use both Rockbox and the original firmware.

Has anyone else experienced this issue? Is there any known way, apart from that outlined in the FAQ, to reset the player when this happens?
Title: Re: Fuze V2: recovering from a crash
Post by: Graveyard on July 30, 2010, 08:33:10 AM
Yes, same thing.  guess I'll let ya know in 3 days
Title: Re: Fuze V2: recovering from a crash
Post by: pierrot on August 03, 2010, 06:15:59 PM
same things too

can you describe how it crashes

me, after connecting the fuze with rockbox on.

 SO,  NEVER CONNECTING THE FUZE V2 WITH ROCKBOX ACTIVE


 THIS SHOULD BE WRITE SOMEWHERE IN THE WARNING !!
Title: Re: Fuze V2: recovering from a crash
Post by: Chronon on August 04, 2010, 03:26:11 PM
There is this mention on the SansaAMS page in the wiki:
Quote
Specific problems
  • Clip+/Clipv2/Fuzev2 USB: Some work has been done on USB support. Work is based on the patch to Linux 2.6 for as353x and on the s3c-hsotg driver in Linux. Some partial information from the S3Cxxxx? SoC datasheet applies but the controller described is probably older and thus does not include the full description. The current SVN code reliably stuck the controller at both high speed and full speed; the problem is still open.