Here's an image showing what the console looks like: https://www.dropbox.com/s/c62tabxsmghaccc/Screenshot%202017-11-17%2015.56.49.png?dl=0 from QSPI boot with where it hangs.
Giordon On Fri, Nov 17, 2017 at 2:55 PM Giordon Stark <[email protected]> wrote: > The reason I ask is that when I try to program the QSPI flash with this > BOOT.bin > > //arch = zynqmp; split = false; format = BIN > the_ROM_image: > { > [fsbl_config]a53_x64 > > > [bootloader]E:\gFEX_pre_production\image\zu19eg_3\zu19eg_3.sdk\fsbl_a53\Debug\fsbl_a53.elf > [destination_cpu = > pmu]E:\gFEX_pre_production\image\giordon\linux\gfex-prototype3\pmu-gfex-prototype3.elf > [destination_device = > pl]E:\gFEX_pre_production\image\zu19eg_3\zu19eg_3.sdk\zcu19eg_top_hw_platform_0\zcu19eg_top.bit > [destination_cpu = a53-0, exception_level = el-3, > trustzone]E:\gFEX_pre_production\image\giordon\linux\gfex-prototype3\arm-trusted-firmware.elf > [destination_cpu = a53-0, exception_level = > el-2]E:\gFEX_pre_production\image\giordon\linux\gfex-prototype3\u-boot.elf > } > > the u-boot line hangs with "MMC: " and nothing else. I think this is > related to the SD not working at all. > > On Fri, Nov 17, 2017 at 2:04 PM Giordon Stark <[email protected]> wrote: > >> Is it possible to tell u-boot to not boot from MMC? I suspect it's a >> configuration flag -- and this is when I try to program the QSPI using my >> boot.bin and it would be beneficial to make that work. >> >> Thanks, >> >> Giordon >> >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
