AWR1243BOOST: awr1642

Majid Joshani

Part Number: AWR1243BOOST
Other Parts Discussed in Thread: AWR1642BOOST, AWR1243, AWR1642, AWR1443

Hi,

I am trying to synchronize two radars (AWR1243BOOST and AWR1642BOOST) in FRAME level and I don't want to use an external oscilator.

My plan is to bring out the FRAME START clock from the AWR1243 (which is set in single chip Software trigger mode) and feed it to the SYNC_IN PIN of the AWR1642 (which is set in single chip Hardware trigger mode). Each radars is connected to a separate PC and is connected via mmWave Studio.

From the following post I realized that I can bring out the FRAME START clock to one of the jumpers PINs:

AWR1443BOOST: Realization of SPI control using two AWR1443BOOST

Here it's mentioned that the FRAME START clock for AWR1443 is on the PIN 0x7:

/* Setup the PINMUX to bring out the FRAME START on PADAY */

Pinmux_Set_OverrideCtrl(SOC_XWR14XX_PINN9_PADAY, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);

Pinmux_Set_FuncSel(SOC_XWR14XX_PINN9_PADAY, 0x7); // FRAME-START TO PAD-AY

This code can be run in MSS_Init, after the other Pin mux changes.

QUESTIONS:

1. What are the FRAME START PIN number for AWR1243 and AWR1642? I could not find anything in the datasheets.

2. How can I run these two commands in the Lua shell of the mmWave Studio? Can I run them with the os.execute command as follows:

AA=os.execute("Pinmux_Set_OverrideCtrl(SOC_XWR12XX_PINN5_PADAX,PINMUX_OUTEN_RETAIN_HW_CTRL,PINMUX_INPEN_RETAIN_HW_CTRL);")
BB=os.execute("Pinmux_Set_FuncSel(SOC_XWR12XX_PINN5_PADAX, SOC_XWR12XX_PINN5_PADAX_FM_CW_CLKOUT);")

Thanks,

Majid

over 1 year ago

0 E. Shareef over 1 year ago

TI__Genius 16120 points

Hello Majid,

I'll looking into your request and will respond here shortly.

Thanks,

E. Shareef

0 Majid Joshani over 1 year ago in reply to E. Shareef

Prodigy 70 points

Thanks,

Regards,

Majid

0 E. Shareef over 1 year ago in reply to Majid Joshani

TI__Genius 16120 points

Hello,

The frame sync is brought out on SYNC_OUT [P11].
In studio yuou can try enabling master mode on the AWR1243 and it should automatically trigger the frame sync at the start of each frame

Hope this helps,

E. Shareef

0 Majid Joshani over 1 year ago in reply to E. Shareef

Prodigy 70 points

Hi,

But the User Guide says the SYNC_OUT for AWR1243 should be on J5-PIN17:

And when I checked the PIN17 of AWR1243 in the Master mode, I did not observe any pulse.

By the way, I'll try PIN11 also and will let you know by tomorrow.

Thanks,

Majid

0 E. Shareef over 1 year ago in reply to Majid Joshani

TI__Genius 16120 points

Hello,

Sync out pin is P11 on the device. On the board, I will need to confirm the schematic to confirm how the signal can be brought out. Pin 17 on J5 may be one option to bring this signal out.

Thanks,

E. Shareef

0 Majid Joshani over 1 year ago in reply to E. Shareef

Prodigy 70 points

Yes, It is P11 for AWR1243 and G13 for AWR1642 on the devices, but what is the register number for each of them?

In the datasheet for the AWR1443 the register number (PINCNTL ADDRESS) is listed (0xFFFFEA08):

But I couln't find the same table in AWR1243 datasheet.

Can I use this PINCNTL ADDRESS for bringing out the signal like the following command?

Pinmux_Set_FuncSel(SOC_XWR16XX_PINN5_PADBE,0xFFFFEA08);

Can I run this command in the Lua shell using the os.execute command as follows:

os.execute("Pinmux_Set_FuncSel(SOC_XWR16XX_PINN5_PADBE,0xFFFFEA08);")

Thanks,

Majid

0 Majid Joshani over 1 year ago in reply to E. Shareef

Prodigy 70 points

Hi,

I also tried to generate the hardware trigger using an external MCU as follows and fed it to the SYNC_IN PIN directly, but could not get a frame that way (Error : The number of files captured is zero!)

- Pulse voltage= 3.3.

- High trigger width= 500ns (as mentioned in the "mmWave Radar Interface Control" user guide).

- Pulse width=Frame Peridicity+Frame Trigger Delay.

- Device: Both AWR1243 and AWR1642.

- Software setup: mmWave Studio 2.1.1, Single Chip mode, Hardware trigger mode, (DCA1000 ARM, and Trigger Frame).

Do you have any idea about what might the issue be?

Thanks in advance,

Majid

0 Jin Lee over 1 year ago in reply to Majid Joshani

TI__Intellectual 2522 points

Hi Majid,

To bring out a specific signal, Pinmux_Set_FuncSel() should be provided the pin number and the desired signal functionality (macros provided in the SDK).

e.g. To bring out the SYNC_OUT signal on pin G13: Pinmux_Set_FuncSel(SOC_XWR16XX_PING13_PADBC, SOC_XWR16XX_PING13_PADBC_SYNC_OUT)

Please refer to this thread regarding LUA shell commands: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/913070/iwr6843-documentation-of-lua-shell-commands

0 Jin Lee over 1 year ago in reply to Majid Joshani

TI__Intellectual 2522 points

Hi Majid,

The the SYNC_IN pulse width should be less than 1us (minimum 25ns). The pulse periodicity should account for the frame periodicity+frame trigger delay.

Linking an older thread on HW trigger timing configurations: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1318786/awr1843aop-hw-trigger-sync_in-pulse

Thank you,

Jin

Sensors

Sensors forum

AWR1243BOOST: awr1642