12/27/2022 0 Comments Dokumentation u bootOnce the symbol file is associated with the execution, the debugger will identify the current execution point and also will open the source file where the core is stop. Perform a reset typing "reset" command in the U-Boot command line console.mmap the u-boot ELF file and add a breakpoint in the board_init_f function (Function prior the relocation).Connect to the target using XSCT console.Generate a new Debug configuration for running target and launch it.Boot the board with the BOOT binary using a SD card.The easiest way is just set the a breakpoint once U-Boot is relocated and then drive a warm reset to make the processor stop in the breakpoint. Nevertheless the main issue for this use case, is stopping the processor before the relocation is done, as there is a small window of time to connect the debugger. PMU-FW, FSBL, ATF, U-boot).ĭebug before relocationThe symbols present on the ELF file match with the with the runtime state before the self-relocation is performed, so this means that there is no remmapping requirement for this use case and the information on the ELF file can be used straightforward for debugging purposes. As of v11.0 of this document this was under the "Loading PMU firmware in JTAG Boot Mode" section and although the focus of that chapter is the PMU-FW the provided script demonstrated loading all boot firmware (i.e. 10 of UG1137 (Zynq UltraScale+ MPSoC: Software Developers Guide). MPSoC where PMUFW and ATF are being loaded before U-Boot).Īn example Tcl script for JTAG booting a ZynqUS+ (ZynqMP) device is provided in Ch. Get the relocation offset from the running U-Boot command line using bdinfo tool, and set the offset in the advanced tabs according to that number.ĭebug running targetThis Debug configuration type can be used either for running targets where U-Boot has been loaded using a QSPI or SD boot modes, or for JTAG bood mode where a script is used for the loading process (i.e. Add a function breakpoint in _main or use the "Stop at program entry" option in order to stop the debugger when the debug configuration is launch.ĭebug after relocationFor debugging the U-Boot code after the relocation, the debug configuration provides an advanced options menu where relocation information can be set. elf files, but the extension can be removed afterwards for the MPSoC use case) and check the core where it will be loaded.īy default the Debug configuration adds two breakpoints at main and _exit functions, however the main entry function for U-Boot is _main rather than main, which means that the debugger will not stop by default ot it. Debug before RelocationIn the Application tab select the U-Boot executable file using the Browse feature (file browser force to use. For ZynqUS+ you should attach to a running target as described in the "Debug running target" section. Debugging U-boot as a standalone application is not fully possible on ZynqUS+ (ZynqMP) devices due to dependencies on other software components (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |