MSP430FR59941: Register read via I2C

Of course you can. But you have to write the code to do it.

I have found that a simple blinking LED is so useful for things like this that it is worth adding one to a design.

the board is under ICT tests, do you know if it is still possible to have register reads via I2C? 

Nathan Kowalsky

Hey David,

Is there any example or any paper with an explanation that defines how to access the registers?

BR,

Nathan 

Nathan Kowalsky said:

Is there any example or any paper with an explanation that defines how to access the registers?

No. But if you look you will find examples of SPI or I2C slave code. What data they send is up to you.

Hey David,

Got it. Can you please let me know where I should look? 

BR,

Nathan

Linked on the product page of course. Handy link to that placed at the top of this thread by the forum software.

Hey David,

My customer is looking to communicate over I2C using the MSP430FR59941. He has access to the TI-provided C code examples but needs help completing the setup and implementation for his use case.

 What he is trying to do:

• Use MSP430 as an I2C master to communicate with a connected device.
• Read the device ID register from that I2C slave.
• Configure the appropriate I2C pins for communication.
• Understand how to correctly set the slave address and perform read/write transactions.

What he needs help with:

1. Pin selection: Since the MSP430FR59941 supports multiple I2C-capable pins, which pins and module should he use for a standard I2C master setup?
2. I2C configuration: A short example or snippet showing how to:

• Initialize the selected I2C module as master
• Set the slave address
• Perform a simple read transaction (e.g., read one register such as a device ID)

3. Reference example: If there’s an existing TI driverlib example or CCS project that demonstrates this functionality, a link or pointer would be helpful.

He has confirmed that he can handle the actual data structure/protocol once the communication is working, but he’s currently stuck getting the basic I2C communication up and running from the MSP430 side.

 BR,

Nathan

1) A hardware design problem. Which pins fit the PCB layout best?

2) The TI provided code examples do this.

3) See 2.