Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12747 Discussions

problem with mkimage from u-boot

Altera_Forum
Honored Contributor II
1,512 Views

Hello, 

 

I downloaded the u-boot version from http://www.psyent.com/download/ (http://www.psyent.com/download/) and did the following and build the EP1C20_config. After make i got the u-boot.bin image and uploaded it. u-boot is working. 

 

So now i want to upload the nios2linux-1.4 kernel image i created. for this i gzip'd the vmlinux.bin image file and got vmlinux.bin.gz. Now i tried to run mkimage but i got: command not found... 

So i looked into the u-boot tools folder and found the uncompiled mkimage source. 

I renamed Makefile.win32 to Makefile and entered make: 

/cygdrive/d/altera/u-boot-src/u-boot/tools $ make gcc -g -Wall -pedantic -I../include -I.. -D__WIN32__ -O -c crc32.c In file included from crc32.c:12: ../include/common.h:108: warning: ANSI C does not allow macro with variable arguments ../include/common.h:109: warning: ANSI C does not allow macro with variable arguments In file included from crc32.c:12: ../include/common.h:571: warning: ANSI C does not allow macro with variable arguments crc32.c:174: too many `l's in integer constant make: *** Error 1 /cygdrive/d/altera/u-boot-src/u-boot/tools 

 

How can i compile mkimage or where can i get the compiled one? 

 

I'm using Quartus II 5.0 and the NIOS II IDE with nios2linux-1.4. 

 

Thanks for you help, 

Tobias
0 Kudos
1 Reply
Altera_Forum
Honored Contributor II
669 Views

Hi Tobias, 

 

> How can i compile mkimage or where can i get the compiled one? 

 

You can get the pre-built binary here: 

 

http://www.psyent.com/download/u-boot-mkimage-bin.zip (http://www.psyent.com/download/u-boot-mkimage-bin.zip

 

Or, you can port the code to cygwin. The mkimage sources in the u-boot source 

tree won't build properly under the nios2 cygwin (as you have already discovered). 

That's why the tools tree is not included in the default make target from psyent. 

 

Or, if you work on a linux host ... you can just add the tools tree back into the 

default make target. It'll build under linux just fine. 

 

If I can ever find the mkimage sources that were already ported, I'll add it in to the 

u-boot source tree at psyent. But it is *highly* unlikely it will ever make it into the 

main u-boot git repository. 

 

Regards, 

--Scott
0 Kudos
Reply