FS#9642 - Bootloader USB Diskmode fails to exit gracefully on CFModded H100.

Attached to Project: Rockbox
Opened by Davide (Davide-NYC) - Sunday, 14 December 2008, 22:31 GMT
Last edited by Marcin Bukat (MarcinBukat) - Wednesday, 16 June 2010, 17:05 GMT
Task Type Bugs
Category Bootloader
Status Closed
Assigned To No-one
Operating System Iriver H100 series
Severity Low
Priority Normal
Reported Version Release 3.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


On iRiver H1x0 targets, if a CFMod has been performed, returning from USB disk mode is not fully supported from the bootloader. Disk mode works to and from Rockbox (after RB has booted) but to Rockbox from bootloader USB disk mode. In other words, if a user plugs in the USB cable with the player turned off, then boots the player they will get into a working USB disk mode but will be unable to get out of this mode without seeing the dreaded "ATA error: -80". A reset is subsequently required.
This task depends upon

Closed by  Marcin Bukat (MarcinBukat)
Wednesday, 16 June 2010, 17:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  Svn bootloader raported to work
Comment by Davide (Davide-NYC) - Monday, 15 December 2008, 01:33 GMT
For clarity...

If you boot an H1x0 series that has been CFModded while USB connected you will enter disk mode and it works. On subsequent unmount you will be presented with an ATA -80 error and have to reset the device (twice) to get back to a working player.
Comment by David Johnston (animatorgeek) - Sunday, 05 July 2009, 07:22 GMT
I think I've isolated the problem, but I'm nervous to test it out. I really don't want to brick my player. Here's my patch file with the very simple change that I think will fix the problem.
Comment by Davide (Davide-NYC) - Sunday, 25 October 2009, 18:14 GMT
I've just used the SVN bootloader (as of OCT 25 2009) and I no longer have this problem on my two CF cards.
That's not to say that ALL CF cards are now supported. We could use a few testers.
Again, I did not apply this patch, just what's in SVN currently and it seems to have resolved the problem in my instances.
Please test and report back here. If more users report success then I think we have a new H1x0 bootloader!