Author Topic: boot hangs in QEMU with known good boot image for TE0820/TE0701  (Read 160 times)

dm1000

  • Active Member
  • *
  • Posts: 23
I built a QEMU image using the guidance found in UG1169 (using SD for Boot).  I have a known-good working boot image that has been booting successfully from the SD card
on a TE0820/TE0701 dev board.  The Linux image was built with Petalinux. 

I see the following message when invoking QEMU.

Code: [Select]
--------------------------------------------------------------------------------

TE0820 TE_XFsbl_HookPsuInit_Custom

Configure PLL: SI530-A

Si5338 Init Registers Write.

Si5338 Init Complete

PLL Status Register 218:0x0                     

USB Reset Complete

ETH Reset Complete

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

Xilinx Zynq MP First Stage Boot Loader (TE modified)

Release 2021.2  Oct 13 2021 - 07:15:53

Device Name: XCZUUNKNEG

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

TE0820 TE_XFsbl_BoardInit_Custom

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

PMU-FW is not running, certain applications may not be supported.

 
And the boot hangs in QEMU.

Is the conclusion that the FSBL has hung? Or something else - like PMU-FW?
Does Trenz have a web link or some guidance for using QEMU?

Dave

JH

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1908
Re: boot hangs in QEMU with known good boot image for TE0820/TE0701
« Reply #1 on: May 23, 2022, 11:23:02 AM »
Hi,
for QEMU, you must check Xilinx documentation. We have only reference design with standard petalinux flow:
https://wiki.trenz-electronic.de/display/PD/TE0820+Test+Board

Xilinx has changed boot flow with 21.x, and it looks like QEMU was last time testet with 20.1 (also latest version is from Nov. 2020, so I would expect that this is the same like 20.1 version....). See:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/821395464/QEMU+User+Documentation

Maybe the QEMU  documentation is not compatible with newer Vivado versions...

br
John