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.

MSP430I2020: IAR Toolchain and Legacy e-meter Library Build configuration

Part Number: MSP430I2020
Other Parts Discussed in Thread: MSP-GANG

TI Friends & Family,

Our customer has some additional questions regarding i2020 e-meter with the legacy library and IAR toolchain:

  1. Do we recommend that “emeter-toolkit” should be built as a Library with configurations shown on the screenshot attached?

 

  1. Customer will be using MSP-GANG Programmer to program the metering IC (MSP430-2020). Based on the MSP Gang Programmer User’s Guide (https://www.ti.com/lit/ug/slau358q/slau358q.pdf?ts=1610126148828&ref_url=https%253A%252F%252Fwww.google.com%252F) it appears users can select only a single code file (TI.txt) to be programmed (2.1.1). Therefore, I assume that one of the three projects should be executable and two other projects should probably be libraries. Does it make sense? If so, which project should be built as the executable one?

 

  1. Also, when building the “emeter-metrology” project some errors [Pe1696] are generated (see screenshot attached). It seems like the “signal.h” and “inttypes.h” libraries could not be found. Do you know how one can fix this error?

TY,
CY

  • Hi Chris,

    Thanks for posting your question to E2E.

    Chris Yorkey said:
    Do we recommend that “emeter-toolkit” should be built as a Library with configurations shown on the screenshot attached?

    Yes, that's correct. Both the toolkit and metrology projects should be built as libraries.

    Chris Yorkey said:
    Customer will be using MSP-GANG Programmer to program the metering IC (MSP430-2020). Based on the MSP Gang Programmer User’s Guide (https://www.ti.com/lit/ug/slau358q/slau358q.pdf?ts=1610126148828&ref_url=https%253A%252F%252Fwww.google.com%252F) it appears users can select only a single code file (TI.txt) to be programmed (2.1.1). Therefore, I assume that one of the three projects should be executable and two other projects should probably be libraries. Does it make sense? If so, which project should be built as the executable one?

    The three projects should be compiled in this order: toolkit > metrology > application. The executable generated by the application project is the one that should be used for programming the device.

    Chris Yorkey said:
    Also, when building the “emeter-metrology” project some errors [Pe1696] are generated (see screenshot attached). It seems like the “signal.h” and “inttypes.h” libraries could not be found. Do you know how one can fix this error?

    I haven't seen this error before, but I suspect it has to do with the directories not being included for these files. I searched the forum for the compiler errors and found several threads that should help. One recommended going to Project -> Options -> C/C++ compiler -> Preprocessor and add the directories where the files can be found.

    Regards,

    James

  • Very helpful, James!  Really appreciate the detailed replies here.  Customer is up and running at this point with their legacy builds.  Thanks for getting us going in the right direction.  I'm guessing this info will be helpful to current/future customers as well.

    Regards,

    Chris

**Attention** This is a public forum