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.

FDC2212: Reset Does Not Set Registers to Default Values

Part Number: FDC2212
Other Parts Discussed in Thread: MSP430FR2676,

I have a setup with the FDC2212 communicating with the MSP430FR2676 via I2C. I have not been able to get the FDC2212 to drive the LC oscillator and receive data. I have set up the code to write the registers in the same order per the Application example in the data sheet. I have confirmed that the MSP430 is writing to the FDC2212 registers properly. However, I notice when I reset the device through either a SW reset command or by shutting it down via hardware and reenabling it, the registers seem to not be set at their default values according to the datasheet. For example, when I power on my unit, the FDC2212 is in shutdown mode by having the SD pin be pulled up to the supply pin. When the MSP430 initializes everything, it drives the shutdown pin low to enable the FDC2212. After enabling the FDC2212, I read the CONFIG register to see what values it is showing. Below are screenshots of what the value should be and what I am reading. I can share more register reads, if needed.

Data Sheet

MSP430 Read

As can be seen, bit 0 according to the datasheet should be set to 1 on a reset. I am reading it as a 0. There are a few other bits that are not reading properly as well.

  • Hello, 

    Sorry you are having this issue. I have a few clarification questions for you on this: 

    • Is it all registers that are showing this behavior or just some of them? 
    • Does the registers read the same each time? 
    • Does the issue occur on first startup when the board is powered on? 
    • Can you check the SD pin voltage with an oscilloscope to make sure there isn't any strange behavior occurring when the pin is changing states? 

    Best Regards, 

    Justin Beigel

  • Hi Justin,

    Thanks for the response. I checked the SD pin and it was accidentally getting driven high by a separate thread in the code, which was causing some issues. Thanks for your help.