Sorry, you need to enable JavaScript to visit this website.

PetaLinux -- Unable to read file uImage

Unsolved
4 posts / 0 new
armendzh's picture
armendzh
Junior(2)
PetaLinux -- Unable to read file uImage

I have AVNET Mini-ITX 7z100 board and I been trying to use PetaLinux to build a linux image.

I am, however, unable to boot the uImage... not from the uImage which I created myself from the BSP files for the same board nor from the pre-built BIN and uImage files provided by AVNET.

Here is an error which I am receiving when trying to boot from SDCARD with BOOT.BIN and image.ub:

//=====================================
U-Boot 2015.04 (Apr 06 2016 - 13:45:26)

DRAM: ECC disabled 1 GiB
MMC: zynq_sdhci: 0
SF: Detected S25FL128S_64K with page size 512 Bytes, erase size 128 KiB, total 32 MiB
In: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Device: zynq_sdhci
Manufacturer ID: 3
OEM: 5054
Name: SL64G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 58.3 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading uimage
** Unable to read file uimage **
U-Boot-PetaLinux> run shboot
## Error: "shboot" not defined
U-Boot-PetaLinux> run sdboot
reading uImage
** Unable to read file uImage **
Unknown command '
setenv' - try 'help'
Unknown command 'softdog.nowayout=0' - try 'help'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
//=====================================

Here are commands which I used ot package my BIN and uImage files (I used both and both failed to boot):

//=====================================
petalinux-package --boot --force --format BIN --fsbl images/linux/zynq_fsbl.elf --fpga images/linux/zynq_design_1_wrapper.bit --u-boot --kernel -o image.ub
petalinux-package --boot --force --format BIN --fsbl images/linux/zynq_fsbl.elf --fpga images/linux/zynq_design_1_wrapper.bit --u-boot
//=====================================

I also have another issue of booting the system (both mine and prebuilt) through JTAG. However, I am not sure if both issues are related (booting via JTAG and via SDcard). Here is what I am getting when trying to boot via JTAG:

//=====================================
INFO: Append dtb - /home/adzh/SBIR_MITX/petalinuxProject/MITX_7100_ED/pre-built/linux/images/system.dtb and other options to boot zImage
INFO: Launching XSDB for file download and boot.
INFO: This may take a few minutes, depending on the size of your image.
rlwrap: warning: your $TERM is 'xterm' but rlwrap couldn't find it in the terminfo database. Expect some problems.: Inappropriate ioctl for device
INFO: Configuring the FPGA...
INFO: Downloading bitstream to the target.

INFO: The XSDB log is as follows
Got $XILINX_SDK: /home/dzhagaryanaa/opt/Xilinx/SDK/2015.2
attempting to launch hw_server

****** Xilinx hw_server v2015.2
**** Build date : Jun 26 2015-16:42:45
** Copyright 1986-1999, 2001-2015 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121

Error in startup script:
No supported FPGA device found
invoked from within
"::tcf::eval -progress ::xsdb::print_progress {::tcf::cache_enter tcfchan#0 {tcf_cache_eval {process_tcf_actions_cache_client ::tcfclient#0::arg}}}"
(procedure "::tcf::cache_eval_with_progress" line 2)
invoked from within
"::tcf::cache_eval_with_progress [dict get $arg chan] [list process_tcf_actions_cache_client $argvar] $progress"
(procedure "process_tcf_actions" line 1)
invoked from within
"process_tcf_actions $arg ::xsdb::print_progress"
(procedure "fpga" line 350)
invoked from within
"fpga "/home/adzh/SBIR_MITX/petalinuxProject/MITX_7100_ED/pre-built/linux/implementation/download.bit""
//=====================================

hockeyman1972's picture
hockeyman1972
Junior(11)
Pulsar vs PetaLinux

From the description of the "softdog.nowayout" in the u-boot parameters, that is indicative of a Pulsar Linux boot, not PetaLinux.  Now how can that possibly happen if you have nothing on your uSD card but a PetaLinux boot.bin and image.ub file?  I'm guessing that someone, not necessarily you, saved environment variables for a Pulsar boot in the QSPI.  If that is the case, then those will override the u-boot parameters in your code, and u-boot will dutifully execute the commands in the saved environment.  Which is a completely different setup than you use for a PetaLinux kernel boot.
If at the very beginning of your execution, you don't see text that indicates a "CRC error, using default environment", then u-boot is definitely using the saved environment.  You can see what is saved by stopping u-boot at the command prompt entering "printenv" at the prompt.
From the u-boot used with a PetaLinux kernel build, you can force it to use your default environment from the u-boot prompt:
env default -a
Then you can clear the environment with:  run eraseenv
Try that and see if that works to get your boot going.
Ron
 

engsci's picture
engsci
Junior(0)
I'm getting the same issue with Petalinux 2016.3

I don't have the 'softdog.nowayout=0' in the same way OP does, but I'm also getting complaints of no image.ub:

-------------------------------------------------------------------
U-Boot 2016.07 (Nov 03 2016 - 19:04:59 +0000)

DRAM: ECC disabled 512 MiB
MMC: sdhci@e0100000: 0
Using default environment

## Error: flags type check failure for "serverip" <= "AUTO" (type: i)
himport_r: can't insert "serverip=AUTO" into hash table
In: serial
Out: serial
Err: serial
Net: ZYNQ GEM: e000b000, phyaddr -1, interface rgmii-id
eth0: ethernet@e000b000
U-BOOT for

ethernet@e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Hit any key to stop autoboot: 0
Device: sdhci@e0100000
Manufacturer ID: 27
OEM: 5048
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
** Unable to read file image.ub **
U-Boot-PetaLinux>

-------------------------------------------------------------------
 
 

JFoster's picture
JFoster
Moderator(48)
Hello engsci,

Hello engsci,

Are you also using the Mini ITX? Or are you using a diffrent develpoment board/SOM?

--Josh