Actions
Forum Thread Details
  • Replies 2 replies
  • Subscribers 346 subscribers
  • Views 636 views
  • Users 0 members are here
Related

Ultra96 V2 hangs at boot, console doesn't print anything, custom Linux, Vivado 2018.3

nico_n04

I used the SDK to generate the PMUFW, device tree, and FSBL. I added debug mode to FSBL and PMUFW and used UART1.

I generated the BOOT.BIN :

bootgen -image test.bif -arch zynqmp -o BOOT.bin -log info -w

 

I have not issues generating the boot.bin.

The test.bif is structure as follow:

 

//arch =  zynqmp; split = false ; format = BIN

the_ROM_image:

{

     [bootloader, destination_cpu = a53-0]FSBL.elf

     [pmufw_image]PMUFW.elf

     [destination_cpu = pl]example.bit

     [destination_cpu = a53-0, exception_level = el-3, trustzone]bl31.elf

     [destination_cpu = a53-0, exception_level = el-2]u-boot.elf

}

 

I have tried everything and read every manual and document I can find. From my understanding the PMUFW its required for the zcu102 dev board, but maybe it is not required for the Ultra96-V2.

I am using Vivado 2018.3, and I loaded the Board Definition Files from Avnet https://github.com/Avnet/bdf

 

any idea?

  • The PMU firmware is not required for simple bare metal stuff. I've seen in work without it. But, it is good practice to use it.

     

    Did you change the STDIN/OUT settings to point to psu_uart1?

     

    How are you connecting to the UART pins on J1?

     

    Have you tried booting via JTAG and was it successful?

     

    Bryan

  • in reply to bhfletcher

    I figured it out, I had an issue on the PS configuration . I created a new project and make sure not to touch the default configs for now.

    I tested the bitstream project but making sure I was loading the bitstream over the JTAG. It was getting stuck when loading the bitstream over the JTAG.

     

    thanks, for your help