could you please share more details about the application that you want to build?
Is it that you want to use the EMDC GUI to configure the MSP430F6779 and then interface the MSP430F6779 with another MSP430? Or do you want to use the EMDC with a MSP430 different than MSP430F6779?
Please let me know which of the scenarios you need help on.

Questions
1) I have studied the documentation on EMDC - my understanding is that meteorology values and way to update calibration parameters are exposed on UART by default by EMDC. please confirm its correct.

2) Id like some help on how to read and write data from EMDC on Host MCU. Code will be helpful. it does not have to be extremely detailed basic will do.

Excellent! We provide several pre-configured EMDC example projects that match our supported EVMs. However, you can always use these as a starting point for your design by saving the project as your custom project and then making your changes rather than starting a new project from the ground up.

Bilal.m.Ahmad

Generate code and deploy it as is (no code changes at all) using JTAG.

You can program the EVM430-F6779 using the provided example firmware images that match the EMDC example projects. There's no need to generate code as long as you use the matching EMDC project and don't need to change anything. If you'd like, you can use the EMDC example project to generate the code, import to CCS or IAR, and then program the EVM430-F6779 over JTAG using the MSP-FET.

Bilal.m.Ahmad

Connect another MSP430( lets call it Host) via UART.

This is possible as long as the UART protocol and state machines match. Please keep in mind that the protocol packets change based on your project configuration - if results aren't needed, then they aren't included to keep the protocol transmission leaner.

Bilal.m.Ahmad

Read meteorology values on host MCU.

Definitely possible. See comments above.

Bilal.m.Ahmad

write calibration parameters to EMDC from Host MCU.

This is also possible if you follow the flow described in the EMDC Technology Guide.

Now, onto your other questions.

Bilal.m.Ahmad

1) I have studied the documentation on EMDC - my understanding is that meteorology values and way to update calibration parameters are exposed on UART by default by EMDC. please confirm its correct.

Yes, that's correct.

Bilal.m.Ahmad

2) Id like some help on how to read and write data from EMDC on Host MCU. Code will be helpful. it does not have to be extremely detailed basic will do.

Have you had a chance to read through the "Communication Protocol Spec" chapter in the EMDC Technology Guide? More specifically, the "Protocol Overview" section shows how the EMDC GUI communicates with the target MSP430 device. As you can see in the diagram below (found here), the application code running on the target MSP430 device switches modes to start sending results (again, this depends on the results selected in the EMDC configuration before code generation) to the EMDC GUI. If your host MCU follows the same flow and uses the same protocol and baud rate, then you'll be able to read data from MSP430 using your host MCU.

Hello.
I found out one thing: when I monitored serial port activity I observed 3 extra bytes before MSP design center ID byte, they are 0x55, 0xAA and 0x0A. These bytes are not described in the spec. How come that they appeared on the line? Also, is CRC checked in the evaluation board?

You're exactly right. This is the three-byte header that's used by both our CapTIvate and Energy Measurement Design Centers' communication protocol between the GUI and MSP430. What you're observing is:

[Byte 0] Sync byte at position 0, equal to 0x55

[Byte 1] Blank byte at position 1, equal to NOT 0x55 (0xAA is typically used)

[Byte 2] Length byte at position 2, equal to the checksum of everything after this byte up to the two checksum bytes

if we change code that is generated by EMDC to change baud rate. Would the EMDC software work with 115200 baud rate. reason we what to do that is because the device we would like to use does not support 250K baud rate.

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.