problem compiling bootloader for H340 on linux, SYSFONT_WIDTH undeclared

[luissifer]

Hi there,

I'm trying to compile the bootloader for a iriver H340.
Everything seems fine until I try to "make", then I get this error:

CC firmware/panic.c
/home/louis/rockbox/firmware/panic.c: In function `panicf':
/home/louis/rockbox/firmware/panic.c:68: error: `SYSFONT_WIDTH' undeclared (first use in this function)
/home/louis/rockbox/firmware/panic.c:68: error: (Each undeclared identifier is reported only once
/home/louis/rockbox/firmware/panic.c:68: error: for each function it appears in.)
make: *** [/home/louis/rockbox/build/firmware/panic.o] Error 1

It looks like SYSFONT_WIDTH is defined in convbdf.c which is not included at this point of the compiling. Is it normal??
Any ideas??

Thanks!

[Llorean]

It's really not a good idea to compile your own bootloader for that player. Why are you attempting it?

[nls]

SYSFONT_WIDTH is defined in sysfont.h which is generated while building. I tried compiling a h300 bootloader with a clean chaeckout here and it works fine so there is likely something wrong with either your build environment or your source checkout.

BUT as llorean said it is generally a bad idea to build this bootloader yourself as there's a significant risk of bricking your player if you install it

[luissifer]

Thanks for your replies,
I am trying to compile a boot loader so that I can try to apply this patch
 FS#9202 - iriver H300 bootloader power/usb fixes
http://forums.rockbox.org/index.php?topic=17202.0

Hopefully I'll be able to play songs while the player is charging ion the USB port. I use it in my car quite a lot and it is a bit annoying to not be able to play music when the battery is flat and it is charging...

[lwizard]

I also need that patch (bootloader_v2).
For USB charching you can hold a-b while plugging, or simply patching rockbox software with another patch for USB charging by default (I have done it).

But I need rockbox to start when the player is off and my car turn on and power it and not going in charging mode.

Please can you compile it for us with that patch or explain us how to do that, point by point?

Thanks a lot!

[Llorean]

As I said, there is a very real chance of custom compiled bootloaders bricking these players. You should not try using a bootloader you compile yourself unless you have a way to recover a bricked H300.

[luissifer]

Thanks for your comments.

I didn't know about the A-B hold while plugging in, that's quite useful!
But yeah it will be nice to have this possibility to get into usb charging mode but not in transfer mode when you start the player as well.
Let me know lwizard, if you get any success compiling the bootloader.
I must have some problems with my environment as I can't manage to compile either normal or just the bootloader...

Okay it sounds risky to compile the bootloader but isn't it still possible to replace the hex file by a functioning one if there are any issues??

Cheers

[nls]

Okay it sounds risky to compile the bootloader but isn't it still possible to replace the hex file by a functioning one if there are any issues??

Short answer: No, flash a non working bootloader and your player is bricked.
Long answer: it's _possible_ with a specialised piece of hardware known as a BDM wiggler and some soldering and of course the skills to use that hardware.

[luissifer]

ah okay, interesting comment!
thanks for that

[GodEater]

Just to clarify here :

This is why we get a little annoyed with people on our forums referring to their players as "bricked", when in reality they really aren't. For a great deal of the players that Rockbox runs on, it's not possible to brick them by installing bad bootloaders or bad rockbox builds - there's always a way to recover them, therefore the player was never bricked in the first place. Just because you can't currently load the original firmware on it, or Rockbox, does not mean it is bricked.

The H3xx and H1xx iRiver players are however entirely possible to break so badly you CANNOT fix them without having to open them up, connect them to some *very* specialist hardware (that costs a lot of money), AND have the smarts to *use* that hardware. *That* is properly bricked.

Therefore we really, really urge people NOT to build and use their own bootloaders for either of these players. The only people qualified to do so are the very small number of developers who own the recovery hardware I mentioned above in case of a failure.