• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 472 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/AWR1642: 1642

user4599865
Prodigy 100 points
Part Number: AWR1642

Tool/software: Code Composer Studio

Hi,

Since 1642 has two processors, we are using the demo program of 1642. When the MSS side sends more targets through the CAN interface, the whole program will hang.According to the preliminary judgment, CAN is still sending at the beginning of the Chirp in the next cycle, interrupting the Chirp signal and interrupting the synchronization, and both DSS and MSS will be dead.Can the ctrltask thread be ported to the DSS side to solve this problem?In addition, what do we need to pay attention to the ctrltask thread migrating to DSS?

Looking forward to your reply!

  • 0
    TI__Mastermind 22155 points
    Hello,
    What is the frame time? Please check by increasing your frame periodicity.

    -Raghu
  • 0 in reply to Raghunandan Kamath
    Prodigy 100 points
    After data processing, MSS sends target data through CAN interface, but before the target is sent, the next frame cycle begins.At this time, the CAN sending thread affects the rf control thread, which will cause the whole program to crash.Due to the large number of targets detected, the data processing and sending time are relatively long, so the phenomenon of program crash often occurs.Under normal circumstances, the target sending only needs to be completed before the target sending in the next cycle, but this is not the case now, the target must be completed before the radio frequency of the next cycle starts.In a nutshell, it's the synchronization of threads.
  • 0 in reply to user4599865
    TI__Mastermind 22155 points
    Please let us know your configuration. The symptom you are describing seems like the interframe time is less. Please increase the interframe time in your frame configuration(frameCfg).

    -Raghu
  • 0 in reply to Raghunandan Kamath
    Prodigy 100 points
    The frame time is 30ms，as normal logic ,the can interface only needs to send the completion target before the detection target in the next frame cycle is written to the mailbox.But in fact, the CAN interface must finish sending the detected target before the rf chirp of the next frame starts. If not, the radar will crash.I transplanted the CTRLSTSK threads in MSS to the DSS side, but failed to solve this problem.I have many detection targets to send through the CAN interface, so I need to solve this problem. THANKS.
  • 0 in reply to user4599865
    TI__Mastermind 22155 points

    Hello ,

    We have demo application that sends out object data over CAN in this link . Please refer to this code and check if there are any issues in your implementation. 

    The configuration for the code is in the "cli.c". You should be able to compare and verify your implemetation . This is a working code tha many of our customers and E2E users are actively using.

    Thanks,

    Raghu