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

AWR1642: Chirp interrupt only being called once in short range radar demo

Alastair Yu
Prodigy 80 points
Part Number: AWR1642

Hello, I'm running into a few problems with the DSS excecution flow on a modified version of the short range radar demo. 

I made some modifications to the interframeprocessing function, and some general modifications to the cli so messages could be instead received from CAN. I've confirmed the configuration is being recieved from CAN properly and the sensor is being started from CAN messages, however the BSS seems to only raise a single chirp interrupt event (I know this from looking at the gSrrDSSMCB.stats.chirpEvt variable in the CCS debugger).

I was just wondering what could have caused the BSS to behave in this way. Is there any way to diagnose issues like this?

Regards,

-Alastair Yu

  • 0
    TI__Guru*** 149044 points
    Hi,

    If I understand correctly you have checked that the commands received from CAN are identical to the ones that was hard coded in the config file?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 80 points
    Yes, the modified CLI is accepting and calling the Mmwave_start function, I'm seeing that the SRR_DSS_chirpIntCallback is called once (through the stats counter), however nothing else seems to happen afterwards.

    When I step through the DSS execution on the CCS debugger, the SRR_DSS_mmWaveTask is looping indefinitely.

    Essentially no interrupts are being triggered from the BSS, I was wondering how I might go about diagnosing this?

    Regards,
    -Alastair Yu
  • 0 in reply to Alastair Yu
    TI__Mastermind 22155 points
    Hello Alastair Yu,

    As you have mentioned you have modified the "interframeprocessing function ", does your modification increase the processing time ?
    In that case have you tried increasing the frame periodicity ?

    Thanks,
    Raghu
  • 0 in reply to Raghunandan Kamath
    Prodigy 80 points
    Hello Raghu,

    Yes, the modification has increased the interframeprocessing time (most likely), but the code hasn't reached that point yet, the inferframeprocessing function isn't being called at the moment. Would this still cause the BSS to hang?

    Side note, do you know how to modify the frame periodicity on the Short Range Radar demo?

    Regards,
    -Alastair Yu
  • 0 in reply to Alastair Yu
    TI__Mastermind 22155 points
    Hello Alastair,

    The BSS hang could be due to some other issue in the modified code. The code from the TIREX is a validated code and is working one.

    You can refer to "SUBFRAME_USRR_PERIODICITY_VAL" or "SUBFRAME_SRR_PERIODICITY_VAL" for the frame periodicity value in case USRR subframe and SRR subframe respectively.

    BR,
    Raghu