Petalinux seems to be working fine for anything that doesn't rely on the FSBL or PMUFW (unfortunately the bootloader is tied to FSBL in Petalinux).
It actually looks like what's causing the problem is related to XSCT in some way, but I don't now enough about what goes on in the background to begin to understand what's missing. I can call XSCT directly with the same commands that the Petalinux FSBL recipe uses during the configure stage of the FSBL source and see the same thing.
Prep clean source:
-------------------------
$ cd /xilinx/petalinux/v2018.2
$ source settings.sh
$ cd projects/zcu102_base
$ petalinux-build -c fsbl -x distclean
$ petalinux-build -c fsbl -x unpack
$ petalinux-build -c fsbl -x create_yaml
$ pushd build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c01
83b-r0/
Setup the environment (manually)
(same as Petalinux recipe)
-------------------------------------------
$ export RDI_PLATFORM=lnx64
$ export SW_GTK3=0
$ export 'AP_ARG= -app "Zynq MP FSBL"'
$ export 'MISC_ARG= -yamlconf /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/fsbl.yaml'
$ export PATH=/xilinx/petalinux/v2018.2/tools/hsm/bin:$PATH
Run the XSCT command manually
----------------------------------------------
$ xsct /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/app.tcl -ws /xilinx/petalinux/v2018.2/projects/zcu102_base/build/../components/plnx_workspace/fsbl -pname fsbl -rp /xilinx/petalinux/v2018.2/tools/hsm/data/embeddedsw -processor psu_cortexa53_0 -hdf /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64 -app "Zynq MP FSBL" -yamlconf /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/fsbl.yaml
Starting xsdk. This could take few seconds... Eclipse:
GTK+ Version Check
done
XSCTHELPER INFO: Empty WorkSpace
{channel "tcfchan#0" closed} {-code 1 -level 0 -errorcode NONE -errorinfo {channel "tcfchan#0" closed
while executing
"::tcf::send_command $chan $service $cmd [list sdk_command_callback]"} -errorline 12}
If I add some additional output messages to the fsbl app.tcl file around the call to 'repo -set $path'...
147: if { $params(rp) ne "none" } {
148: #Local Repo Available, Set repo path. Or will pick it up from build
149: set path [split $params(rp) { }]
150: puts "+repo -set $path"
151: repo -set $path
152: puts "-repo -set $path"
153: }It shows the call to repo is what's not returning...
xsct /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/app.tcl -ws /xilinx/petalinux/v2018.2/projects/zcu102_base/build/../components/plnx_workspace/fsbl -pname fsbl -rp /xilinx/petalinux/v2018.2/tools/hsm/data/embeddedsw -processor psu_cortexa53_0 -hdf /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64 -app "Zynq MP FSBL" -yamlconf /xilinx/petalinux/v2018.2/projects/zcu102_base/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/fsbl.yaml
Starting xsdk. This could take few seconds... Eclipse:
GTK+ Version Check
done
XSCTHELPER INFO: Empty WorkSpace
+repo -set /xilinx/petalinux/v2018.2/tools/hsm/data/embeddedsw
{channel "tcfchan#0" closed} {-code 1 -level 0 -errorcode NONE -errorinfo {channel "tcfchan#0" closed
while executing
"::tcf::send_command $chan $service $cmd [list sdk_command_callback]"} -errorline 12}It looks like the next step is to dig into xsct and see what this script is calling and where that might lead - I suspect a host configuration issue, but just need to peel the onion a bit more.
Thanks,
Jason
