Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Altera_Forum
Honored Contributor I
775 Views

How to create uImage for SoCrates (EBV) board?

After executing the build process (bitbake altera-gsrd-image) I cannot find an uImage file for uBoot. 

I try to create uImage using 

root@ubuntu:/home/hitex/soc_1# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "SoC FPGA 2015.01.21" -d zImage uImage 

Image Name: SoC FPGA 2015.01.21 

Created: Wed Jan 21 03:16:36 2015 

Image Type: ARM Linux Kernel Image (uncompressed) 

Data Size: 3202816 Bytes = 3127.75 kB = 3.05 MB 

Load Address: 0x00008000 

Entry Point: 0x00008000 

and replaced this uImage on the original SD card content. The image will be loadad and the last visible message in terminal is "Starting kernel ...":  

 

U-Boot SPL 2013.01.01 (Jan 24 2014 - 11:22:14) 

BOARD : SoCrates Cyclone V-SoC Board 

SDRAM: Initializing MMR registers 

SDRAM: Calibrating PHY 

SEQ.C: Preparing to start memory calibration 

SEQ.C: CALIBRATION PASSED 

ALTERA DWMMC: 0 

 

 

U-Boot 2013.01.01 (Jan 24 2014 - 11:26:34) 

 

CPU : Altera SOCFPGA Platform 

BOARD : SoCrates Cyclone V-SoC Board 

DRAM: 1 GiB 

MMC: ALTERA DWMMC: 0 

In: serial 

Out: serial 

Err: serial 

Net: mii0 

Hit any key to stop autoboot: 0 

3202880 bytes read in 1136 ms (2.7 MiB/s) 

17905 bytes read in 44 ms (396.5 KiB/s) 

# # Booting kernel from Legacy Image at 10000000 ... 

Image Name: SoC FPGA 2015.01.21 

Image Type: ARM Linux Kernel Image (uncompressed) 

Data Size: 3202816 Bytes = 3.1 MiB 

Load Address: 00008000 

Entry Point: 00008000 

# # Flattened Device Tree blob at 00f00000 

Booting using the fdt blob at 0x00f00000 

Loading Kernel Image ... OK 

OK 

Loading Device Tree to 03ff8000, end 03fff5f0 ... OK 

 

Starting kernel ... 

 

The build process has created following files: 

hitex@ubuntu:~/altera-yocto/build_gsrd-image/tmp/deploy/images$ ls -l 

total 483188 

-rw-r--r-- 1 hitex hitex 114673664 2015-01-20 09:01 altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.cpio 

-rw-r--r-- 1 hitex hitex 152550400 2015-01-20 09:01 altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.ext3 

-rw-r--r-- 1 hitex hitex 117637120 2015-01-20 09:03 altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.jffs2 

-rw-r--r-- 1 hitex hitex 56007193 2015-01-20 09:02 altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.tar.gz 

lrwxrwxrwx 1 hitex hitex 61 2015-01-20 09:01 altera-gsrd-image-socfpga_cyclone5.cpio -> altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.cpio 

lrwxrwxrwx 1 hitex hitex 61 2015-01-20 09:01 altera-gsrd-image-socfpga_cyclone5.ext3 -> altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.ext3 

lrwxrwxrwx 1 hitex hitex 62 2015-01-20 09:03 altera-gsrd-image-socfpga_cyclone5.jffs2 -> altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.jffs2 

lrwxrwxrwx 1 hitex hitex 63 2015-01-20 09:02 altera-gsrd-image-socfpga_cyclone5.tar.gz -> altera-gsrd-image-socfpga_cyclone5-20150120131804.rootfs.tar.gz 

-rw-r--r-- 1 hitex hitex 3379224 2015-01-20 08:42 modules-3.9.0-r1-socfpga_cyclone5.tgz 

-rw-r--r-- 1 hitex hitex 294 2015-01-20 08:59 README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt 

lrwxrwxrwx 1 hitex hitex 46 2015-01-20 08:43 vmlinux -> vmlinux-1.0-r1-socfpga_cyclone5-20150120131804 

-rw-r--r-- 1 hitex hitex 76221877 2015-01-20 08:42 vmlinux-1.0-r1-socfpga_cyclone5-20150120131804 

lrwxrwxrwx 1 hitex hitex 49 2015-01-20 08:42 zImage -> zImage-1.0-r1-socfpga_cyclone5-20150120131804.bin 

-rw-r--r-- 1 hitex hitex 3202816 2015-01-20 08:42 zImage-1.0-r1-socfpga_cyclone5-20150120131804.bin 

-rw-r--r-- 1 hitex hitex 3202816 2015-01-20 06:45 zImage-3.9.0 

lrwxrwxrwx 1 hitex hitex 49 2015-01-20 08:43 zImage-socfpga_cyclone5.bin -> zImage-1.0-r1-socfpga_cyclone5-20150120131804.bin 

 

I have also checked the content of rootfs and I see another content as on the original SD card content. No uImage exists in /boot folder. Only zImage-3.9.0 is available (same content as my zImage). 

I have created also an own SD card content using the generated files and the original uImage and this is also working. So I have located my problem in the generated uImage file. 

 

 

Please help me to create a working uImage!
0 Kudos
0 Replies
Reply