• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 739 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.

AWR1843AOP: HW trigger SYNC_IN pulse

user244678
Expert 1365 points
Part Number: AWR1843AOP
Other Parts Discussed in Thread: MMWAVE-DFP,

Hello,

I am using SDK 3.5.0.4 demo farm,

Is it correct to understand that in HW trigger mode, the operation from SYNC_IN pulse input to frame start (chirp start) is executed directly by RadarSS without going through MSS/DSS?

Best Regards,

Hiroyuki Taguchi

  • 0
    TI__Intellectual 2972 points

    Hi Taguchi-san,

    Yes, the SYNC_IN pulse is executed directly by the RF front-end SS (BSS). 

    For more information on the HW trigger, please refer to the interface control document, available in MMWAVE-DFP package 1.2.6.3: C:\ti\mmwave_dfp_01_02_06_03\docs\mmWave-Radar-Interface-Control.pdf.

    Regards,

    Jin

  • 0 in reply to Jin Lee
    Expert 1365 points

    Hi Jin,

    >Yes, the SYNC_IN pulse is executed directly by the RF front-end SS (BSS). 

    I understand. thank you.I'll read the documentation later.

    I'm currently experiencing the following issue and am having trouble.

    The frame cycle is set to 50ms in frameCfg, and the HW trigger pulse is input to the SYNC_IN terminal of the AWR1843AOP at a cycle of approximately 50ms to operate it. It will work normally for a while, but eventually the frame will not start even though the SYNC_IN pulse is being input. Once it stops frame starting, it won't come back until I reset and reconfigure the AWR1843AOP.

    The width of the SYNC_IN pulse is 600ns.

    Even when looking at it on the CCS debugger, no error messages are displayed before or after the frame stops starting, and CLI commands can be sent and received.

    Could you please give me some advice as to why the frame won't start?

    Regards,

    Hiroyuki

  • +1 in reply to user244678
    TI__Intellectual 2972 points

    Hi Hiroyuki,

    The width of the SYNC_IN pulse seems okay. The periodicity of the HW trigger pulse should be configured to be greater than the active frame duration, among other timing requirements.

    Linking similar thread: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/834651/awr1843boost-hardware-trigger

    Please take a look at section 5.5.3 in the documentation for notes on how the SYNC_IN pulse and periodicity should be configured to ensure proper operation.

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Expert 1365 points

    Hi Jin,

    Please tell me more.

    In the unlikely event that a SYNC_IN pulse is input at an irregular timing that is shorter than the Frame duration, is it possible that the frame will not start for subsequent SYNC_IN inputs?

    Regards,

    Hiroyuki

  • +1 in reply to user244678
    TI__Intellectual 2972 points

    Hi Hiroyuki, 

    Yes, that is correct. The periodicity should be configured so that the pulse is not issued before the end of the previous frame.

    Thank you,

    Jin