UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor mberemand
Visitor
75 Views
Registered: ‎10-22-2018

ZC702 hangs at "Starting kernel...". Haven't modified device tree.

Using 2017.2 version of all tools. My .bif file looks like this

all:
{
   [pskfile] psk.pem
   [sskfile] ssk.pem	
   [bootloader, authentication=rsa] test_secure_fsbl.elf
   [authentication=rsa] download.bit
   [authentication=rsa] u-boot.elf
   [authentication=rsa, partition_owner=uboot] image.ub
}

Where test_secure_fsbl.elf is just the default fsbl compiled with RSA_SUPPORT defined.

The only relevant setting I've changed in petalinux-config is setting the kernel address as well as the device from which to find the kernel image (manual instead of sdcard).

I've tried the steps outlined here without success. It's my understanding that I should never have to touch a .dts file and that the petalinux-config menu utilities take care of all of the relevant settings for me, and I'm using as many of the default settings as possible.

When the board starts I am running the commands manually since u-boot is incorrectly trying to use the default env variables.

Zynq> load mmc 0 0x100000 BOOT.bin
reading BOOT.bin
48810752 bytes read in 4049 ms (11.5 MiB/s)
Zynq> zynqrsa 0x100000
UBOOT is not Owner for partition 0
UBOOT is not Owner for partition 1
UBOOT is not Owner for partition 2
Zynq> bootm 0
## Loading kernel from FIT Image at 00000000 ...
   Using 'conf@1' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x000000d4
     Data Size:    2000552 Bytes = 1.9 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x20008000
     Entry Point:  0x20008000
     Hash algo:    sha1
     Hash value:   117655556b0f751e23a257513088cf6521bb0ee2
   Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 00000000 ...
   Using 'conf@1' configuration
   Trying 'ramdisk@0' ramdisk subimage
     Description:  ramdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x001ec1d0
     Data Size:    42202890 Bytes = 40.2 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha1
     Hash value:   86d65657008671bdd0023b5778b58b05a052ce19
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 00000000 ...
   Using 'conf@1' configuration
   Trying 'fdt@0' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x001e8870
     Data Size:    14512 Bytes = 14.2 KiB
     Architecture: ARM
     Hash algo:    sha1
     Hash value:   53ce411b2e02de46a75e3b265b178eb5d01cb029
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x1e8870
   Loading Kernel Image ... OK
   Loading Ramdisk to 1d7c0000, end 1ffff70a ... OK
   Loading Device Tree to 1d7b9000, end 1d7bf8af ... OK

Starting kernel ...

I realize 0x20000000 is a ridiculous address for the kernel, I was just trying something.

0 Kudos
2 Replies
Visitor peimann
Visitor
45 Views
Registered: ‎10-03-2018

Re: ZC702 hangs at "Starting kernel...". Haven't modified device tree.

Hello @mberemand,

Saw your post.  This may be a little nit. 

The load address that I see in your output is 0x20008000, not 0x20000000. 

Hopefully that helps some.

Regards,
Peimann

 

Kind Regards,
Peimann, S. M.
----
Toddlers are the Storm-Troopers of the Great God Entropy.
Physics: Not Just a Good Idea, It's THE LAW.
0 Kudos
Visitor mberemand
Visitor
23 Views
Registered: ‎10-22-2018

Re: ZC702 hangs at "Starting kernel...". Haven't modified device tree.

I saw that, I don't know why it's doing that. I never specified any value of 0x8000 for it to use as an offset.

0 Kudos