• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 632 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.

IWR6843: Debug mode

Calex36
Intellectual 2245 points
Part Number: IWR6843

Our current sticking point is in debug mode. Indeed, we followed the instructions provided by your document: MMWAVE SDK Demo - 68xx DSP Version Lab User's Guide

Once the connection steps are done and the cortex and C674X are running, could you clarify the possibilities for sending a configuration to the sensor and starting the inference (like the "SensorStart" command).

  • 0
    TI__Genius 17265 points

    Hi,

    Once the device is started, you can send over the configuration using the GUI for this demo, or you can make your own and send it over via a UART terminal. You can find some example configurations for this demo at <mmwave_sdk_location>\packages\ti\demo\xwr68xx\mmw\profiles

    Let me know if there are any further questions.

    Best Regards,
    Alec

  • 0
    Prodigy 30 points

    Hi Alec,

    Thanks, I already sent a configuration, and made some changes in it.
    My problem now is that I am unable to send this config and start inference when running in debug mode with CSS because the COM ports seem busy. Could you guide me on how to communicate with the chip once entered debug mode please?

  • 0 in reply to Charles Lentz
    TI__Genius 17265 points

    Hi,

    There should be no change in COM port functionality when in Debug Mode, you should be able to connect via a terminal regardless. Are you trying to connect via the visualizer or just using a terminal program such as teraterm/putty? Additionally, is this custom hardware or one of our EVM's?

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 30 points

    Ok it works now.
    Now, I would like to put breakpoints in the DPC_ObjectDetection_execute function in the objdetrangehwa.c file however by reducing the compilation optimization, the MmwDemo_configSensor() function in the mmw_cli.c is problematic. Do you have a solution to fix this problem?

  • 0 in reply to Charles Lentz
    TI__Genius 17265 points

    Hi,

    First, it may be helpful if you elaborate on how it is being problematic so that I may provide more insightful advice. Secondly, due to the size of our radar data, we often do not have enough free space to completely disable optimization. I would recommend that you lower the optimization level only for the file which you need it for. You can do this by right clicking the file in CCSproject view and then going to properties->optimization.

    Best Regards,
    Alec