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.

AWR1843BOOST: How to debug demo program in real time?

Part Number: AWR1843BOOST

Hi,
I'm using the CCS v12.1 and radar toolbox 1.10.00.13
and I'm trying to run demo program(Medium Range Radar) on AWR1843BOOST
i want to break/run in demo src for debug. but if i break at dsp or arm, the program does not run again.
How to debug demo code in real time?

  • Hi,

    Please refer to the SDK user guide section "CCS Debugging of real time application" for all the information. 

    Thanks,

    Pradipta.

  • Hi, Pradipta.
    I've already checked the document. Set break point in demo SW and run again, SW stops.
    I wonder what I should change within SW.
    Can you try break/run on demo SW(Medium Range Radar)?

  • Hi,

    Are you simply flashing the prebuilt binaries or are you flashing the CCS debug .appimage file. Please provide this detail. If you are not flashing the debug image then flash it as per the MRR user guide.

    Thanks,

    Pradipta.

  • Hi,

    I'm connected EVM to CCS debug and loaded the image files.

    I referred to this link.(dev.ti.com/.../node)

    Then I try to break and run in debug mode, the program does not run again.

    Can you run MRR SW on board please?

  • Hi,

    We will check this internally on the bench and provide you an update after that.

    Thanks,

    Pradipta.

  • Hi,

    We have ran this lab at our end and we were able to pause and run the code at our end. 

    Can you provide screen shots of the error you are facing? Also can you provide the sequence of steps you follow?

    Thanks,

    Pradipta.

  • Hi,

    thanks your effort.

    my sequence is

    1. Import ‘medium range radar’ project(C:\ti\radar_toolbox_1_00_01_07\source\ti\examples\ADAS\medium_range_radar)

    2. DSS and MSS rebuild

    3. Launch the target configuration(with AWR1843BOOST)

    4. Connect C674x, cortex_R4_0

    5. Load .xe674 file to c674x

    6. Grouping both c674x and cortex_R4_0

    7. Enable silicon real time mode to c674x

    8. Run the group

    9. Running the MRRVisualizer(C:\ti\radar_toolbox_1_00_01_07\tools\visualizers\MRR_GUI) and check objects of radar output

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    then,

    case 1> After I set the breakpoint at 1727 line(fastChirpVelIdx = (int16_t) obj->cfar…) in dss_data_path.c file and run again but radar could not update objects in MRRVisualizer.

    case 2> After I suspend the c674x at anytime and run again, runtime error occurs as shown below.

    Thanks.

  • Hi John,

    Can you once check with flashing the prebuilt binaries available with the project files. We have checked with them and not facing any issues. 

    Thanks,

    Pradipta.

  • Hi Pradipta,

    I tried downloading the project file again, but the problem was the same.

    Can you check the project file image I attached?

    If it works well, can you please provide a screenshot of the stops at the two brake points I mentioned?

    Thanks.

    AWR1843_mrr_image.zip

  • Hi,

    Let me try out your request and provide my observations by next week.

    Thanks,

    Pradipta.

  • Hi John,

    We performed the sequence provided by you on our bench. We used the latest SDK version for AWR1843BOOST (3.6) and the files form the latest radar toolbox. 

    Radar Academy (ti.com)

    Here are our observations.

    Case 1: if the global breakpoint is enabled for the group, then the problem is solved. Objects are being updated in MRRVisualizer. 

    The Breakpoint needs to be global as otherwise one core is halted while the other is still working which will break the Sync between the cores in the device. 

    Use global breakpoint.

    Case 2: After enabling global breakpoint, runtime error is occurring but not all the time. Sometimes it is working fine without any error. It's based on when we suspended.

    Randomly suspending the core will not work sometimes as this code is written for a specific experiment and does not account for random suspension form the debugger. 

    Thanks,

    Pradipta.