cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mdn1
Visitor
Visitor
171 Views
Registered: ‎12-07-2020

Vitis 2019.2 Bug? destination_cpu not defined in bif file

Hello,

I reported my ZCU102 could not boot up and its boot image was created from Vitis 2019.2 "Create Boot Image" function.

https://forums.xilinx.com/t5/Embedded-Linux/UG1209-Embedded-Design-Tutorial-PMU-not-loaded-in-boot-sequence/m-p/1201761

Finally I found the root cause. "destination_cpu" was not defined in bif file.

The bif file that my Vitis generated is below:

//arch = zynqmp; split = false; format = BIN
the_ROM_image:
{
	[bootloader]<PATH>/zynqmp_fsbl.elf
	[pmufw_image]<PATH>/pmufw.elf
	[exception_level = el-3, trustzone]<PATH>/bl31.elf
	[exception_level = el-2]<PATH>/u-boot.elf
}

The destination CPU for ATF and U-boot was not defined, so I modified the bif file like below:

//arch = zynqmp; split = false; format = BIN
the_ROM_image:
{
	[bootloader]<PATH>/zynqmp_fsbl.elf
	[pmufw_image]<PATH>/pmufw.elf
	[destination_cpu = a53-0, exception_level = el-3, trustzone]<PATH>/bl31.elf
	[destination_cpu = a53-0, exception_level = el-2]<PATH>/u-boot.elf
} 

 Now my ZCU102 board can boot up with the boot image generated from the modified bif file.

Why is "destination_cpu" not defined when bif file is created by Vitis? Is this a bug?

 

Thanks in advance,

mdn1

0 Kudos
0 Replies