• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 30 subscribers
  • Views 573 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.

IWRL6432BOOST: Debugging applications ends up in HWI

Munan Xu
Expert 4940 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

Hello,

Any tips on getting debugging working on the IWRL6432 booster pack? I followed the debug instructions on the tirex loading the empty project and then starting a debug session. Then I loaded in the application I'm trying to debug (the motion and presence detect demo) and try to step through the code. I have a few breakpoints set in the mmw_cli.c source file since I'm trying to run this demo without needing to feed it a config file. The application never gets there though and always ends up in hard fault. 

Is there a different way I'm supposed to be trying to debug?

BTW I did set the gDebugTargetCode flag to 1 so it's not that the application is going into low power mode.

Munan

  • 0
    TI__Mastermind 19450 points

    Hello Munan.

    Is the application going directly into HWI or is it after you send a CLI command? Could you provide what configuration file you are using?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 4940 points

    Hi Santosh,

    It's going into HWI somewhere after main but before the CLI commands are processed. 

    Here is my mmw_cli.c which has the hard coded commands that I have added. The config file is the PresenceDetect.cfg from the mmWave toolbox.

    I have the CLI_BYPASS=1 defined within my project settings and a breakpoint set at the CLI_ByPassApi() function.

    1651.mmw_cli.c

    Munan

  • 0 in reply to Munan Xu
    TI__Mastermind 19450 points

    Hello Munan.

    Can you tell me which SDK you are using?  I will work to recreate your setup and report back what I find.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 4940 points

    Hi Santosh,
    I am using MMWAVE_L_SDK_05_03_00_02

    Munan

  • 0 in reply to Munan Xu
    TI__Mastermind 19450 points

    Hello Munan.

    I also noticed that you are missing the delimiter \r\n after every CLI command in the radarCmdString.  Can you try adding this delimiter to see if then accepts your configuration?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 4940 points

    Hi Santosh,

    I did try this and it still doesn't seem to be working correctly. I do see the LED blinking so it looks like it's sampling, but I have no way of telling. The desktop industrial visualizer GUI is not updating and the debug access is also still not working for me.

    Munan

  • +1 in reply to Munan Xu
    TI__Mastermind 19450 points

    Hello Munan.

    Since you are not parsing the configuration via the visualizer, the visualizer is still expecting data at the 115200 baud rate.  However, the data from the device is being sent at a baud rate of 1250000, so you could remove that baud rate command to see the data on the visualizer.  In addition, debug access could be disconnecting due to going into low power mode.  To get around this, change the lowPowerCfg from 1 to 2 in order to enter low power emulation mode.  You can preserve debug access this way.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 4940 points

    Hi Santosh,

    Ok, commenting out the change baud rate line fixed the GUI issue, thank you for pointing that out. I'll try the second item here and see if that fixes the debug issues I'm having.

    Munan

  • 0 in reply to Munan Xu
    TI__Expert 4940 points

    Can confirm that changing the lowPowerCfg from 1 to 2 in the cfg restored debug access. Also for what it's worth, instead of flashing the empty project to the external spiflash and loading the actual application binary through the debugger, I loaded the presence detect demo directly onto the serial flash and put the device in operational mode. Then launching the configuration from the target configuration list and connecting to the M4F core works as expected. Then you can just load the symbols instead of having to program the device through the debugger. 

    I can now debug through CCS and GUI is working as expected.

    Thanks for the pointers!

    Munan