Versions Compared

Old Version 12

changes.mady.by.user stephenm

Saved on

compared with

New Version 13

changes.mady.by.user stephenm

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



Open the Address editor and unmap (right click and select unmap segment) on the GP0_DDR_LOWOCM, GP0_QSPI_LINEAR and GP0_M_AXI_GP0:Image Removed

Image Added
Here, I have changed the base address to match my Microblaze boot vector address. 

Note: change the range to 4K first, then change the base address to 0x0010_0000. Then, change the range to 256MB (or whatever size you need). 

Software Generation:

Create FSBL:


Select File -> New -> Application Project. Set the Project Name to "fsbl", and the Processor to "ps7_cortexa9_0" and select Next. Select the Zynq FSBL and Finish.

FSBL Modification:

We can add the debug to the FSBL (this is optional). To do this, right click on the fsbl in the Project explorer and select C/C++ Build Settings and add the FSBL_DEBUG_INFO to the compiler symbol:
Image Modified

Next, open the fsbl_hooks.c from fsbl/src in the Project Explorer, and add the code to toggle the GPIO that we added in the Hardware. You can add the register writes seen below to the FsblHookFallback function:
Image Modified

Right click on the FSBL, and select Generate Linker Script, and place all sections in ps7_ram_0 and Generate.

Create Microblaze Hello World Application:

Create the MicroBlaze Hello World Application. Select New -> Application Project. Set the Project Name to "hello", and the Processor to "microblaze_0" and select Next. Select the Hello World and Finish. This will automatically create the BSP. The BSP will use the PS7_UART_1 for STDIN/OUT as we have connected the DP interface on the MicroBlaze to the GP port which allows access to PS IP (including the UART). Generate the Linker script for this application and make sure all sections are in the DDR.

Note: Both the MicroBlaze app and the FSBL are sharing the same ps7_uart_1. Be aware that if both processors try to write at the same time, you might see issues.

Note: The linker script will automatically be created based on the memory settings detected in the XSA. In this case, the DDR i set to 0x0010_0000:

Image Added

Boot Image Creation:

Here, we will be booting from the SD card. To create a BIN image for the SD card, use the Create Boot Image tool in the SDK. Right click on the FSBL, and select Create Boot Image. The FSBL and the BIT should be pre-populated. If not, then you can add these manually using the Add button in the GUI.

Note: the FSBL partition type is bootloader, all other partitions are datafile. Add the hello.elf (select Add, and browse to the hello.elf. The partition type is datafile):
Image Modified

Select Create Image to create the BOOT.BIN file.

Booting from SD Card:

Place this BOOT.bin file onto the SD card, and set the bootmode to boot from the SD card and power on the board. You will see the FSBL debug information, and the Hello World App:
Image Modified

Debugging in Vitis:


In typical systems containing a Microblaze the executable BRAM is populated with a bootloop that is automatically generated in Vivado based on the Microblaze BOOT_VECTOR. This bootloop ELF is then associated in Vivado. The reason for the bootloop is so the Microblaze has some valid instructions to execute once the Microblaze comes out of reset. This is not an issue if booting from SD Card. However, if we want to debug in Vitis, we can place this bootloop in our executable memory (PS DDR) and bring our Microblaze out of reset prior to debugging in Vitis. We can use an XSCT script to do this:

...