<div dir="ltr">Hi,<div><br></div><div>I followed the <a href="https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#xilinx-zynqmp" target="_blank">8.2.23 docs</a> to build rtems for the xilinx_zynqmp_ultra96 bsp since it was the only bsp corresponding to xilinx-zynqmp in the rtems-bsp. </div><div><br></div><div>Then I followed the boot via Uboot section <a href="https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#boot-via-u-boot" target="_blank">8.2.1.1 on docs</a>, but the uboot on zcu106 does not have a run loadfdt command, and its alternative is fdt addr [address]. But something is wrong, I cannot run the sp01.img file:</div><div><br></div><div>With fdt:</div><div>------------------------------</div><div>ZynqMP> tftpboot 0x3000000 rdubey/sp01.img                    <br></div><div>Using ethernet@ff0e0000 device                          <br>TFTP from server 172.19.0.3; our IP address is 172.19.2.40            <br>Filename 'rdubey/sp01.img'.                           <br>Load address: 0x3000000                             <br>Loading: ####                                  <br>     6.9 MiB/s                                <br>done                                       <br>Bytes transferred = 50978 (c722 hex)                       <br>ZynqMP> fdt addr 0x2A00000                            <br>ZynqMP> bootm  0x3000000 - 0x2A00000 ; reset                   <br>## Booting kernel from Legacy Image at 03000000 ...               <br>  Image Name:  RTEMS                              <br>  Image Type:  ARM Linux Kernel Image (gzip compressed)            <br>  Data Size:   50914 Bytes = 49.7 KiB                     <br>  Load Address: 00300000                            <br>  Entry Point:  00300000                            <br>  Verifying Checksum ... OK                           <br>## Flattened Device Tree blob at 02a00000                    <br>  Booting using the fdt blob at 0x2a00000                    <br>  Uncompressing Kernel Image ... OK                       <br>  Loading Device Tree to 0000000007ff1000, end 0000000007fff257 ... OK     <br>fdt_find_or_add_subnode: chosen: FDT_ERR_BADSTRUCTURE              <br>ERROR: /chosen node create failed                        <br> - must RESET the board to recover.                       <br><br>FDT creation failed! hanging...### ERROR ### Please RESET the board ### <br></div><div><div></div><div>------------------------------</div></div><div><br></div><div>With loading the system.dtb that I generally use for loading yocto linux images:</div><div><br></div><div><br></div><div>---------------------<br></div><div>ZynqMP> tftpboot 0x2A00000 rdubey/system.dtb                   <br>Using ethernet@ff0e0000 device                          <br>TFTP from server 172.19.0.3; our IP address is 172.19.253.142          <br>Filename 'rdubey/system.dtb'.                          <br>Load address: 0x2a00000                             <br>Loading: ###T #                                 <br>     8.8 KiB/s                                <br>done                                       <br>Bytes transferred = 45656 (b258 hex)                       <br>ZynqMP> tftpboot 0x3000000 rdubey/sp01.img                    <br>Using ethernet@ff0e0000 device                          <br>TFTP from server 172.19.0.3; our IP address is 172.19.253.142          <br>Filename 'rdubey/sp01.img'.                           <br>Load address: 0x3000000                             <br>Loading: ####                                  <br>     1.7 MiB/s                                <br>done                                       <br>Bytes transferred = 50978 (c722 hex)                       <br>ZynqMP> bootm  0x3000000 - 0x2A00000 ; reset                   <br>## Booting kernel from Legacy Image at 03000000 ...               <br>  Image Name:  RTEMS                              <br>  Image Type:  ARM Linux Kernel Image (gzip compressed)            <br>  Data Size:   50914 Bytes = 49.7 KiB                     <br>  Load Address: 00300000                            <br>  Entry Point:  00300000                            <br>  Verifying Checksum ... OK                           <br>## Flattened Device Tree blob at 02a00000                    <br>  Booting using the fdt blob at 0x2a00000                    <br>  Uncompressing Kernel Image ... OK                       <br>  Loading Device Tree to 0000000007ff1000, end 0000000007fff257 ... OK     <br><br>Starting kernel ...                               <br><br>"Synchronous Abort" handler, esr 0x02000000                   <br>elr: ffffffff90593000 lr : 0000000010081868 (reloc)               <br>elr: 0000000000300000 lr : 000000007fdee868                   <br>x0 : 0000000000000000 x1 : 0000000000000000                   <br>x2 : 0000000007ff1000 x3 : 0000000000000000                   <br>x4 : 0000000000300000 x5 : 0000000000000000                   <br>x6 : 0000000000000008 x7 : 0000000000000000                   <br>x8 : 000000007dda0650 x9 : 0000000001008000                   <br>x10: 000000000a200023 x11: 0000000000000002                   <br>x12: 0000000000000002 x13: 00000000000096f4                   <br>x14: 000000007dda06ac x15: 000000007fdee224                   <br>x16: 0000000000000002 x17: 0000000007fff258                   <br>x18: 000000007ddacde8 x19: 000000007fead720                   <br>x20: 0000000000000000 x21: 0000000000000400                   <br>x22: 000000000000071f x23: 000000007fdeedb8                   <br>x24: 0000000000000003 x25: 000000007ddbd378                   <br>x26: 000000007fe9ac18 x27: 0000000000300000                   <br>x28: 0000000003000040 x29: 000000007dda0790                   <br><br>Resetting CPU ...                                <br><br>### ERROR ### Please RESET the board ### <br></div><div><br></div><div>---------------------</div><div><br></div><div>What might be going wrong? zcu106 is a multi processor board, so do I need to do something special to run the sp01 test? I have not tested any other .exe (or .img) so far.</div></div>