Rockbox Technical Forums

Installation / Removal => Manual Installation => Iriver - Installation/Removal/Flashing => Topic started by: Mr_Rabid_Teddybear on January 12, 2011, 06:47:01 PM

Title: Current status of H300 bootloader?
Post by: Mr_Rabid_Teddybear on January 12, 2011, 06:47:01 PM
I have a H340 with a functional v5 bootloader. The boot USB mode is a bit volatile but the device boots OK. I see that the v6 bootloader release doesn't seem to be around the corner anytime soon and reading some other posts it seems that some (several?) people have got a bit in a stick trying to use bootloader freshly compiled from SVN. So I should probably just stick with the bootloader I have on already I guess? But I just wondered if someone have some info on surrounding matters as of primo 2011...?

Title: Re: Current status of H300 bootloader?
Post by: Llorean on January 12, 2011, 10:02:46 PM
Is there actually a problem with the V5 bootloader that needs fixing? Has a bug report been filed?
Title: Re: Current status of H300 bootloader?
Post by: AlexP on January 14, 2011, 03:22:09 AM
H300 bootloaders in SVN are broken, DO NOT USE ONE as you will brick your player. You will not be able to recover it without specialist hardware.
Title: Re: Current status of H300 bootloader?
Post by: galapogos01 on January 19, 2014, 12:36:57 AM
I found via trial and error that you can recover a SVN/GIT bricked H300.  To recover it, I hard-reset the device with HOLD enabled and a DC charger plugged in (this was found via trial and error in a desperate attempt to bring it back to life).

There are a few feature requests for the H300 (inc auto-boot & charge w/ USB input) that would be nice to have.  There are several patches around for similar functions but they can't be used due to no source for a working bootloader.

Cheers,
Jason
Title: Re: Current status of H300 bootloader?
Post by: gevaerts on January 19, 2014, 02:52:08 PM
I found via trial and error that you can recover a SVN/GIT bricked H300.  To recover it, I hard-reset the device with HOLD enabled and a DC charger plugged in (this was found via trial and error in a desperate attempt to bring it back to life).

That may have worked for you in one specific case, but it's not a general way to recover.
Title: Re: Current status of H300 bootloader?
Post by: wodz on January 19, 2014, 04:07:06 PM
From my experience with MPIOs (very similar platform and codebase) this IS general way unless 1) reset vector is screwed up 2) bootloader crashes early enough to not check cookie presence. The bootloader checks if there is specific value at some iram address to judge if it crashed previously or not (see crt0.S line 166 and below).