Notice: A non well formed numeric value encountered in /sites/ on line 96 Notice: A non well formed numeric value encountered in /sites/ on line 96 Notice: A non well formed numeric value encountered in /sites/ on line 96 Deprecated: Function create_function() is deprecated in /sites/ on line 104 Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /sites/ on line 845 Deprecated: Function create_function() is deprecated in /sites/ on line 111 FS#12769 : rb 3.12 - iriver H140 bootloader crash: 1st boot fails, Reset pin, 2nd boot Successful. Repeatable.



FS#12769 - rb 3.12 - iriver H140 bootloader crash: 1st boot fails, Reset pin, 2nd boot Successful. Repeatable.

Attached to Project: Rockbox
Opened by Leo H. (FLACvest) - Friday, 19 October 2012, 05:24 GMT
Task Type Bugs
Category Bootloader
Status Unconfirmed
Assigned To No-one
Operating System Iriver H100 series
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Rockbox Info: Version: 3.12

Device: iRiver H140, 80GB Toshiba MK8009GAH 8mm 1.8" IDE HDD 8mm


BUG: Repeatable, Consistent.


Additional Information:
1. To verify that I had a good installation of the 3.12 version of the Rockbox firmware working, I have reformatted, and re-flashed rockbox 3.12 two seperate times after initially encountering this, duplicating this behavior. So it doesn't seem to be a bad firmware flash.


Expected Behavior:

1. Player should Power On and boot properly every single time the bootup sequence is initiated correctly (Play Button pressed when Player is in a Powered Off state).


Buggy Behavior:

1. Player Powers Up, then locks up (i.e. "crashes") during bootloader sequence, requiring a hard reset, and upon second boot, finally Powers On and boots properly, bringing up a functional session of the Main User Interface. This is repeatable, and consistent.


Bug Symptoms & How To Repeat:

1. Consistently the Player will lock up during first "boot" sequence. The bootloader will usually reach the text stage, and sometimes crash here. Sometimes the bootloader will get through the text stage and reach the Rockbox Logo and then crash here. The Main User Interface is never reached upon first "boot" sequence.

2. The result of the first "boot" lockup (i.e. "crash") requires that I reset the Player by inserting a paperclip into the Reset hole (on the bottom plate of the Player) and triggering the button hidden in there. This Powers Down the Player, and Resets the Firmware, leaving the Player ready to be Powered On again.

3. Upon the second "boot", the Player will "boot" and the bootloader will make it past the text stage, the Rockbox Logo stage, and then spin up the HDD properly; the bootloader will not lock up the firmware, and behaves 'normally', finally resulting in a completed boot up sequence with the Main User Interface coming up (as a user would expect). The Player is now ready to use.
This task depends upon

Comment by Frank Gevaerts (fg) - Friday, 19 October 2012, 08:15 GMT
Which bootloader version are you using?
Comment by MichaelGiacomelli (saratoga) - Friday, 19 October 2012, 16:31 GMT
Does it work with the players original drive?
Comment by Dominik Riebeling (bluebrother) - Friday, 19 October 2012, 17:16 GMT
What behaviour do you observe when downgrading to the old version you've been using? Which version did you use before? Have you checked the filesystem for errors? If not please do so and check if the problem persists.
Comment by Leo H. (FLACvest) - Friday, 19 October 2012, 18:49 GMT
Reply to (fg): Bootloader Version: 7-pre4

Reply to (saratoga): I DO have the original 40 GB Toshiba MK4004GAH drive, and I will test it today, and report back.

Reply to (bluebrother): I was using Rockbox version 3.11 before. I will check the filesystem for errors on the current 3.12 installation, then downgrade, and check to see what the behavior is like, and report back.

Comment by Justin (xabba) - Monday, 05 November 2012, 23:53 GMT
I wanted to add that I am experiencing the exact same issue with my H140. I have the original hard drive in mine. It seems to me like a combination of the v7pre4 bootloader and the v3.12 firmware. I had upgraded the firmware first and did not have any problems. After upgrading the bootloader from v6, and then flashing the firmware RAM and ROM images did the issue appear. I downgraded the disk, RAM and ROM firmware to v3.11.2 and the issue no longer occurs. I hope this helps!
Comment by Leo H. (FLACvest) - Thursday, 03 January 2013, 00:09 GMT
I just noticed a behavior change:

I was getting some system messages ".rockbox directory not found" then the message "incomplete installation", when loading rockbox firmware from: RAM or ROM rather than DISK from the HOLD SWITCH bootup screen...

Sometimes it would also appear when booting from DISK, however; it was always happening from loading via RAM or ROM.

Furthermore, after flashing "Files > /.rockbox/rockbox.iriver" to RAM via ' a long-press > Open With... > iriver_flash ' with rockbox.iriver file selected, and completing the on-screen instruction to flash to RAM Image,
and also doing the same to the file "Files > /.rockbox/rombox.iriver" to RAM via ' a long-press > Open With... > iriver_flash ' with rombox.iriver file selected, and completing the on-screen instruction to flash to ROM Image,
then afterward, shutting down, booting via HOLD SWITCH boot menu to first load firmware via ROM, shut down, and repeat with loading firmware via RAM, and repeat, but this time using REC to set default load from DISK,

I have been able to load from DISK repeatedly AS NORMAL without the errors. I don't know if having the same VERSION of the rockbox firmware written to the ROM and RAM and DISK sections is what helps the problem, or if having different versions (using rockbox 3.12) causes an error with the bootloader version 7-pre4.

This is currently now working normally for my on my H140. My H120 is having a (possibly hardware related issue) that makes it unsuitable to confirm this information with on a second unit, unfortunately.

Perhaps someone else having this issue could try what I did and mention and see if 3.12 will work for them now?
Comment by Sascha L├╝decke (Moxon) - Tuesday, 26 March 2013, 22:00 GMT
I can second the experience initially described in the bug. It is working fine with 3.11.2 but it does not work with 3.12 or 3.13.

For me, every second boot works fine and every other boot hangs on the Rockbox start screen (which shows the logo and the version) and I have to hard reset the device.

Device Information:

Bootloader v7-pre4
iRiver iHP-120
CF MOD with 32GB CF card

I highly appreciate any fixes for this because I am stuck with 3.11.2 right now.
Comment by Joaquim Dias (dunno) - Saturday, 06 July 2013, 04:58 GMT
I have had the same bug as stated above with rockbox v 3.12 and v3.13.

My H140 is stock standard original with no mods.
If I don't flash to RAM/ROM and boot sequence is set to disk the boot up will only freeze upon the first boot after rolo, thereafter it will boot normally. But, If I flash to RAM and ROM with the same firmware the player will hang during bootup irrespective of boot sequence set.