COMPILE BOOT.ELF CODE

The code for the Xilinx version of go is explicit: unsigned long do_go_exec(ulong (*entry)(int, char * const ), int argc,Īrmv8_switch_to_el1(0x0, 0, 0, 0, (unsigned long)entry, This is why you first attempt was working, and your second one failed:įirst attempt: fatload mmc 1 0圆000000 add.bin This is likely that this was never one of their requirements:Ī) They diverged from the standard implementation of the go command so that it would start the program at EL1, from say, the EL2or E元 u-boot is running at, using armv8_switch_to_el1(): that means that, once you have executed, say, add.bin once, you will return to u-boot at EL1, and u-boot will never allow you to use the go command again. This having been said, Xilinx did not do anything to allow you to use this feature, that is allowing you to execute a program and return to the u-boot prompt. You may have, and I would advise you, to use the dcache flush/ icache flush commands in the case you would successively load/execute two different programs from the same address: some bizarre things may otherwise happen. Yes, you are right to think that this can be achieved by using the go u-boot command when using a standard version of u-boot: it actually is more like a call command than a go command, and it will display the return code returned by the program. Now How do I exit from this application and get back to u-boot prompt?Īn ordinary return statement from the main procedure will resume execution at the U-Boot prompt (assuming your program conforms to the API and does not clobber the stack or the U-Boot image in high memory). Hence your code is stranded, and cannot resume U-Boot. When your program allocates its own stack (as your tested code does), it is discarding the return address to the calling U-Boot code. This will cause your 'program' to use U-Boot's already allocated stack and heap. Use of U-Boot's API is recommended, especially if you want to return back to U-Boot's command prompt.

The salient requirements are that you use U-Boot's make file and CONFIG_STANDALONE_LOAD_ADDR is properly defined (e.g. U-Boot like console I/O functions or interrupt services. Run 'standalone' applications, which can use some resources of One of the features of U-Boot is that you can dynamically load and Well) you can continue to work in U-Boot after return from Provided by U-Boot it is expected that (if they behave 'Standalone Programs' are directly runnable in the environment If U-Boot is configured properly, then this 'standalone' program is automatically built with an ordinary make command.įrom U-Boot's README file: U-Boot supports the following image types: That is possible, but start with the sample code at examples/standalone/hello_world.c.

Right click on application project and build project.

Right click on the platform project -> build project.įile -> New -> Application project -> Select the platform project created in the above steps -> Keep everything default -> Select Hello World template -> finish.

Launch the Vitis IDE by executing the vitis command.įile -> New -> Platform project -> Create from hardware specification(XSA) -> Browse(Select zcu102.xsa) -> keep everything default(as attached screen shot below) -> Finish.

Set up the environment to run in a specific command shell:įor example in our case source /opt/Xilinx/Vitis/2020.1/settings64.sh

COMPILE BOOT.ELF SOFTWARE

To configure the environment to run the Vitis software platform, run the following scripts, which.

COMPILE BOOT.ELF INSTALL

Install Vitis 2020.2.(In our case Vitis is installed on /opt/Xilinx/ path).Now How do I exit from this application and get back to u-boot prompt? Any suggestion would be gratefully received. IWG35M> fatload mmc 1 0圆000000 Hello_World.bin I loaded the Hello_world.bin using fatload from the SD card, and executed the binary using go command.

I have followed this to get the application running on the u-boot, however, I am not able to exit from my application(system hangs after executing the application). I am trying to run a simple hello_world program in u-boot command prompt.

Compile boot.elf