For me the most important one is the possibility to handle the startup
with my
non-LCD remote...
That works fine with the bootloader I'm using, (r14938M).
That's another reason to release an updated bootloader version ;)
regards,
Matthias (aka Massa)
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
For me the most important one is the possibility to handle the startup
with my
non-LCD remote...
That works fine with the bootloader I'm using, (r14938M).
pondlife
On Wed, 9 Apr 2008, Matthias Mohr wrote:
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
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
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
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
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.
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 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
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 *might* be an issue with petur's device rather than a
On Mon, 7 Apr 2008, Peter D'Hoye wrote:
Maybe I can abuse Linus to test changes on his BDM equipped player ;)
Hey, that's not abuse, that's our regular use! ;-)
--
Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/
On Mon, Apr 7, 2008 at 11:45 AM, pondlife [EMAIL PROTECTED] wrote:
you'd have to try current svn to be really sure though...
the svn version at the time of devcon07 booted 50% of the time, the
newer
ones less, so the behaviour changes with revisions
Sure, I'll give it a go tonight,
On Mon, Apr 7, 2008 at 12:18 AM, Daniel Dalton [EMAIL PROTECTED] wrote:
That is the problem. You can't reanimate a bricked h300 without special
equipment.
What equipment is needed? And what is the process of unbricking a h300?
Is it a long and complicated process...?
You need to access
Hi Daniel,
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 lot of things have been fixed
Matthias Mohr wrote:
Unfortunately it seems that only Linus is able to do this - and it seems
he doesn't have enough time or isn't in the mood to do it...
The thing is that the current SVN bootloader still has issues with some
hard drives, and I don't want to release a bootloader that doesn't
Unfortunately it seems that only Linus is able to do this - and it
seems
he doesn't have enough time or isn't in the mood to do it...
The thing is that the current SVN bootloader still has issues with some
hard drives, and I don't want to release a bootloader that doesn't work.
Hi Linus,
The thing is that the current SVN bootloader still has issues with some
hard drives, and I don't want to release a bootloader that doesn't work.
And the released bootloader don't have this issues?
- If they also have the issues, the SVN bootloader should still be better than
the
Matthias Mohr wrote:
If the risk of bricking my device isn't big (or if it's possible for me
to reanimate a bricked H300) I would try to put a current SVN version of the
bootloader on my device...
That is the problem. You can't reanimate a bricked h300 without special
equipment.
Linus
If the risk of bricking my device isn't big (or if it's possible for me to
reanimate
a bricked H300) I would try to put a current SVN version of the bootloader
on my device...
I wouldn't say that the risk is very high, but it is there. In the past I
tried to enable H110 flashing so I had to
On Sun, 6 Apr 2008, XavierGr wrote:
On a side note:
Last working svn bootloader I built for me and about 7 (IIRC) people, was
r14945 (with added alarm support).
Does that revission contain any bugs what so ever in the bootloader code?
Like does it work with all the different hard drives or
On Sun, 6 Apr 2008, Matthias Mohr wrote:
Hi Linus,
The thing is that the current SVN bootloader still has issues with some
hard drives, and I don't want to release a bootloader that doesn't work.
And the released bootloader don't have this issues?
- If they also have the issues, the SVN
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 introduced?
If it worked fine for
I have an iriver h320, do I build the bootloader from source like this?
../tools/configure
11
b
make
Or does make want a special argument?
Then what is the output file called?
And then do I just need to patch this file into an iriver firmware?
Is it safe currently to build the bootloader from
24 matches
Mail list logo
