AWR2243: Question about SOP=7 (I2C mode of operation)

Chris Meng

Part Number: AWR2243

Hi,

With SOP=7 (I2C mode of operation), does external host still need to check the pin P6 (SPI_HOST_INTR_1) of AWR2243 as the host interrupt function during I2C communication?

I checked the code of mmWaveLink_SingleChip_Example in DFP 2.2.3.1 and I found for SPI/I2C mode, the only difference is to use SPI or I2C for read/write operation.

Can we update AWR2243 datasheet and mmWave-Radar-Interface-Control.pdf in DFP package to provide more detail info of the I2C mode of operation? I can't find detail info of I2C mode.

Thanks,

Chris

over 4 years ago

0 Cesar over 4 years ago

TI__Guru**** 150174 points

Hi,

Please give us some time to review your question

thank you

Cesar

0 Jitendra Gupta over 4 years ago

TI__Guru 70100 points

Hi Chris,

There is much I2C information is provided in AWR2243 Datasheet as an alternative to SPI connection.

https://www.ti.com/lit/ds/symlink/awr2243.pdf

Here are some snapshot from datasheet.

Please let us know what exact information you think is missing, we'll update accrongily.

Regards,

Jitendra

0 haoming zhao over 4 years ago in reply to Jitendra Gupta

Prodigy 10 points

Hi Jitendra,

We have seen this I2C information in datasheet, but we don't find communication sequence about I2C mode in mmWave-Radar-Interface-Control.pdf, the I2C and SPI use the same communication sequence? If they use the same communication sequence, then I2C doesn't have the simailar HOST INTR pin(SPI_HOST_INTR_1) as SPI, how can host check the "HOST IRQ line" of I2C mode?

Here are some snapshot from mmWave-Radar-Interface-Control.pdf.

+1 Jitendra Gupta over 4 years ago in reply to haoming zhao

TI__Guru 70100 points

Here, Protocol communication over I2C will be same as SPI. i.e. after Command data is being written to I2C slave (AWR2243), Host(mmwaveLink) needs to wait till HostIRQ high-> then write CNYS pattern-> AWR takes HostIRQ down-> Host reads the response message over I2C.

So effectively you need to change mmwavelink communication callbacks to I2C only, all other callbacks would be same as SPI implementation.

Regards,

Jitendra

0 Chris Meng over 4 years ago in reply to Jitendra Gupta

TI__Mastermind 38126 points

Jitendra,

Thanks for reply. It is clear now. Pls kindly update such info in AWR2243/DFP document.

Best Regards,

Chris

0 Bruce Lee over 4 years ago in reply to Jitendra Gupta

Prodigy 10 points

We have succeeded over I2C by your supporting. Thanks!

0 Jitendra Gupta over 4 years ago in reply to Bruce Lee

TI__Guru 70100 points

Great, glad to hear that now you are able to communicate over I2C to AWR device.

You can create a new thread for any future queries.

Regards,

Jitendra

0 Ron Persky over 4 years ago in reply to Chris Meng

Prodigy 160 points

Hi Chris,

I am trying to work with AWR2243 at SOP=7 and external host, with no luck.

It seems that I can't communicate with AWR2243 over I2C at-all.

I am setting SOP to the value 7, releasing nRESET, and pinging I2C 0x28 - but there is no answer.

Can you please elaborate if there were any difficulties bringing up this setup ?

What host are you using ?

Regards,

Ron

0 Jitendra Gupta over 4 years ago in reply to Ron Persky

TI__Guru 70100 points

Hi Ron,

Could you check these points:

1. As soon as device booted in SOP=7, do you see HostIRQ high?

2. If yes then at this point you need to write 16bytes of CNYS pattern (0x5678...) to AWR device over I2C, so it takes HostIRQ down.

3. When HostIRQ down, Host application then can read the asynchronous event from device over I2C.

I hope you are using mmwavelink to communicate with AWR device over I2C where you need to implement all the I2C communication callbacks.

Regards,

Jitendra

0 Ron Persky over 4 years ago in reply to Jitendra Gupta

Prodigy 160 points

Hi Jitendra,

The HostIRQ is high.

But when I try to write the CNYS pattern, I get NACK from address 0x28.

Also, the HostIRQ is always high, even when device is in reset (holding nRESET in low).

Regards,

Ron

0 Jitendra Gupta over 4 years ago in reply to Ron Persky

TI__Guru 70100 points

Can you capture the I2C signal and interpret if that is correct CNYS pattern like below.

0x5678 0x8765 0xFFFF 0xFFFF 0xFFFF 0xFFFF 0xFFFF 0xFFFF

AWR device will take HostIRQ down when it receives correct CNYS data.

Regards,

Jitendra

0 Ron Persky over 4 years ago in reply to Jitendra Gupta

Prodigy 160 points

Thank you Jitendra!

After sending this pattern, address 0x28 appeared.

0 Jitendra Gupta over 4 years ago in reply to Ron Persky

TI__Guru 70100 points

Hi Ron,

I didn't get your response here.

So with this CNYS pattern written over I2C, do you see HostIRQ going down?

Only after HostIRQ goes down, Host is eligible to read the asynchronous event message from AWR device over I2C. mmWaveLink takes care of this flow using all those callbacks.

0 Ron Persky over 4 years ago in reply to Jitendra Gupta

Prodigy 160 points

Correct.

After writing this pattern the HostIRQ went don and I was able to communicate over I2C.

0 Jitendra Gupta over 4 years ago in reply to Ron Persky

TI__Guru 70100 points

Hi Ron,

Ron Persky said:
I was able to communicate over I2C.

Did I get it correct that you are able to make it work over I2C?

Regards,

Jitendra

Sensors

Sensors forum

AWR2243: Question about SOP=7 (I2C mode of operation)