• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 2050 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.

CCS/AWR1843BOOST: xdc.runtime.Error.raise: terminating execution

hasan guz
Intellectual 255 points
Part Number: AWR1843BOOST


Tool/software: Code Composer Studio

Hi,

I downloaded the Automotive Toolbox and successfully imported the Medium Range Radar project in CCS.

I followed the user guide to run the project.

I started flashing the device with the debug binary file located at

C:\ti\mmwave_sdk_<ver>\packages\ti\utils\ccsdebug\xwr18xx_ccsdebug.bin

i am running first Cortex_R4_0 target and  running C674X_0 target but i'm getting runtime error like this;

[Cortex_R4_0] Debug: Launched the Initialization Task
Debug: Initialized the mmWave module
Debug: Synchronized the mmWave module
Set LDO Bypass
Debug: MMWave has been configured for MRR.
Debug: Sensor will start momentarily.
[C674X_0] Heap L1 : size 16384 (0x4000), free 6144 (0x1800)
Heap L3 : size 1048576 (0x100000), free 0 (0x0)
Heap L1 : size 16384 (0x4000), free 1000 (0x3e8)
Heap L3 : size 1048576 (0x100000), free 262144 (0x40000)
Heap L2 : size 102400 (0x19000), free 21488 (0x53f0)
Heap L2 : size 102400 (0x19000), free 14432 (0x3860)
[Cortex_R4_0] xdc.runtime.Main: "../mss_main.c", line 670: assertion failure
xdc.runtime.Error.raise: terminating execution

I encountered similar errors on the forum and tried but the result did not change.

Could someone please help  this error code ?

Thanks 

Hasan

SDK ver: 3.05.00.04
CCS ver: 9.10
Automotive_ toolbox: 3.2.0

  • 0
    TI__Genius 15046 points

    Hi Hasan,

    This is possibly due to a known issue with the lab in debug mode. Could you try to load the debug binaries, and run the DSS first, and then the MSS?

    This happens because currently, there is a lack of synchronization between MSS and DSS. MMWave_start happens on the MSS straight away without any input from the CLI. Due to this, the DSS can sometimes miss some frames before it starts up and raise an assertion error.

    Let me know if this doesn't resolve this issue.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Intellectual 255 points

    Hi Aayush

    This helped a lot, thank you.

    Now how can I read this data over teraterm with uart. I don't want to use matlab.

    Regards,

    Hasan

  • 0 in reply to hasan guz
    TI__Genius 15046 points

    Hi Hasan,

    The data is sent over UART in TLV frame format frame header + multiple (type, length, value). You can have a look at the "Output Data Format" section of the MRR Developer's Guide. To make sense of the data, you would have to decode the incoming data in accordance with the specified format. This is what the Matlab GUI does. The documentation might not be comprehensive enough to get an exact idea of the format, I'd suggest you look into the code, specifically UART_writePolling function calls in mss_main.c.

    Essentially, per message, it sends one frame header: MmwDemo_output_message_header and then multiple TLV's which are made up of MmwDemo_output_message_tl and the array being transmitted (the value). The number of TLVs in a message are specified in the message header so that the message can be decoded on the receiver side.

    You can capture the data over UART by any number of means, and then write software to decode this data in accordance with the TLV output format.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Intellectual 255 points

    Hi Aayush,

    Thanks for your answer,

    I've already looked. My question is how do i do this?

    After making uart port connection like this

    I sended this command

    "advFrameCfg", "sensorStart"

    And I'm connecting to the data port from a new teraterm page, but I'm not getting any data.

    Regards,

    Hasan

  • 0 in reply to hasan guz
    TI__Genius 15046 points

    Hi Hasan,

    I have just verified this on my end, there should be data on the auxiliary data COM port.  I would suggest the first step to be to ensure that the GUI displays the data. If this is the case, you can be assured that the data is coming in over the data COM port.

    For teraterm, the baud rate for the data port should be 921600, maybe that is the issue?

    Also, the user COM port is not used by the MRR lab. The data would start coming in as soon as you run the debug binaries, there is no need to write "advFrameCfg", "sensorStart" to the user port. I know the developer guide says differently, this discrepancy will be patched soon.

    Once you have ensured that the GUI is receiving data, could you open up teraterm on the auxiliary data port with baud rate set to 921600 and run the lab again (DSS first and then MSS)? Alternatively, you could also flash the binary image file and power up the device to get the data.

    Let me know if the issue still persists.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Intellectual 255 points

    Hi Aayush,

    Now its okey, thanks

    Regards,

    Hasan