You copied the Doc URL to your clipboard.

Software design post processing

The target file, m1_for_arty_a7.axf, is generated in /Build_Keil/objects.

There is a post-process batch file, make_hex_a7.bat that the design calls automatically when the target is built. The batch file converts the .axf file to suitable .hex, .bin, and .elf files. The batch file automatically copies the relevant output files to the appropriate hardware project directories.

Therefore, when the design is rebuilt in Arm Keil μVision Microcontroller Development Kit (MDK), new .elf and .hex files are present in the filepath V:/hardware/m1_for_arty_a7/m1_for_arty_a7 .


For V2C-DAPLink drag and drop operation, qspi_a7.bin is created as part of the software design post processing process. This file is present in the /Build_Keil directory. This file can be directly copied to the V2C-DAPLink drive. The .hex file that the batch file generates is intended for use with the Vivado tools, and it does not work for drag and drop programming.


If the example design has no output to the UART, but the rest of design runs correctly on the board, that is, the LEDs respond to the push button changes, the cause is the generation of the standalone BSP, in particular, the setting of the stdin and stdout locations. For more information on changing the stdin and stdout locations, see Generating the Arty A7 board support package. You must delete the current standalone_bsp_0 directory and regenerate.
Was this page helpful? Yes No