• State
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 186 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

SYNC_IN Hardware Trigger

Oliver Arnold
Prodigy 30 points
Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2243BOOST

Tool/software:

Hi,

since the last thread is already closed i opened this one. You said it is possible that the AWR2544LOPEVM can be used in secondary mode and use the SYNC_IN (C17) function. Can you tell me how? In MMWave studio i can choose the hardware trigger option but it doesn't work. So i looked it up in the source code of the mss and i saw that the trigger option is delivered to the BSS. So i guess the BSS (RadarSS) is not using this option.

So can i get access to the source code of BSS? Then i can change it accordingly. If you don't want to share the code, can you maybe add this functionality?

The other option that was metioned was the Satellite architecture with PTP. Can you tell me what the timing accuracy is? I would need ~ns accuracy to be able to use it for MIMO processing with diffferent boards.

Best regards,
Oliver

  • 0
    TI__Mastermind 26305 points

    Hello,

    The hardware trigger should work. Can you share the electrical specifications and timing of the trigger you are using?

    Regarding the PTP timing accuracy, I believe that ns accuracy could be achievable accroding to the below app note, but I will loop in someone more familiar to comment.

    IEEE 1588 Precision Time Protocol Time Synchronization Performance (Rev. A)

    Regards,

    Adrian 

  • 0 in reply to aozer
    Prodigy 30 points

    Hi,

    I'm using an Arduino Uno in combination with a digital isolator to trigger the boards. The pulse is the same as for the AWR2243BOOST boards and has a duration of ~2us and 3.3V. I soldered the cable to one of the pads that are connected to AR_SYNCIN.

    Regards,
    Oliver

  • 0 in reply to Oliver Arnold
    TI__Mastermind 26305 points

    Hello, 

    Can you confirm which point you soldered? Can you also try probing at the point below to confirm that the trigger is reaching the device?

    REgards,

    Adrian 

  • 0 in reply to aozer
    Prodigy 30 points

    Hi Adrian,


    Sure, I soldered it to the pad "2 LED_0", which can be seen in the picture below. It is connected to AR_SYNCIN with the 0 Ohm resistor R61. A measurement with an Oscilloscope confirms that the trigger signal reaches R17 with 3.2V and a pulse duration of 2.04us.

    In MMWaveStudio, I only changed the parameters in the sensor configuration tab and chose "hardware trigger" in the frame config. Is that correct?

    I also tried the subframe trigger, but that didn't work either.

    I measured if the board was sending (to rule out any other errors (from the DCA1000, for example)). Anything works fine with the software trigger, but not with the hardware trigger.

    Do I need to change anything on the board? I only attached the cable, the rest is still unchanged.

    Regards,
    Oliver


  • 0 in reply to Oliver Arnold
    TI__Mastermind 26305 points

    Hello,

    There should be nothing else needed. I just want to confirm that you are issuing the AWR_FRAMESTARTSTOP_CONF_SB API? In HW trigger you still need to issue this API before sending the HW trigger.

    If that is being done then I do not have any other ideas. I will need to check with the firmware team to make sure this feature is enabled.

    Regards,

    Adrian

  • 0 in reply to aozer
    Prodigy 30 points

    Hi,

    yes that should be invoked by the "Trigger Frame" button. Then, a message from the BSS with "Async Event XXX" is received, and the BSS should be waiting for the trigger pulse.

    Ok thank you!

    Regards,
    Oliver

  • 0 in reply to aozer
    Prodigy 30 points

    Hi,

    is there any info from the firmware team?

    BR Oliver