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++
12627 Discussions

building problem - toolchain

Altera_Forum
Honored Contributor II
1,253 Views

Your kernel directory 'linux-2.6.x' lacks a vmImage file: 

/home/z125188/nios2-linux/uClinux-dist/linux-2.6.x/arch/nios2/boot/vmImage 

This usually means your toolchain lacks u-boot tools. Please check your 

toolchain installation. The file is generated when running 'make linux'. 

 

how do i check my toolchain installation? :/ 

 

0 Kudos
5 Replies
Altera_Forum
Honored Contributor II
369 Views

In normal nios2nommu build, mkimage is not needed. You should use "make" once to build everything. 

 

Only if you are using "trunk" branch of uClinux-dist, it will need mkimage. mkimage is available from u-boot, you can either install it or build it. 

 

1. for ubuntu/debian, apt-get install uboot-mkimage 

 

2. cd nios2-linux/toolchain-build 

make u-boot 

# then move the mkimage to your toolchain binary dir in your PATH. 

 

- Hippo
0 Kudos
Altera_Forum
Honored Contributor II
369 Views

<div class='quotetop'>QUOTE (hippo @ Aug 24 2009, 08:17 PM) <{post_snapback}> (index.php?act=findpost&pid=23567)</div> 

--- Quote Start ---  

In normal nios2nommu build, mkimage is not needed. You should use "make" once to build everything. 

 

Only if you are using "trunk" branch of uClinux-dist, it will need mkimage. mkimage is available from u-boot, you can either install it or build it. 

 

1. for ubuntu/debian, apt-get install uboot-mkimage 

 

2. cd nios2-linux/toolchain-build 

make u-boot[/b] 

--- Quote End ---  

 

 

Those steps worked fine but i still get the same error. 

 

I want to try nios2 with MMU 

without it worked fine and i build a lot of zImages but the MMU stuffs not working. 

 

 

do i have to move the "mkimage" binary or just add the path to the PATH variable? 

i tried adding it with PATH=$PATH:/home/xyz/nios2-linux/toolchain-build/u-boot/tools 

 

 

mfg Sven 

0 Kudos
Altera_Forum
Honored Contributor II
369 Views

<div class='quotetop'>QUOTE </div> 

--- Quote Start ---  

WARNING: modpost: Found 4 section mismatch(es). 

To see full details build your kernel with: 

&#39;make CONFIG_DEBUG_SECTION_MISMATCH=y&#39; 

GEN .version 

CHK include/linux/compile.h 

UPD include/linux/compile.h 

CC init/version.o 

LD init/built-in.o 

LD .tmp_vmlinux1 

KSYM .tmp_kallsyms1.S 

AS .tmp_kallsyms1.o 

LD .tmp_vmlinux2 

KSYM .tmp_kallsyms2.S 

AS .tmp_kallsyms2.o 

LD vmlinux 

SYSMAP System.map 

SYSMAP .tmp_System.map 

OBJCOPY arch/nios2/boot/vmlinux.bin 

GZIP arch/nios2/boot/vmlinux.gz 

UIMAGE arch/nios2/boot/vmImage 

/usr/bin/mkimage [OPTIONS] 

 

Options: 

-f <MD5 name> Specify an input MD5 file. MD5s must be in jigdo&#39;s 

pseudo-base64 format 

-j <jigdo name> Specify the input jigdo file 

-t <template name> Specify the input template file 

-m <item=path> Map <item> to <path> to find the files in the mirror 

-M <missing name> Rather than try to build the image, just check that 

all the needed files are available. If any are missing, 

list them in this file. 

-v Make the output logging more verbose 

-l <logfile> Specify a logfile to append to. 

If not specified, will log to stderr 

-o <outfile> Specify a file to write the ISO image to. 

If not specified, will write to stdout 

-q Quick mode. Don&#39;t check MD5sums. Dangerous! 

-s <bytenum> Start byte number; will start at 0 if not specified 

-e <bytenum> End byte number; will end at EOF if not specified 

-z Don&#39;t attempt to rebuild the image; simply print its 

size in bytes 

Kernel: arch/nios2/boot/vmImage is ready 

Building modules, stage 2. 

MODPOST 0 modules 

make[1]: Verlasse Verzeichnis &#39;/home/z125188/nios2-linux/linux-2.6&#39; 

if [ -f linux-2.6.x/vmlinux ]; then  

ln -f linux-2.6.x/vmlinux linux-2.6.x/linux ;  

fi[/b] 

--- Quote End ---  

 

 

why is he telling me the vmImage is ready when there is none ? :/ 

 

 

 

0 Kudos
Altera_Forum
Honored Contributor II
369 Views

<div class='quotetop'>QUOTE (SvenHe @ Aug 25 2009, 04:15 PM) <{post_snapback}> (index.php?act=findpost&pid=23585)</div> 

--- Quote Start ---  

I want to try nios2 with MMU[/b] 

--- Quote End ---  

 

 

The nios2 linux with MMU is under final testing and will be opened for the public soon. Please wait. 

 

- Hippo
0 Kudos
Altera_Forum
Honored Contributor II
369 Views

I don't want to update this message. But it seems to me that it is related to my issue. After i compiled the kernel, I got this message. 

 

Image Name: Linux-3.7.0-01377-g1061bd7 

Created: Mon Mar 25 15:41:30 2013 

Image Type: NIOS II Linux Kernel Image (gzip compressed) 

Data Size: 1445018 Bytes = 1411.15 kB = 1.38 MB 

Load Address: c8000000 

Entry Point: c8000000 

Kernel: arch/nios2/boot/vmImage is ready 

 

Configuring .sof files works smoothly but i could not download vmImage file: 

 

rootF15: /path/nios2-download vmImage 

nios2-elf-objcopy:./vmImage: File format not recognized 

./vmImage.srec: Unable to open input file 

rm: cannot remove `./vmImage.srec': No such file or directory 

 

Have anybody encountered with this problem ? How to obtain zImage ?
0 Kudos
Reply