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.

AWR1642BOOST: How to Enable SYNC_OUT

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642,

Hi,

I try to capture AWR1642 SYNC_OUT and output chirp on AWR1642BOOST. According the datasheet and Schematics, The AWR1642 PIN G13 is configured to SYNC_OUT and  connected to P2 PIN1, but it didn't output SYNC OUT signal  on P2 PIN1. 

On AWR1642 datasheet page19, Table 4-1. Pin Attributes, The BALL RESET STATE of PIN G13 is Output disabled. I think the BIN file(xwr16xx_radarss_rprc_ES1.0.bin) in mmWave Studio install path also doesn't configure the SYNC_OUT to output enable. 

Is there any  mothed to enable SYNC_OUT through mmWave Studio ? 

Thanks for your help.

  • Hi,

    It seems that you have an AWR1642BOOST EVM with ES 1.0 silicon. Is this correct?

    Thank you
    Cesar
  • Hello Anqiang,

    There is no way to enable the digital SYNC_OUT in mmWaveStudio for single chip mode. This function is enabled in cascaded mode, but AWR1642 does not support cascading.

    Regards,

    Adrian
  • Hi Adrian,

    As the AWR1642 datasheet page26 Table 4-4. Signal Descriptions, We have the PIN definition of SYNC_OUT, I think we should be able to enable.

    And, I don't want to make AWR1642 work in cascaded mode. I thought SYNC_OUT should compare with the captured chirp waveform as a reference that we can exact know the captured chirp waveform is same as configuration or not.
  • Hi Cesar,

    Yes, I have an AWR1642BOOST with ES1.0 silicon.
  • Hi

    I found the below topic, his question is same. And solved through modify firmware, I think we also can get the same result through modify REG, but I didn't find the REG definition.

    e2e.ti.com/.../773333

    thanks for your help.
  • Hello Anqiang,

    In that thread, they used a GPIO to toggle on frame start by doing as follows:

    "MSS frame start interrupt handler sends a message to the MSS, and the MSS asserts a GPIO output - this works OK and I assume the latency with respect to the true frame start is small."

    For this implementation, you would need to implement this yourself in code by adding the necessary code to the MSS frame start interrupt handler. You could use any accessible GPIO of your choosing. Unfortunately, there is no simple way to do this in mmWaveStudio with 16xx.

    Regards,

    Adrian