04-03-2019 09:13 PM
When 10G ethernet was added, petalinux -build failed with this error. I added 10G to the KCU105 bsp provided by Xilinx (in the attached image).
Error log shows following:
ERROR: fs-boot-2018.3+gitAUTOINC+56f3da2afb-r0 do_configure: Function failed: do_configure (log file is located at /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.28821)
ERROR: Logfile of failure stored in: /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.28821
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is -hdf_type hdf -yamlconf /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.yaml
| APP_ARG is -app "mba_fs_boot"
| Using xsct from: /home/petalinux/tools/xsct/SDK/2018.3/bin/xsct
| cmd is: xsct -sdx -nodisp /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.tcl -ws /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname fs-boot -rp /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor microblaze_0 -hdf /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/deploy/images/plnx-microblazeel/Xilinx-plnx-microblazeel.hdf -arch 32 -app "mba_fs_boot" -hdf_type hdf -yamlconf /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.yaml
| INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
| hsi::open_hw_design: Time (s): cpu = 00:00:04 ; elapsed = 00:00:14 . Memory (MB): peak = 718.102 ; gain = 87.203 ; free physical = 14698 ; free virtual = 37774
| /home/petalinux/tools/xsct/SDK/2018.3/gnu/microblaze/lin
| can't set "periph_config_params": variable is array
| while executing
| "set periph_config_params 0"
| (file "xxvethernet.tcl" line 37)
| ERROR: [Hsi 55-1545] Problem running tcl command namespace eval sw_xxvethernet_v1_1 source xxvethernet.tcl :
| while executing
| "source xxvethernet.tcl"
| (in namespace eval "::sw_xxvethernet_v1_1" script line 1)
| invoked from within
| "namespace eval sw_xxvethernet_v1_1 source xxvethernet.tcl"
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
| ERROR: [Hsi 55-1450] Error: running generate_bsp.
| hsi::generate_app: Time (s): cpu = 00:00:00.87 ; elapsed = 00:00:05 . Memory (MB): peak = 731.703 ; gain = 12.766 ; free physical = 14638 ; free virtual = 37728
| Failed to generate app mba_fs_boot
| while executing
| "error "Failed to generate app $params(app)""
| invoked from within
| "if { [catch {hsi generate_app -dir $project} res] } {
| error "Failed to generate app $params(app)"
| }"
| (file "/home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.tc..." line 36)
| WARNING: /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/temp/run.do_configure.28821:1 exit 1 from 'xsct -sdx -nodisp /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.tcl -ws /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname fs-boot -rp /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor microblaze_0 -hdf /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/deploy/images/plnx-microblazeel/Xilinx-plnx-microblazeel.hdf -arch 32 -app "mba_fs_boot" -hdf_type hdf -yamlconf /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/fsboot.yaml'
| ERROR: Function failed: do_configure (log file is located at /home/petalinux/shared/pl_projects/KCU105_10G_v2_64bit/build/tmp/work/plnx_microblazeel-xilinx-linux/fs-boot/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.28821)
ERROR: Task (/home/petalinux/components/yocto/source/microblaze_full/layers/meta-xilinx-tools/recipes-bsp/fsboot/fs-boot_git.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2736 tasks of which 2051 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/petalinux/components/yocto/source/microblaze_full/layers/meta-xilinx-tools/recipes-bsp/fsboot/fs-boot_git.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
ERROR: Failed to build project
04-04-2019 08:42 AM - edited 04-04-2019 08:45 AM
Thanks for the HDF. The issue is in the fs boot generation. I could replicate this issue in a standalone applciation.
I had a look at the later version of the xxv_ethernet driver, and there is a change her to fix this issue
10/31/18 rsp Use identifiable suffix for global variables to avoid conflicts.
I created a patch (against xilinx-v2018.3 branch of embeddedsw) for you that can be added to the fsboot recipe in your petalinux workspace to address this issue.
You can create a fsboot recipe folder as shown below:
I have added the patch, and the fs-boot_%.bbappend here
place the 0001_update_suffix_xxv_ethernet_tcl.patch into the files folder, and fs-boot_%.bbappend in the fsboot folder as seen above.
To test, do a petalinux-build -c fs-boot
04-04-2019 01:49 AM
Can you share the devicetree. I will replicate this issue on my end.
04-04-2019 03:34 AM
04-04-2019 03:43 AM
Sorry, I meant the HDF file please
04-04-2019 03:49 AM
04-04-2019 08:42 AM - edited 04-04-2019 08:45 AM
Thanks for the HDF. The issue is in the fs boot generation. I could replicate this issue in a standalone applciation.
I had a look at the later version of the xxv_ethernet driver, and there is a change her to fix this issue
10/31/18 rsp Use identifiable suffix for global variables to avoid conflicts.
I created a patch (against xilinx-v2018.3 branch of embeddedsw) for you that can be added to the fsboot recipe in your petalinux workspace to address this issue.
You can create a fsboot recipe folder as shown below:
I have added the patch, and the fs-boot_%.bbappend here
place the 0001_update_suffix_xxv_ethernet_tcl.patch into the files folder, and fs-boot_%.bbappend in the fsboot folder as seen above.
To test, do a petalinux-build -c fs-boot
04-04-2019 09:24 PM
04-05-2019 12:01 AM
@stephenm Thank you for your response. We have 2 boards as of now. KCU105 and our own custom board. We have a base microblaze design for the custom board, that works fine and has been tested to boot linux.
when we added the 10G/25G ethernet subsystem in PCS/PMA +MAC mode. We find that the microblaze(which runs petalinux) is constantly under reset.
Appreciate any pointers. Thanks!
04-05-2019 12:30 AM - edited 04-05-2019 12:37 AM
Can you verify if the patch fixed the issue in this thread. If so, we can mark this as closed. This helps other users that might have the same issue as you find the solution too.
You can create another thread for the microblaze reset issue. This sounds like a HW issue, that I can help with in another thread.
04-05-2019 03:08 AM
This patch worked. Thank you so much!
I have posted microblaze question here: https://forums.xilinx.com/t5/UltraScale-Architecture/microblaze-is-in-constant-reset-after-adding-10G-25G-ethernet/td-p/958336
Along with it there are these unanswered questions on the forum from my side:
https://forums.xilinx.com/t5/Embedded-Processor-System-Design/How-to-interface-emmc/td-p/957098
04-05-2019 03:49 AM
Ok, can you mark this thread as solved?
I'll take a look at the other threads
05-04-2020 01:34 PM
I have similar issue onb 2018.3/zynqmp
Where would I find this patch ???
0001_update_suffix_xxv_ethernet_tcl.patch