Rockbox mail archiveSubject: Re: building bootloader from source (h300)
Re: building bootloader from source (h300)
From: Nils <deathtoallhumans_at_gmail.com>
Date: Tue, 8 Apr 2008 17:01:40 +0200
On Tue, Apr 8, 2008 at 9:20 AM, Daniel Dalton <d.dalton_at_iinet.net.au> wrote:
> On Mon, 7 Apr 2008, Nils wrote:
> Is there a way to extract a usable copy of the existing bootloader first?
> > > Having changed PCs I've misplaced both the h300.hex file and the list
> > > of
> > > which modifications I included.
> > >
> > > pondlife
> > >
> > >
> > > "Dump ROM contents" creates a 4MiB bin file in the root, just
> > scramble it
> > again and the of should be able to flash it.
> Oh so I just get the bin file and basically use the instructions on the
> wiki to create a new hex file? That will work just like before?
> And it will support the dual boot and alarm and everything?
That bin file will contain the image that is currently flashed in your
player (Original firmware patched with rockbox bootloader). Yes you can
scramble it and flash it again providing you can start the original
firmware. If you want to patch in a new bootloader the old one can probably
be removed from the image and replaced with a new one but there are no
automatic tools for this (and doing it manually comes with the same risk as
using an untested bootloader). Looking at mkboot.c could give some clues
though, that said I don't know why you would want to do this (I might have
misunderstood). It would be much easier/safer to get a fresh .hex file and
Received on 2008-04-08