AWR1843BOOST: the "SYNC_OUT" signal from AWR1843

Hello,

Your pinmux is correct. Can you please share your console output when building the binary to make sure there are no issues? I am assuming it is otherwise working correctly and you can see the device framing and receiving data? I am also assuming you are measuring this during the device frame period.

Regards,

Adrian

Hello，

I  send the profile_2d.cfg via cli，   add GPIO_2 toggle at every frame to prove that the frame is running.

But there is nothing on R108.

Thank you in advance,

Best regards

Hello ,

 My console output when building the binary.

Best regards

Hi,

If you don't get any building error, than the code builds correctly.

Can you please send us the demo files you have changed?

Thank you

Cesar

Hi Expret,

Pinmux_Set_OverrideCtrl(SOC_XWR18XX_PING13_PADBC, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL); Pinmux_Set_FuncSel(SOC_XWR18XX_PING13_PADBC,SOC_XWR18XX_PING13_PADBC_SYNC_OUT);

The aboved  code was add to the MmwDemo_PlatformInit.

Add GPIO_write(DOC_XWR18XX_GPIO_2,toggle) to rhe MmwDemo_transmitProcessOutput  to indicate that the frame is running.

Thank you

Hi,

Thanks for the details. To confirm, nothing is captured by the oscilloscope when connected to pin 18 (AR_SYNC_OUT_SOP1) of the J6 header either? 

Would it be possible to connect it to another board that is expecting a HW trigger and confirm it is working in that context?

Hi,

Nothing is captured by the oscilloscope when connected to pin 18 (AR_SYNC_OUT_SOP1) of the J6 header.

Is the firmware does not support?

Hi,

Let me test with those changes and get back to you by end of this week.

Thank you,

Jin

Hi Expret,

Is the test done?

Best regards

Hi, 

Apologies for the delay. While the pinmux changes look fine, the AWR1843BOOST is missing a 0 ohm resistor that needs to be added to R108 to test SYNC_OUT. I have not had time to do this and will keep you updated. 

Could you confirm that your AWR1843BOOST board has a 0 ohm resistor added to R108?