RF430CL330H: VCORE do not work as expect in RF430CL330H

Part Number: RF430CL330H
Other Parts Discussed in Thread: MSP430F6779A,

Tool/software:

Hi

We use MSP430F6779A as I2C master, it has 3 slaves, one is RF430CL330H.

When power off the RF430CL330H, the vcore is still keep high, When SDA and SCL keep high.

Also find that is SDA and SCL from low to high, the VCORE will change from low to high.

It seem  I2c will wakeup the RF430CL330H.

Question 1:

1. how to disable I2C to trigger the VCORE from low to high ?

2. If SDA and SCL keep high, how to make the VCORE to low, when power is off?( when find in this case, VCORE is keep high)

  • Hi,

    When power off the RF430CL330H, the vcore is still keep high, When SDA and SCL keep high

      Is there a RF present? If a RF is detected, the VCORE will be raised to 1.5V. 

      Can you also show the schematic for the VCORE and how you provide the VCC to the device? Do you have the recommended Capacitor on VCORE pin and decoupling cap on VCC?  

      Please refer to this apps note about using VCORE to wake up the MCU. https://www.ti.com/lit/pdf/sloa200. Despite this apps note's intention is to demonstrate how to wake up the host MCU using a raised VCORE voltage due to an active RF, I think it provides some tips on where to troubleshoot your board. Is it possible that a RF is detected on your system and hence the VCORE is raised. Check if the host MCU is configured to wake up by any external GPIO pin. 

  •   I attached the hard design. I have check the link https://www.ti.com/lit/pdf/sloa200. It is not the same as ours.

    a. We use I2C_PWR to control the Power, but It seems the I2C communication will wake up the NFC, is it has register to disable it? If possible, can we set up a meeting to discuss it.

    b. The pull up resistor also will has the power consumption issue, it will cost about 2.5ma. When I2C_PWR is disabled and master SDA, SCL setup to GPIO high, the VCORE can not go to zero.

  • Hi WeiWei,

      I have responded to you in email. I will take it offline for ongoing discussion and hence close the thread here.