Then upon a reboot, then breakpoint should be hit and user can step through the uboot code.
|Table of Contents|
Determining the uboot relocation address and offset:
Connecting to Running Target in SDK:
Launch SDK 2018.3, and Run → Debug Configurations
Double click on the Xilinx C/C++ (System Debugger) to create a new debug configuration.
Select Attach to running target as the Debug Type
If the board is connected directly to your machine, select Conection as local. However ,as in the case here the board is connected remotely, then set this up by selecting New
and setting up the target connection.
Updating the relocated symbol information:
We need to stop the processor (CortexA53 #0), and update the memory map to set the relocated symbol information. Users can do this from the XSCT command line in SDK
Adding the breakpoint to the relocated uboot driver function:
Users can set the breakpoint from XSCT too using the address calculated above:
Debugging relocated uboot function in SDK:
Now, if the user re-boots the uboot then the breakpoint will be hit, and the user can then step through the code to see if the uboot is executing as expected:
Users may need to highlight the processor to enable the debugging symbols to step over, into, ect: