Search the Community
Showing results for tags 'SSBL'.
Found 2 results
-
I am using Zynq 7000 SoC developing Bare metal application image. Assuming Image_1 is already running, I am exploring how to load & execute Image_2 (with non-overlapping memory in l_script.ld). 1) I already have working Image1.mcs (FSBL + *bit + App1.elf) in QSPI Flash. 2) The Image_1 application can receive Image_2 from the Host. 3) What I want is - to load Image_2 (*elf? or *.mcs?) to respective DDR memory, and then execute it. I think I need to reuse some code from FSBL to achieve this. But I am not sure. Please advise if this direction is correct or h -
Recently I had to make a standalone Zynq project that had multiple .ELF files all residing on an SD card. The board had to somehow know, while being powered off, which .ELF file to boot from. So how to do this? The answer is in the FSBL file. Currently, in Vivado's 2014.2 SDK, the FSBL can handle multiple "partitions" (that's how any Second Stage BootLoader is called, in our case the .ELF files) by executing the first one, when done returning to the FSBL that handoffs control to the second one and so on. But there is another way with the so called hooks: FsblHookBeforeBitstreamDload, FsblHoo
