This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RF430FRL152HEVM: Cannot get any response via SPI host interface

Part Number: RF430FRL152HEVM
Other Parts Discussed in Thread: CC3200-LAUNCHXL, MSP-FET, RF430FRL152H, CC3200

Hi,

I'm trying to talk to RF430FRL152HEVM working on top of CC3200-LAUNCHXL via SPI interface. So far I cannot get any reasonable response.

On RF430FRL152HEVM: S6 switch is in "Supply", S5/S4 is in "0", S3 is in "S[lave]". I've also un-soldered R20 (just in case).

Here I'm trying to read some reg (all valid FRAM regs yield 0). The only response I get is MISO toggled with ~100uSec shift compared to CS signal. The tag is readable via 15693.

I do not have MSP-FET by hand yet.

Please suggest me where to dig, right now I'm kinda out of ideas.

Thanks,

Oleg

  • Hello Oleg,

    If you don't have an MSP-FET in hand I presume you are using Default Firmware? The Default Firmware doesn't support SPI mode.

    Furthermore, we don't have a TI example with the RF430FRL152HEVM in a slave mode for SPI. You will need to develop such an application yourself. I would recommend starting from the RF430FRL152H_SensorHub_Project.

  • Hello Ralph,

    Thanks for a prompt answer! So the documentation is not correct then -- it says nothing about the lack of SPI slave support by the ROM code, please consider updating it accordingly.

    BTW I managed to get a communication working via I2C, no programming was required.

    Regard,
    Oleg
  • Hello Oleg,

    Honestly I must confess I had a moment of complete stupidity with my prior reply. I was thinking along the lines of sensors and application code and not host/slave and ROM code. The ROM code does support both SPI and I2C slave modes.

    This post explains the pin states needed for each configuration: e2e.ti.com/.../2028385

    Sorry about that...
  • Hello Ralph,

    No problem, at least I got the communication working via I2C, so I can go on with my development. Although it's not very nice of a solution because when I stack the RF430 EVM on top of CC3200-LAUNCHXL, I need to make some patchwork in order to switch the interface to CC3200's I2C pins -- SPI communication does not require that.

    I've read a comment you've referenced, and I'm sure I drive CS pin high for SPI selection during the reset of RF430. For me, it seems that SPI communication starts working (MISO driven low in response to CS), but the RF430 chip somehow does not like the SPI reception so it remains silent. Maybe I'm wrong here.

    So it'd still be very nice to hear from someone who has experience bringing up slave SPI mode on RF430.

    Thanks,

    Oleg

  • Hello Oleg,

    When you say reset of the RF430 - do you mean a full power down and power up sequence to allow the ROM to re-sample the pins?

    Do you know if the CC3200 is sending out SPI packets with the SPI mode that the RF430FRL152H expects? Have you tried different SPI modes?

    The device will support all SPI modes, but would need to be configured for anything other than the default. It looks like the default will be UCCKPH = 0 and UCCKPL = 0 as the bits are set to 0 on startup.
  • Hello Ralph,

    I reset it using a 1->0->1 sequence on an NMI/RST pin, also tried resetting using S2 button on the RF430 EVM. I'm sure any of these are enough to trigger RF430 to re-sample the switch positions.

    Yes, CC3200 uses mode 0: inactive CLK is '0' and the data is clocked out with the rising edge of the CLK signal. Tried just in case all the possible combinations of S4/S5 -- still no effect.

    BR,
    Oleg