Re: [meta-xilinx] [meta-xilinx-tools] PMU Firmware Generation Error for ZynqMP
On 12/11/2022 11:48 AM, Mark Hatle via lists.yoctoproject.org wrote:
On 12/10/22 10:52 AM, Joao Paulo Silva Goncalves wrote:
(background)
All of the messages below come from xsct tool and it's hsi APIs (these
are part of Vivado, the HSI bits are being run by some tcl code in
order to extract required values from the XSA to configure and compile
the firmware properly.)
/home/joaopaulo/opt/repos/xilinx-development/build-mcomm/xsct/Vitis/2022.2/gnu/microblaze/lin
| ERROR: [Common 17-55] 'get_property' expects at least one object.
| Resolution: If [get_] was used to populate the object, check
to make sure this command returns at least one valid object.
|
| ERROR: [Hsi 55-1545] Problem running tcl command
::sw_standalone_v8_0::generate : ERROR: [Common 17-55] 'get_property'
expects at least one object.
| Resolution: If [get_] was used to populate the object, check
to make sure this command returns at least one valid object.
|
| while executing
| "common::get_property IP_NAME [hsi::get_cells -hier $stdin]"
| (procedure "::sw_standalone_v8_0::generate" line 413)
| invoked from within
| "::sw_standalone_v8_0::generate standalone"
The system was looking at the property IP_NAME and got an unexpected
result. (Error message seems to indicate the property itself is not
defined?) I've no idea if it means it's missing or if it's formatted
incorrectly. But this should be verified.
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
|
| Failed to generate the bsp sources for domain.pmu-firmware_domain
|
| Details: ERROR: [Common 17-55] 'get_property' expects at least one
object.
| Resolution: If [get_] was used to populate the object, check
to make sure this command returns at least one valid object.
|
| ERROR: [Hsi 55-1545] Problem running tcl command
::sw_standalone_v8_0::generate : ERROR: [Common 17-55] 'get_property'
expects at least one object.
| Resolution: If [get_] was used to populate the object, check
to make sure this command returns at least one valid object.
|
| while executing
| "common::get_property IP_NAME [hsi::get_cells -hier $stdin]"
| (procedure "::sw_standalone_v8_0::generate" line 413)
| invoked from within
| "::sw_standalone_v8_0::generate standalone"
Same error a second time, so it looks like something is missing from
the XSA side. You'll need to go into vivado, and figure this out.
(Asking on the Xilinx support site will probably get you faster
results then here. I'm only familiar with what the system should be
doing with a working XSA.)
[Sandeep]: I extracted your xsa and it looks good to me, Issue is with
your machine configuration file where you are using UART1 for pmufw, but
UART 1 is not enabled in your vivado pcw configuration. Now you have two
option
1. Enable UART1 in vivado pcw and regenerate the xsa and use it with
same machine.conf or
2. Change the machine conf file a shown below.
#@TYPE: Machine
#@NAME: mcomm
#@DESCRIPTION: Machine configuration for mcomm board.
MACHINEOVERRIDES .= ":mcomm"
# Required generic machine inclusion
require conf/machine/zynqmp-generic.conf
# Yocto FSBL variables
YAML_SERIAL_CONSOLE_STDIN:pn-fsbl-firmware = "psu_uart_0"
YAML_SERIAL_CONSOLE_STDOUT:pn-fsbl-firmware = "psu_uart_0"
# Yocto PMUFW variables
YAML_SERIAL_CONSOLE_STDIN:pn-pmu-firmware = "psu_uart_0"
YAML_SERIAL_CONSOLE_STDOUT:pn-pmu-firmware = "psu_uart_0"
# Yocto arm-trusted-firmware(TF-A) variables
ATF_CONSOLE ?= "cadence"
TFA_BL33_LOAD ?= "0x800"
EXTRA_OEMAKE:append:pn-arm-trusted-firmware = "
PRELOADED_BL33_BASE=${TFA_BL33_LOAD}"
# Yocto device-tree variables
YAML_CONSOLE_DEVICE_CONFIG:pn-device-tree = "psu_uart_0"
YAML_MAIN_MEMORY_CONFIG:pn-device-tree = "PSU_DDR_0"
EXTRA_DT_FILES += ""
DT_PADDING_SIZE:pn-device-tree = "0x1000"
DTC_FLAGS:pn-device-tree += "-@"
YAML_DT_BOARD_FLAGS = "{BOARD template}"
# Yocto KERNEL Variables
UBOOT_ENTRYPOINT ?= "0x20"
UBOOT_LOADADDRESS ?= "0x20"
KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
# mcomm Serial Console
SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
YAML_SERIAL_CONSOLE_BAUDRATE ?= "115200"
Can try:
https://support.xilinx.com
I'm not sure what topic/forum to use though.
--Mark
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
|
| while executing
| "builtin_domain {*}$saved_args"
| (procedure "domain" line 233)
| invoked from within
| "domain create -name $params(bspname) -proc $processor -os
$params(osname) -support-app $hsitemplate -arch $params(arch)"
| invoked from within
| "if { $params(ws) ne "" } {
| #Local Work Space available
| if { $params(pname) ne "" } {
| # hwpname/bspname is empty then default it to pname+_hwproj/b..."
| (file
"/home/joaopaulo/opt/repos/xilinx-development/build-mcomm/tmp/work/mcomm-poky-linux/pmu-firmware/2022.2+gitAUTOINC+5330a64c8e-r0/app.tcl"
line 141)
| WARNING: exit code 1 from a shell command.
ERROR: Task
Re: [meta-xilinx] [meta-xilinx-tools] PMU Firmware Generation Error for ZynqMP
On 12/10/22 10:52 AM, Joao Paulo Silva Goncalves wrote:
(background)
All of the messages below come from xsct tool and it's hsi APIs (these are part
of Vivado, the HSI bits are being run by some tcl code in order to extract
required values from the XSA to configure and compile the firmware properly.)
/home/joaopaulo/opt/repos/xilinx-development/build-mcomm/xsct/Vitis/2022.2/gnu/microblaze/lin
| ERROR: [Common 17-55] 'get_property' expects at least one object.
| Resolution: If [get_] was used to populate the object, check to make
sure this command returns at least one valid object.
|
| ERROR: [Hsi 55-1545] Problem running tcl command
::sw_standalone_v8_0::generate : ERROR: [Common 17-55] 'get_property' expects at
least one object.
| Resolution: If [get_] was used to populate the object, check to make
sure this command returns at least one valid object.
|
| while executing
| "common::get_property IP_NAME [hsi::get_cells -hier $stdin]"
| (procedure "::sw_standalone_v8_0::generate" line 413)
| invoked from within
| "::sw_standalone_v8_0::generate standalone"
The system was looking at the property IP_NAME and got an unexpected result.
(Error message seems to indicate the property itself is not defined?) I've no
idea if it means it's missing or if it's formatted incorrectly. But this should
be verified.
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
|
| Failed to generate the bsp sources for domain.pmu-firmware_domain
|
| Details: ERROR: [Common 17-55] 'get_property' expects at least one object.
| Resolution: If [get_] was used to populate the object, check to make
sure this command returns at least one valid object.
|
| ERROR: [Hsi 55-1545] Problem running tcl command
::sw_standalone_v8_0::generate : ERROR: [Common 17-55] 'get_property' expects at
least one object.
| Resolution: If [get_] was used to populate the object, check to make
sure this command returns at least one valid object.
|
| while executing
| "common::get_property IP_NAME [hsi::get_cells -hier $stdin]"
| (procedure "::sw_standalone_v8_0::generate" line 413)
| invoked from within
| "::sw_standalone_v8_0::generate standalone"
Same error a second time, so it looks like something is missing from the XSA
side. You'll need to go into vivado, and figure this out. (Asking on the
Xilinx support site will probably get you faster results then here. I'm only
familiar with what the system should be doing with a working XSA.)
Can try:
https://support.xilinx.com
I'm not sure what topic/forum to use though.
--Mark
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
|
| while executing
| "builtin_domain {*}$saved_args"
| (procedure "domain" line 233)
| invoked from within
| "domain create -name $params(bspname) -proc $processor -os $params(osname)
-support-app $hsitemplate -arch $params(arch)"
| invoked from within
| "if { $params(ws) ne "" } {
| #Local Work Space available
| if { $params(pname) ne "" } {
| # hwpname/bspname is empty then default it to pname+_hwproj/b..."
| (file
"/home/joaopaulo/opt/repos/xilinx-development/build-mcomm/tmp/work/mcomm-poky-linux/pmu-firmware/2022.2+gitAUTOINC+5330a64c8e-r0/app.tcl" line 141)
| WARNING: exit code 1 from a shell command.
ERROR: Task
(/home/joaopaulo/opt/repos/xilinx-development/meta-xilinx/meta-xilinx-standalone/recipes-bsp/embeddedsw/pmu-firmware_2022.2.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 342 tasks of which 341 didn't need to be rerun
and 1 failed.
Summary: 1 task failed:
/home/joaopaulo/opt/repos/xilinx-development/meta-xilinx/meta-xilinx-standalone/recipes-bsp/embeddedsw/pmu-firmware_2022.2.bb:do_configure*
I am starting to think about to try to generate pmu firmware by hand.
Can you help me solve this problem?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5113):
https://lists.yoctoproject.org/g/meta-xilinx/message/5113
Mute This Topic: https://lists.yoctoproject.org/mt/95584811/21656
Group Owner: meta-xilinx+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-xilinx] [meta-xilinx-tools] PMU Firmware Generation Error for ZynqMP
Hi , Grzegorz. I changed HAS_PLATFORM_INIT to *HAS_PLATFORM_INIT = xilinx_zynqmp_virt_config* (as my board is based on zynqmp ) but the error remains and still the same. I think that this is not the problem. The files in HAS_PLATFORM_INIT are u-boot defconfigs and seem to be used to add init dependencies when building u-boot SPL (show in file u-boot-spl-zynq-init.inc) if your UBOOT MACHINE is different than the files in HAS_PLATFORM_INIT. So it seems that HAS_PLATFORM_INIT has no relation to pmu firmware building. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5112): https://lists.yoctoproject.org/g/meta-xilinx/message/5112 Mute This Topic: https://lists.yoctoproject.org/mt/95584811/21656 Group Owner: meta-xilinx+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-xilinx] [meta-xilinx-tools] PMU Firmware Generation Error for ZynqMP
On Sun, Dec 11, 2022 at 01:46 AM, Grzegorz Heldt wrote: > > HAS_PLATFORM_INIT += "mcomm" Sorry, quickly looking at: https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx_2022.1.bb The line should be HAS_PLATFORM_INIT += "mcomm_defconfig" and assumes you have a separate defconfig for your machine. The line should be then HAS_PLATFORM_INIT += "mcomm_defconfig" and it refers to defconfig of u-boot-xlnx if I remember correctly. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5111): https://lists.yoctoproject.org/g/meta-xilinx/message/5111 Mute This Topic: https://lists.yoctoproject.org/mt/95584811/21656 Group Owner: meta-xilinx+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-xilinx] [meta-xilinx-tools] PMU Firmware Generation Error for ZynqMP
Hi, Joao. I was at this point a few weeks ago, I'm not really sure how I resolved that, but you can give a try this: In your layer, can you create bbappend for u-boot-xlnx, with the following statement: HAS_PLATFORM_INIT += "mcomm" -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5110): https://lists.yoctoproject.org/g/meta-xilinx/message/5110 Mute This Topic: https://lists.yoctoproject.org/mt/95584811/21656 Group Owner: meta-xilinx+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
