AWR2243: SOP Mode for loading from SPI & then communicating via I2C

Hi,

Our AWR2243 expert will review your question and will get back to you as soon as possible

thank you

Cesar

Hello,

Device selects communication interface SPI or I2C at boot time only which is based on SOP setting.

AWR2243 Datasheet explains this SOP config:

[SOP2 SOP1 SOP0] = [0 0 1] -> Functional SPI mode
[SOP2 SOP1 SOP0] = [1 0 1] -> Flashing mode
[SOP2 SOP1 SOP0] = [0 1 1] -> debug mode
[SOP2 SOP1 SOP0] = [1 1 1] -> Functional I2C mode

mmWave DFP provides an example for I2C communication, you can refer (C:\ti\mmwave_dfp_02_02_01_00\ti\example\mmWaveLink_SingleChip_Example)

Zoe Nuyens said:

loading the initial configuration via flash using SPI,

Do you mean loading firmware image via sFlash connected with AWR2243 device and later all the device configuration via I2C (post device boot)?

As switching b/w SPI and I2C is not possible after device booted up. So you can flash the firmware to the sFlash connected to AWR2243 and you can skip firmware download via I2C (which would be slower compare to SPI).

Hope I'm clear here, let me know if you have any other question.

Regards,

Jitendra

Additional Info:

I2C address is being set by i2cAddr in this example which is being handled by FDTI Port driver (available under mmWave Studio Installation)

C:\ti\mmwave_studio_03_00_00_14\mmWaveStudio\ReferenceCode\FTDILib\SourceCode

Look for these functions rlsI2cWrite(), rlsI2cRead(),  rlsI2CSendByteAndCheckACK() in mmwl_port_ftdi.c file.

Hi Jitendra,

Thanks for the response.

Jitendra Gupta said:

Do you mean loading firmware image via sFlash connected with AWR2243 device and later all the device configuration via I2C (post device boot)?

Yes, this is what I am asking for.

From your reply, it seems this is not possible. However, I don't understand this statement: 

Jitendra Gupta said:

As switching b/w SPI and I2C is not possible after device booted up. So you can flash the firmware to the sFlash connected to AWR2243 and you can skip firmware download via I2C (which would be slower compare to SPI).

The reason I wanted the firmware download via SPI is because it is faster. However, there is no SPI master in the system to look at statuses after the device is initialized. This is why I am interested in I2C communication only after the initial firmware is loaded. For instance, there seems to be no way to monitor e.g. temperature sensor readings via I2C if the initial firmware is loaded via SPI.

In order to support I2C communication to check statuses, etc.,it seems I will have to load the initial firmware using I2C as well. Do you see any alternative option?