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.
Part Number: MSP430F6779
Is there any help available on interfacing EMDC with another MCU over UART.
Please verify the answer by clicking the green "RESOLVED MY ISSUE " button in case the reply solved your question.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
If I had answered to your question, please mark this post as Resolved.
In reply to Britta Ruelander:
In reply to Bilal.m.Ahmad:
Thanks for your interest in using EMDC. First, I would recommend that you update from the initial version v1.20.00 to the latest version v1.30.00. Here's some feedback.
Bilal.m.AhmadDesign energy measurement solution using ENERGY Measurement Design Center (EMDC) GUI.
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.AhmadGenerate 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.AhmadConnect 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.AhmadRead meteorology values on host MCU.
Definitely possible. See comments above.
Bilal.m.Ahmadwrite 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.Ahmad1) 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.Ahmad2) 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.
For more details about the packet structure, refer to the "MSP430 EM Design Center Packet Structure" section in the EMDC Technology Guide.
I hope this helps!
In reply to James Evans:
Bilal.m.AhmadI aim to deploy the code as it generated by EMDC on to MSP430F6779 EVM.
Bilal.m.AhmadWhat is the default baud rate?
The default baud rate is 250kbaud. I'm not sure how we missed adding that to the documentation. I'll get it added in the next release.
In reply to Oleg Irinichev:
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:
More information about the packets can be found here in the CapTIvate Technology Guide. It does seem rather hidden in the documentation, so I'll add this feedback and request the overall packet structure gets updated in the EMDC Technology Guide.
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.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.