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.

IWR6843ISK: Issues compiling a working Long Range People Detection project...

Part Number: IWR6843ISK

We're trying to setup a project using the mmwave_industrial_toolbox_4_12_0 Long_Range_People_Detection binary for the 6843.  We are able to load the prebuilt binary for the device, and run through the 6843_50m_3D.cfg on it.  When completed, the datapath appears to run, and we get mmwDemo:/> back from the CLI interface indicating it will take another command.  That all seems to work.  When we compile the project code imported from the toolbox we are doing so with the 03.05.00.04 SDK (like the prebuilt binary that we run successfully). 

version
Platform : xWR68xx
mmWave SDK Version : 03.05.00.04
Device Info : IWR68XX QM non-secure ES 02.00
RF F/W Version : 06.03.02.06.20.08.11
RF F/W Patch : 00.00.00.00.00.00.00
mmWaveLink Version : 01.02.06.06
Lot number : 4226697
Wafer number : 20
Die coordinates in wafer: X = 24, Y = 20
Done

mmwDemo:/>

....

mmwDemo:/>sensorStart
Debug: Init Calibration Status = 0xffe
Done
mmwDemo:/>

The code can be flashed from the project binary, but when we configure it with the same 6843_50m_3D.cfg file, we get the same: 

Debug: Init Calibration Status = 0xffe

but no 'Done' and the CLI is unresponsive.

So, we try to run it with a BOOST board and debug it.  There are a couple of issues.  The first is that with the provided project code, it will never break out of the DPM_synch test

...

while (1)
{
int32_t syncStatus;

/* Get the synchronization status: */

syncStatus = DPM_synch (gMmwMssMCB.objDetDpmHandle, &errCode);

..

We can force this through by having it break if it tries more than 10 times without a valid response back, and that does push it through the rest of the initialization to the CLI.  This is only needed for debugging with the BOOST board, not for the binary flashed into the board.  It's not clear why that is an issue just for the debugging mode.

Moving on, when we load the configuration file while running in the debug mode through a local terminal and initiate the system using sensorStart, we get an error on the debugger console that we don't see with the flashed binary.  Here is what we do see from the debug console:

[Cortex_R4_0] **********************************************
Debug: Launching the MMW Demo on MSS
**********************************************
Debug: Launched the mmwaveLink Management Task
Debug: Launched the Initialization Task
Debug: mmWave Control Initialization was successful
Debug: mmWave Control Synchronization was successful
Debug: mmwaveCtrl task setup
Debug: dpm setup
Error: DPM Synchronization timed out
Debug: dpm sync completed
Debug: dpm task launched
Debug: Cycleprofiler Initialized
Debug: CLI is operational
Debug: CLI initialized
Debug: Sending rlRfSetLdoBypassConfig with 3 1 0
Error: Unable to add BPM cfg for BPM disabled. Subframe 0 [Error code -203227134]
Error: MMWDemoMSS mmWave BPM Configuration failed
Exception occurred in ThreadType_Task. 

The error: "Error: Unable to add BPM cfg for BPM disabled. Subframe 0 [Error code -203227134]" seems to be the issue.

It's unclear why the project seemingly right off of the development site won't run like the binary, or what the above issue implies about why it won't run the datapath.  

Any pointers that you can provide would be much appreciated.

-TomG.

 

  • Hi Tom,

    This DPM sync issue typically indicates that the DSS is not getting into a good state. Can you first please confirm if you are following the instructions in the Developer's Guide section of the Long Range People Detection User Guide? Including loading and running both the .xer4f (MSS) AND .xe674 (DSS) binaries when debugging in CCS.

    Best Regards,

    Josh

  • It's not clear how I need to setup the target configurations for the debug configuration so that I can debug the dss and the mss at the same time - or load the code for the dss while I debug the mss.  I had previously assumed the debugger was already doing that when I selected the IWR6843ISK in the Target Configuration and it included both CPUs:

     

    clicking on debug with the mss portion of the project selected I'm able to run the code - but it indicates that the debug probe for the C674x is disconnected.

    Let me know if there is a process to setup both at the same time.  I wasn't able to find any documentation which matched this development environment.

    -TomG.

  • I've tried under Debug Configuration to setup a launch group to 'Run' the DSS, and Debug the MSS:

    But I get this message about terminating the existing debug session as it sets up:

    And it won't setup debug for the MSS after that.  Running the debugger with the default ccxml seems to be the only thing that works.

    Even though I have Debug and Run setup in the Common tab:

      

    I get nothing on the task bar to actually start and stop the debugger with, and the DSS debug session is terminated:

    Regards,

    -TomG.

  • I couldn't get the launch group to work, so maybe that's not what that functionality is for.  However, it looks like I was able to get it setup but there were several steps that I was unaware of.  The best resource I could find on this was at: IWR6843: Debugging overhead_3d_people_count_68xx_mss failed - Sensors forum - Sensors - TI E2E support forums  

    So, using the Default configuration ccxml for the MSS code after compiling and resetting the target board, and then clicking on 'Debug', I get both of the Debug Probe for the Cortex_R4 and the Probe for the C674X.  I then Connect to the Target on the C674X, and then using the load icon, point it at the DSS project and it's xe674 binary.  I then hit run, and then debug runs the MSS project.  It now tells me that the DPM sync task completed successfully (on both side) which indicates that the DSP is communicating properly with us now.  It looks like I can reverse this process to debug on the DSP while the MSS runs.

    **********************************************
    Debug: Launching the MMW Demo on MSS
    **********************************************
    Debug: Launched the Initialization Task
    Debug: mmWave Control Initialization was successful
    Debug: mmWave Control Synchronization was successful
    Debug: MmWave CTL Task priority set
    Debug: DPC init configured
    Debug: DPC call-back configured
    Debug: DPM Module initialized
    Debug: DPM sync completed
    Debug: dpm task launched
    Debug: Cycleprofiler Initialized
    [C674X_0] Debug: DPM Module Sync is done.
    [Cortex_R4_0] Debug: CLI is operational.
    Debug: Setup MmwaveLink
    Debug: CRC Channel @08006db8 has been opened successfully
    Debug: Launched the mmwaveLink Management Task
    Debug: BSS Mailbox Handle @08001d78
    Debug: for deviceIndex 0
    Debug: Enabling the device 0
    Debug: Disabling the device 0
    Debug: BSS Mailbox Handle @08001d78
    Debug: for deviceIndex 0
    Debug: Enabling the device 0
    Debug: Power on request successfully passed to the BSS
    Debug: MmwaveLink version:
    RF H/W Version : 02.00
    RF F/W Version : 06.03.02.06.20.08.11
    RF F/W Patch Version : 00.00.00.00.00.00.00
    mmWaveLink Version: 01.02.06.06
    Debug: Finished rlSetContModeConfig
    Debug: Finished rlEnableContMode
    Debug: BootupStatus = 0x2
    Debug: Finished get radarSS bootup status to BSS
    Error: Unable to start Sensor [Error 22]
    Debug: MmwaveLink_sensorStart completed
    Debug: Frames are already stopped [21]
    Debug: MmwaveLink CW test completed

    I'm still getting the 'Unable to start Sensor [Error 22] for the CW settings test - but that is a different problem.

    In any case, let me know if this looks correct to you and if there is any additional information available on this process that would be helpful.

    Regards,

    -TomG.

  • Hi Tom,

    I'm sorry for the delayed response here. Glad you were able to resolve your issue. Thank you for including the details of the resolution. If you are still looking for additional information you can refer to the guide for using CCS Debug from the Radar Toolbox.

    Best Regards,

    Josh