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_<value>] 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_<value>] 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_<value>] 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_<value>] 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: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
