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.

AWR1243: hw trigger output for each chirp for AWR1243/AWR2243

Part Number: AWR1243
Other Parts Discussed in Thread: AWR2243,

Hi,

I know that AWR1243/AWR2243 can output hardware trigger pulse at the beginning of each frame.

Is there a similar functionality to output a pulse at the beginning of each chirp?


Thanks,

Ilia.

  • Hello Ilia,

    In cascade operation the master device can send the frame trigger pulse to the slave devices inorder to help synchronize the framing. Cascade feature is available  in AWr2243 device, not in AWR1243 device. 

    Unfortunately we do not have any chirp level trigger mechanism. In mmwave studio there is a way to bring out the ADC VALID signal on the GPIO0 pin for debug purpose. This signal would remain high for the period where the RX ADC is sampling the front end data.  If this is something that could be useful to you, you can find the details in the following post. This is valid for both 1243 and 2243 : https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/685983/awr1243-api-for-adc-valid

    Regards,
    vivek 

  • Thanks, Vivek!

    ADC VALID seems suitable for my needs, since it should be toggled for each chirp. However, the thread you link to describes this as a debug-only feature available via Radar Studio. I need to be able to use it in production. I do not have a strict timing requirements as long as I have a pulse between each chirp. I could not find a mention of ADC_VALID or GPIO_0 in "mmWave Radar Interface Control Document" from DFP v1.2.5.1 (this is what we use currently). Is there a way to enable this functionality outside of the Radar Studio? Should I check the more recent DFP?

    Thanks,
    Ilia.

  • Hello Ilia,

    To enable ADC_VALID signal on the GPIO_0 pin (pin #N4) you can perform the below register writes (using the register write API available in the DFP) . This is not provided in the DFP since this was intended only for debug purpose.  But you could use it in your production testing.

    register address: 0xFFFFEBF8, value: 0x83E70B13

    register address: 0xFFFFEBFC, value: 0x95A4F1E0

    register address: 0xFFFFE260, value: 0x6101

    register address: 0xFFFFE270, value: 0x30

    register address: 0xFFFFEA04, value: 0x44

    register address: 0xFFFFEBF8, value: 0x0

    register address: 0xFFFFEBFC, value: 0x0

    regards,

    Vivek

  • Thank you, Vivek! This is great!