This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR6843ISK: AWR6843ISK +mmwave booster debug mode (breakpoints randomly moves)

Part Number: AWR6843ISK
Other Parts Discussed in Thread: AWR6843

Tool/software:

Dear sir/madam

  we are using AWR6843ISk + mmwave booseter setup . and able to run the "AWR6843_CPD_with_Classification"  example  project  on  debug mode on code composure studio .

we observed randomly movement and breaking the code ,when we  try to "step into"  the code with breakpoint.

we found on Ti forum thread that this is due to code optimization settings and recommended to make optimization off will help running breakpoint with out issue.

 we have tried with all combination available and summary of result is attached for your reference(So random movement  observed, when we "step into" the code with breakpoint with all the cases).

Optimzation level AWR6843_CPD_with_Classification project
off build errors in dss code, mss built
0 build errors in dss code, mss built
1 build errors in dss code, mss built. Since, mss built checked mss main code but breakpoint movement is still random
2 No build errors , but breakpoint movement is random
3 No build errors , but breakpoint movement is random
4 This level is not there in dss project , but there in mss. Continued to do so but breakpoint movement is random

build error snapshots:

My question: 

1.what is the reason for random random movement of code flow ,when we use "step into"  option in the code with breakpoint? and how to resolve this issue?

Regards,

mani

  • Hey Mani,

    Thanks for reaching out regarding this observed behavior. I have looped in another software expert to look into the matter regarding why -o0 optimization is failing to build on the DSS side, but for the random movement of the code when stepping, this is indeed because of optimization. Optimization can move or even remove certain lines of code to improve speed or decrease size which makes the debugger appear to move erratically when stepping, hence why it is recommended to disable optimization completely.

    Hopefully this answers your initial question, but please give my colleague a day or two to look into the DSS build issue.

    Regards,

    Kristien

  • Hi Mani,

    Regarding the DSS build issue, re-arranging how you store your program data should solve your build issue. A great visual tool that you can use can be accessed through View>Memory Allocation. See below image

    You can re-arrange how memory is allocated in the linker.cmd. Let me know if you want additional tips on how to move memory around so everything fits.

    Best,

    Vignesh K.