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.

EVM430-FR6047: MSP communication with external controller

Part Number: EVM430-FR6047

Hello

I would like to communicate with my msp direcly to another microcontroller. I believe I can use the i2c pins on the board COMM_SDA, COMM_SCL, COMM_IRQ and using the USS Design Center Packets. I would like to have some clarification for this communication. For example for the command 0x81 which controlls the Number of Pulses if I want to write a new value to the MSP from my microcontroller I should send something like that :

0x0A 0x55 0xAA 0x09 0x04 0x81 0x01 0x12 0x34 0x00 0x00 0xCC 0x00

The first byte is the slave address(MSP) with the read/write bit set to 0 for write. The second and third are the sync and blank byte respectively. Next is the length byte and the Design Center Id byte. Then we have the command byte and the read/write byte set to 1 for write. Next are the two bytes that hold the value, the other two that we do not care and the checksum. Is this correct? Will I receive a response from this?

Next if I want to read that value from the MSP to my microcontroller I should send something like that:

0x0A 0x55 0xAA 0x09 0x04 0x81 0x00 0x00 0x00 0x00 0x00 0x85 0x00

The change here is that the byte after the command byte, the Read/Write byte is now 0  for read and no values are in the payload.

Then I would receive a response from the MSP to my microcontroller like:

0x0B 0x09 0x04 0x81 0x01 0xXX 0xXX 0x00 0x00 0xXX 0xXX

The first byte has changed since we want to write with this command the address is the same and the last bit is now 1 and the payload packets now have the value we want.

Is this the correct behavior or I have misunderstood something?

Thank you for your time

Nomikos Panagiotis

**Attention** This is a public forum