• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 484 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1642 Debugging problem

hittx
Prodigy 240 points
Other Parts Discussed in Thread: AWR1642

hello

Apply the AWR1642evm development board debugger,After the program is found to be running, if you set a breakpoint in C674, you can't continue to run according to the previous process, and the host computer can't get the information. You can use the SSR program to test the above phenomenon. Is there a problem with the AWR1642 chip or a software setup problem?

Thanks

  • 0
    TI__Guru 69960 points

    Hi,

    While frame is triggered, if DSS halts on some breakpoint then in the next run it will do in ASSERT. As when software or core halts but hardware will be chirping in background, so when it re-run frame/chirp count will not match as expected and goes in ASSERT.

    To skip this check, please remove MACRO definition from packages\ti\common\mmwave_sdk.mak and rebuild.

    # Compiler Flags for C674 Builds:

    C674_CFLAGS  = -mv6740 --abi=eabi --gcc -g -O3 -ms0 -mo --define=SUBSYS_DSS \

                  --define=$(PLATFORM_DEFINE) --define=_LITTLE_ENDIAN --display_error_number \

                  --define=DebugP_ASSERT_ENABLED --diag_warning=225 --diag_wrap=off \

                  --preproc_with_compile $(C674_INCLUDE) --emit_warnings_as_errors

    BR,

    Jitendra