Hi Daniel,
it would still be nice to have solved some of the problems in the released
bootloader.
What issues are there currently?
Look at http://www.rockbox.org/twiki/bin/view/Main/IriverBoot#H320_H340
There is a table with known issues and other TODOs and which already have
been fixed /
On Wed, 9 Apr 2008, XavierGr wrote:
Because I lost my .hex file for the alarm... (alarm support in the
bootloader...) so it can wakeup the player.
If you want I can send you my known-working bootloader.
Yes please. Could you also send along a sha1 check sum?
And will this be a hex file patc
> Because I lost my .hex file for the alarm... (alarm support in the
> bootloader...) so it can wakeup the player.
If you want I can send you my known-working bootloader.
On Tue, 8 Apr 2008, Nils wrote:
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
Because I lost my .hex file for the alarm... (alarm support in the
bootloader...) so it can wakeup the player.
Hey
I and Linus wouldn't mind setting it up again in Sweden. Is there anyone who
who'd rather *arrange* it someplace else? If so I think it is about time to
speak up so that we can get a date set and get moving!
Note that I'm not asking where people want to go, but where there are people
will
Hi all.
I read from:
http://www.rockbox.org/twiki/bin/view/Main/HowtoWritePlugins
that:
"Some button handling, and a check for USB being plugged in while the
plugin is running. The default_handler() call on unhandled events should
be put in all code that handles button input."
OK, so a plug-in s
On Tue, Apr 8, 2008 at 9:20 AM, Daniel Dalton <[EMAIL PROTECTED]> 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
On Sun, 6 Apr 2008, Matthias Mohr wrote:
Also, if the svn has a bug in the bootloader, it can make your target
unbootable even if it's not your fault. That's why Rockbox "releases"
bootloader.
The last "released" H300 bootloader is from july, 2006!
Regarding the TODO list at the above page, a
On Mon, 7 Apr 2008, XavierGr wrote:
On 07/04/2008, Daniel Dalton <[EMAIL PROTECTED]> wrote:
On Sun, 6 Apr 2008, XavierGr wrote:
Does that revission contain any bugs what so ever in the bootloader code?
Like does it work with all the different hard drives or whatever?
Or has this bug been int
On Mon, 7 Apr 2008, Linus Nielsen Feltzing wrote:
pondlife wrote:
But not for my H300... I have the same 80GB drive as petur (I think, mine's
a Toshiba MK8007GAH), and am happily using r14938M (modified, but I can't
recall how - probably just the RTC alarm now you mention it).
Hmmm, so it *m
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 i
On Mon, 7 Apr 2008, Dominik Riebeling wrote:
What equipment is needed? And what is the process of unbricking a h300?
Is it a long and complicated process...?
You need to access the debug module of the CPU from "outside", i.e.
via hardware. Freescale calls this part of the hardware BDM
(Backg
12 matches
Mail list logo
