CC2640R2F: SDKv5.30: Simple Peripheral Off-Chip OAD does not finish if set CC2640R2_LAUNCHXL_SPI0_CSN IOID_11

Hi kel,

What are you seeking to do?  CC2640R2_LAUNCHXL_SPI_FLASH_CS/IOID_20 is already used for external flash CS and setting the csnPin of spiCC26XXDMAHWAttrs from PIN_UNASSIGNED to a valid IOID most likely changes the SPI TI Driver behavior in a manner not expected for the operation of the simple_peripheral_oad_offchip example, causing communication with the external flash memory to fail.  Also note that the same configuration is expected for the bsp_spi.c/h files from the bim_oad_offchip project.

Regards,
Ryan

Hi Ryan,

I am working on a CC2640R2F + NXP NTM88 TPMS project. The CC2640R2F communicates with NXP NTM88 using SPI interface. When the device is not connected every 2 seconds reads sensor data from NXP NTM88 and advertises the sensor data. When it is connected to smart phone disables the task that reads the sensor data. The device while connected is used for OAD only. Here is connection diagram.

I reviewed the code SPI external flash for OAD and SPI NTM88 can work together. Maybe not all.

-kel

Thanks for sharing.  You can manually drive CC2640R2_LAUNCHXL_SPI_FLASH_CS low when not using the OAD feature with external flash, and likewise control NXP NTM88 CS functionality through software to control when it is enabled/disabled.

Regards,
Ryan

Hi Ryan,

Why using the original Simple Peripheral Off Chip OAD example program if I set the CC2640R2_LAUNCHXL_SPI0_CSN from PIN_UNASSIGNED to IOD_11 the OAD fails using SimpleLink Starter App?

My communication with SPI NTM88 already works and I can see the set SPI CS IOD_11 automatically goes low during SPI communication. I am not sure I can replicate the same way manually.

-kel

Ryan Brown1 said:

Is the NXP NTM88 connected when you evaluate the Simple Peripheral Off Chip OAD example program?

No. I have isolated the root cause of the OAD failure to be changing CC2640R2_LAUNCHXL_SPI0_CSN from PIN_UNASSIGNED to IOD_11. That is the only code change.

I have only captured SPI communication of CC2640R2F and NXP NTM88 using logic analyzer.

-kel

Hey Kel,

I've tried to reproduce this issue but am unable to using a launchpad. I believe Ryan voiced my main concern in his initial reply. Are you able to verify that you can write to external flash while also connected to the NXP chip? The OAD will not succeed if it is unable to write to the ext flash.

Hi Ammar N,

Markel Robregado said:

root cause of the OAD failure to be changing CC2640R2_LAUNCHXL_SPI0_CSN from PIN_UNASSIGNED to IOD_11. That is the only code change.

Using only the CC2640R2F Launchpad and original Simple Peripheral Off-Chip OAD example program. This is not right I set  CC2640R2_LAUNCHXL_SPI0_CSN from PIN_UNASSIGNED to IOID_11 causes OAD failure. This is something that happens internally, which I have no idea. As Ryan mentioned could change SSI hardware module from 3 wire to 4 wire, but CC2640R2_LAUNCHXL_SPI0_CSN from PIN_UNASSIGNED to IOID_11 is not even executable code that I wrote.

Anyway, I will find alternative ways to solve my problem. I will mark this post as answered.

-kel

Just want to update both of you, the NTM88 communication works in 4 wire SPI configuration. But, if I configure it to 3 wire SPI configuration and manually turn the NTM88 SPI CS low and high, I am not able to read the NTM88 sensor data. So, this is now an impossible task.

Ammar N Do you know the property of SPI CS pin at 4 wire SPI configuration. Is it push/pull or pull ony?

-kel