Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hello,
im using an IWRL1432BOOST Board. I built the OOB Demo with SDK Version 5.4.0.1. My jumper settings are set as shown in the picture.
If i flash the binary it runs just fine, i can load a config via the visualizer and the data plot i see looks reasonable. Right now i bypass the CLI to make sure to directly see whether the program gets executed or not (the blinking LED shows that the application is running after a config is set).
However, if i want to debug the same software, i'm facing issues. I can step through with the debugger up to where rfs_rfsOpen (rfs_driver.c) is called. In that function the HwiP_nmi_handler of freertos gets called after this part:
/*! -# unhalt RFS M3 core - use TOPRCM register, this takes ~120us */
w_regValue = M_FE_TOPRCM_FEC_PD_CM3_UNHALT_VAL;
M_REG32_SWRITE(c_devIndex, p_regFecPdRst, w_regValue, w_regCmpSts, xw_return1);
xw_return += xw_return1;
I also tried to just let the software run in debug mode without breakpoints. The actual application does not get executed, it always lands in the HwiP_nmi_handler. If i place a breakpoint in the bypass_cli function (where it should land), it never reaches that point. To prevent the bootloader from jumping to any applicationin the flash, i erased it using the Uniflash tool.
I followed the steps in Debug Guide CCS20. Also the output of the GEL script looks exactly the same as in the debug guide.
I'm curious why this happens as the guide suggests a straight forward procedure. Am i missing something?
I also tried the original OOB Demo of SDK Versions 5.5.3 and 5.5.4, but for some reason even if i flash the binary, the application is not running. I also don't see any output of the CLI.
I would appreciate if somebody can help me out.
Regards,
Markus
