"mkimage" not found
Hi,
I have just downloaded the new ELDK 3.0 installed and compiled for the EST8260 board.
With the previous ELDK2.0 I would have generated the image with the "make pImage" command while now I suppose the command "make uImage" must be used. Is this correct?
Then at the end of compilation process, I have the following message:
"mkimage" not found - U-boot Images will not be built.
I have checked the presence of mkimage as executable file (which exist because prior to compile the linux tree I have generate the U-boot executable) and its functionality (by calling it directly without script). Anybody has an idea where I am wrong?
Thanks
Gianfranco
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 4 lines · In message <00a101c401d4$26140fc0$0400a8c0@portatile> you wrote:
With the previous ELDK2.0 I would have generated the image with the "make pImage" command while now I suppose the command "make uImage" must be used. Is this correct?
This is correct, but "make pImage" will still work, too.
Quoted 2 lines
Then at the end of compilation process, I have the following message:
"mkimage" not found - U-boot Images will not be built.
The "mkimage" should be in your PATH when using the ELDK - it gets installed in /opt/eldk/usr/bin/
Quoted 1 line
Anybody has an idea where I am wrong?
Maybe your PATH ist not correct?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: [email protected] Felson's Law:
To steal ideas from one person is plagiarism; to steal from many is research.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Dear Wolfgang
Quoted 1 line
Maybe your PATH ist not correct?
You are perfectly right! I didn't add the line "export PATH=$PATH:/opt/eldk/usr/bin" to .bashrc. Many thanks
Quoted 1 line
Quoted 1 line
With the previous ELDK2.0 I would have generated the image with the
"make
Quoted 1 line
Quoted 1 line
pImage" command while now I suppose the command "make uImage" must be
used.
Quoted 3 lines
Quoted 1 line
Is this correct?
This is correct, but "make pImage" will still work, too.
unfortunately I had the following messages:
[gianfranco@home001 linux]$ make pImage
make: *** No rule to make target `pImage'. Stop. [gianfranco@home001 linux]$ grep -r pImage * arch/ppc/boot/Makefile:pImage: $(MKIMAGE) images/vmlinux.gz [gianfranco@home001 linux]$ grep -r uImage * arch/ppc/boot/Makefile:uImage \arch/ppc/boot/Makefile: ln -sf vmlinux.UBoot images/uImage arch/ppc/Makefile:BOOT_TARGETS = zImage zImage.initrd znetboot znetboot.initrd uImage
CHANGELOG:Add support for U-Boot boot image "uImage" [gianfranco@home001 linux]$
Should I modify BOOT_TARGET into arch/ppc/Makefile?
Best regards
Gianfranco
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Dear Gianfranco,
Quoted 4 lines · in message <00a101c40291$c31a7120$0400a8c0@portatile> you wrote:
Quoted 2 lines
Maybe your PATH ist not correct?
You are perfectly right! I didn't add the line "export
Thanks for the confirmation.
Quoted 2 lines
[gianfranco@home001 linux]$ make pImage
make: *** No rule to make target `pImage'. Stop.
...
Quoted 1 line
Should I modify
BOOT_TARGETintoarch/ppc/Makefile?
As you like. Maybe it's better to get used to the U-Boot image name.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: [email protected] There is is no reason for any individual to have a computer in their
home. -- Ken Olsen (President of Digital Equipment Corporation),
Convention of the World Future Society, in Boston, 1977
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AFAIK, uImage target does not exist for all linuxppc sources. I got my kernel sources from PenguinPPC bitkeeper so it does not have it. I just build vmlinux target and use the following steps to generate uImage (which is documented in U-Boot documentation)
(taken from my shell script that automates this stuff)
${CROSS_COMPILE}objcopy -O binary -R .note -R .comment -S vmlinux vmlinux.bin gzip -9 vmlinux.bin
$MKIMAGE -n "Linux Image" -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
-d vmlinux.bin.gz" uImage
Quoted 32 lines
Dear Wolfgang
Quoted 1 line
Maybe your PATH ist not correct?
You are perfectly right! I didn't add the line "export PATH=$PATH:/opt/eldk/usr/bin" to .bashrc. Many thanks
Quoted 1 line
Quoted 1 line
With the previous ELDK2.0 I would have generated the image with the
"make
Quoted 1 line
Quoted 1 line
pImage" command while now I suppose the command "make uImage" must be
used.
Quoted 3 lines
Quoted 1 line
Is this correct?
This is correct, but "make pImage" will still work, too.
unfortunately I had the following messages:
[gianfranco@home001 linux]$ make pImage
make: *** No rule to make target `pImage'. Stop. [gianfranco@home001 linux]$ grep -r pImage * arch/ppc/boot/Makefile:pImage: $(MKIMAGE) images/vmlinux.gz [gianfranco@home001 linux]$ grep -r uImage * arch/ppc/boot/Makefile:uImage \arch/ppc/boot/Makefile: ln -sf vmlinux.UBoot images/uImage arch/ppc/Makefile:BOOT_TARGETS = zImage zImage.initrd znetboot znetboot.initrd uImage
CHANGELOG:Add support for U-Boot boot image "uImage" [gianfranco@home001 linux]$
Quoted 7 lines
Should I modify
BOOT_TARGETintoarch/ppc/Makefile?Best regards
Gianfranco
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/