MSP430F5438A: Interfacing DS3234 RTC module with the board ,

Hey Nithesh,

Start with a TI-provided 3-wire SPI example and modify such that it follows the timing diagram specifications of the DS3234. You will at least need a GPIO-controlled CS line active low, SPI clock inactive state high (UCCKPL = 1), and data change on the first SPI clock edge & captured on the following (UCCKPH = 0). Remember that dummy data must be written out to drive the clock in order to read in data, this is common SPI protocol.

Regards,
Ryan

Thanks Ryan, 

I was planning to connect MOSI and MISO pins to defined pins of Microcontroller and CLK and CS to any of the GPIO, Will this type of connection give the reliable result?

Nitesh,

You will need to connect the MISO, MOSI, and CLK pins to the respective UCAx/UCBx peripheral driving the SPI communication. Only CS is used on any GPIO pin.

Regards,
Ryan

Hey Ryan, 

But if we don't have a CLK pins (UCAx/UCBx) available on microcontroller we can use GPIO pin and make it work!

like toggling it every time we require output, do we face any issues with this!

Bruce McKenney47378 said:

but for short transactions it probably won't make much of a difference.

Hey Bruce, 

Can you elaborate this.

But Whenever the microcontroller is on, it will be taking the value depends on the time delay given by us !!! 

I'm not sure I understand the question.

You use the SPI CLK signal only when you want the DS3234 to do something (an SPI "transaction"), which could be once/second or even once/year.

The Real Time Clock inside the chip has its own clock source (the crystal).

My bad, you are right about that. 

My doubt was if I use software CLK will there any reliability issues during the long run?

Thank you Bruce,