Is there some plan to support 677x in Energy library and CCS?
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.
Is there some plan to support 677x in Energy library and CCS?
Hi Rafael,
I would recommend searching for F6779 on the TI Designs: Reference Design library: www.ti.com/tidesigns
I found this when I searched there: http://www.ti.com/tool/TIDM-THREEPHASEMETER-F6779
Which includes a download that has energy library software in it for F677x: http://www.ti.com/lit/zip/tidc256
Regards,
Katie
Hi Katie,
I already have checked slaa577 (the same firmware as tidc256).
My question is about slac488/slaa538 (http://www.ti.com/lit/zip/slac488) F6779 integration. It seems the code is better structured there (taxonomy toolkit/metrology/app/ makes more sense to me) and it also supports CCS.
IAR tools are expensive and CCS can be used for full firmware development with XDS100 debug probe.
Is there some on going project to support F6779 in slac488 in near future?
Regards,
Rafael.
Hi Rafael,
I will check with our metering team that develops this software and get back to you.
-Katie
Hi Rafael,
I checked with the metering team. They said this:
"We are working on a full Energy-Lib release, with CCS and IAR support across all emeter devices and EVMs"
This means that F6779 will be added into the slac488 energy library zip file eventually. However, they also said that they do not have any expected release date for this yet, so this is probably still fairly forward-looking. For now all we have for the F6779 is the code I pointed you to before on TI Designs, which is a customized energy library for the F6779.
Regards,
Katie
Thanks Katie.
I hope to see slac488 support soon. I will try to migrate sla577 code from IAR to CCS.
Regards,
Rafael.
Katie,
It has been almost three months since the last update on "We are working on a full Energy-Lib release, with CCS and IAR support across all emeter devices and EVMs". Could I please get an update with a target delivery date with at least quarterly resolution. Thank you in advance for the update.
Bart
Hi Bart,
I checked with the metering team again, but they still do not have this on the timeline. As I mentioned in my last post, it is on the list to eventually be updated, but it is still pretty forward-looking - so unfortunately they don't have an estimated delivery date. If you are working on a project in the near term, your best bet is still going to be to work from the 677x energy library that is here: http://www.ti.com/lit/zip/tidc256
Regards,
Katie
Katie,
Besides wondering if there's been any update from the metering team on Bart's question, I'd also like to know if there is GCC support for the 677x energy library (6779 in my case)?
Thanks,
Jim
Hello Mohan,
You can find links to the source code for each of the following MSP430F6779-based TI Designs in the product folder or in the Design Guide.
High Accuracy Three-Phase Electricity Meter with Tamper Detection (TIDM-THREEPHASEMETER-F6779)
Three-Phase Metrology With Enhanced ESD Protection and Tamper Detection Reference Design (TIDM-3PHMTR-TAMP-ESD)
Also, you may find the following reference helpful. It covers the differences between the non-A and A versions of this device.
Differences Between MSP430F67xx and MSP430F67xxA Devices
Regards,
James
MSP Customer Applications
Hello,
Thank you for your post and interest. We've received many requests for CCS support and are currently working to address this. I don't have a specific completion date yet, but most likely it'll be by the end of this year or early next year. In the meantime, I'd recommend using IAR, since the porting effort to CCS will be very challenging. Is it possible to port from IAR to CCS? Yes. Although I've never done it, I guess I'd start with reconstructing the project structures, adding the files to the projects, and then debugging the compilation errors (while referring to the IDE or compiler related documentation). Depending on the errors, I could envision that some functions would need to be manually re-implemented.
Take a look at the following thread.
Regards,
James
MSP Customer Applications
**Attention** This is a public forum