How to make a uImage....

[fastrobot]

Hi,

I've been hacking on the Glo.
It's zForce-ir-touch driver is buggy, and gives wildly wrong timestamps because of a timer error and misses a certain number of short touches because of the bug.

The zForce-ir-touch driver in the AuraHD was patched by someone to fix the timer bug and works pretty well. I'm not sure it's an optimal solution, but it's a good enough solution which doesn't require any new kernel symbols (it's a self cotained fix).

SO -- I want to move the HD's fix over to my Glo...

Unfortunately, the zForce driver is compiled as built-in driver and not as a module -- so I must recompile and reinstall the whole kernel rather than just make a module. sigh.
I know how to make modules work.... I don't know how to do uboot stuff, and don't really want to fight this....

I replaced the zForce_i2c.c driver source code in the Glo Kernel directly from KoboLabs,
and to make sure I get a message in the kernel log, I replaced the zforce's printk Boot complete message with a printk Patched Boot complete message.

Then I recompiled the kernel using KoboLabs C compilers from the repository; ( make arch=arm CROSS_COMPILE=arm_none_linux-gnueabi- )

No problems. I find a Image, zImage, and uImage file in the kernel tree after it's built.
and install the uimage in a variety of ways, but the new message doesn't printk. So, I delete uImage from the kernel tree and remake -- and to my disgust uImage is not remade, so it's was a stale binary.

when I try to "make uImage", it complains that a mkimage command is not found, U-Boot images will not be built.

So -- I realize I have to install u-boot, and I do that.
For the Glo it exists, and is pre-compiled; but I have no idea what it is compiled for...-- but for the Aura-HD, It is not compiled at all....

I can recover my SD card if I hard brick it, but I'd rather not do a lot of trial and error.
The kenel now makes a uImage when I say make uImage -- but does anyone know if the make file in the Glo's linux kernel is already correctly configured to make a uImage, or do I have to do anything special to make a proper uImage?

How do I get the proper load addresses, etc, for the image if I need them?

Eg: do I have to install both a uImage and complie some specific u-boot-bin, or can I just use the old u-boot-bin from the kobo-update package, and just replace the Kobo-Glo's uImage ?

How is it normally done?

(EDIT: I installed the uImage made by the kernel make file, and left the old uboot.bin --- and my Kobo Glo did successfully boot the new kernel. So... thankfully it was preconfigured right, but I still don't know how to make the uboot package for the AuraHD if I need it in the future....)

[NiLuJe]

I'm guessing you need u-boot-tools on your host .

equery f u-boot-tools                                                                                                                                   
 * Searching for u-boot-tools ...
 * Contents of dev-embedded/u-boot-tools-2015.04:
/etc
/etc/fw_env.config
/usr
/usr/bin
/usr/bin/bmp_logo
/usr/bin/easylogo
/usr/bin/fw_printenv
/usr/bin/fw_setenv -> fw_printenv
/usr/bin/gen_eth_addr
/usr/bin/img2srec
/usr/bin/mkimage
/usr/lib
/usr/lib/debug
/usr/lib/debug/usr
/usr/lib/debug/usr/bin
/usr/lib/debug/usr/bin/bmp_logo.debug
/usr/lib/debug/usr/bin/easylogo.debug
/usr/lib/debug/usr/bin/fw_printenv.debug
/usr/lib/debug/usr/bin/gen_eth_addr.debug
/usr/lib/debug/usr/bin/img2srec.debug
/usr/lib/debug/usr/bin/mkimage.debug
/usr/share
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/mkimage.1