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-F67641: EMDC support for this micro?

Part Number: EVM430-F67641
Other Parts Discussed in Thread: MSP-FET, MSP430F6779A, MSP430I2041, MSP430F67641A, , MSP430F67641

We're designing an interface board for a telematics device to an AC generator using the MSP430-F67641A and have purchased the EVM as a development tool. I have questions that I am struggling to find the answers to:

1. I have installed the EMDC software but it does not list the MSP430-F67641 micro. Can I use EMDC for this application or is there another GUI tool I can use?

2. I tried to run Calibrator.exe after changing to the correct COM port in the .xml file as instructed but the program just hangs with 'not responding'. Does that .exe work with windows 10?

3. I determined I need an MSP-FET to program the micro in the EVM but do I also need a HID bridge or is that already part of the EVM?

4. I have installed CCS for coding but do I also need to install IAR?

Any help is appreciated, thanks.

  • Hi David,

    Thanks for your detailed post, and I'll do my best to answer your questions.

    David Parenti said:
    1. I have installed the EMDC software but it does not list the MSP430-F67641 micro. Can I use EMDC for this application or is there another GUI tool I can use?

    Unfortunately, the EMDC GUI and software library does not support MSP430F67641A at this time. The F67641A features both SAR and Sigma Delta ADCs for measuring high voltage AC whereas EMDC only supports devices with Sigma Delta ADCs such as the MSP430i2041 and MSP430F6779A. Thus, I would recommend using the legacy Energy library code that can be found in the Implementation of a Low-Cost Three-Phase Electronic Watt-Hour Meter Using the MSP430F67641 user's guide.

    David Parenti said:
    2. I tried to run Calibrator.exe after changing to the correct COM port in the .xml file as instructed but the program just hangs with 'not responding'. Does that .exe work with windows 10?

    Yes, I just verified that 'calibrator.exe' works on Windows 10 PC. Perhaps you didn't save the 'calibration-config.xml' file after you changed the COM port? After changing it to match the serial port shown in Device Manager, I saved the .xml file, opened the GUI, clicked the green connect button, and then results started showing up correctly. On the EVM, please make sure the "TX_EN" and "RX_EN" jumpers are populated on the RS232 headers (near the RS232 port). They should be connected left to right (parallel to the LCD). This may be why you're not seeing anything in the GUI.

    David Parenti said:
    3. I determined I need an MSP-FET to program the micro in the EVM but do I also need a HID bridge or is that already part of the EVM?

    Yes, you'll need the MSP-FET to program the MCU on the EVM if you'd like to make changes to the default code. The original code programmed on the EVM should work with the 'calibrator.exe' GUI out of the box. You do not need the HID bridge - this is only required when using EMDC.

    David Parenti said:
    4. I have installed CCS for coding but do I also need to install IAR?

    Good question. The legacy Energy library code was developed in IAR with no CCS support whereas EMDC supports both IAR and CCS. Since EMDC does not support the EVM430-F67641, then I would recommend installing IAR for your development using the legacy Energy library as a starting point.

    I hope this helps!

    Regards,

    James

  • Thank you James, that was helpful. I have calibrator.exe working now, it apparently needed a PC reboot after install.

    My issue now is with CCS. I have imported the emeter library files (app, metrology, toolkit) for the MSP430F67641A. In trying to do a build I get an error on this 2nd include statement in emeter-toolkit.h because no "ccs/extra_peripherals_definition.h" file was supplied. However the IAR folder and files were supplied, but I would prefer to avoid the cost of an IAR license.

    #if defined(__IAR_SYSTEMS_ICC__)
    #include <iar/extra_peripheral_definitions.h>
    #endif
    #if (defined(__TI_COMPILER_VERSION__) && __TI_COMPILER_VERSION__ >= 4000000)
    #include <ccs/extra_peripheral_definitions.h>
    #endif

    I tried to substitute the IAR version but that did not work. Do you know if there are ccs versions of the iar include files that you can point me to?
  • Hi David,

    David Parenti said:
    Thank you James, that was helpful. I have calibrator.exe working now, it apparently needed a PC reboot after install.

    Excellent!

    David Parenti said:
    My issue now is with CCS. I have imported the emeter library files (app, metrology, toolkit) for the MSP430F67641A. In trying to do a build I get an error on this 2nd include statement in emeter-toolkit.h because no "ccs/extra_peripherals_definition.h" file was supplied. However the IAR folder and files were supplied, but I would prefer to avoid the cost of an IAR license.

    Although some CCS files were included with this design, I'm not sure if CCS was ever fully supported. In the SLAA621 source code folder, I found the 'extra_peripheral_definitions.h' file under the slaa621c > Source > emeter-toolkit > include > ccs folder. Does it show up for you? You may need to add/modify the include paths for the compiler to find the file.

    Regards,

    James

  • Again thank you James, I am making progress.

    I have determined that the EVM we acquired uses the MSP430F67641 RevA chip, not the MSP430F67641A. This is not a problem for us now that I know and have switched to the proper code base.

    Back to CCS issues, when doing a build of the emeter-toolkit project, the MSP430 compiler can not handle the IAR .s43 assembly files (obviously). Should I exclude those from the build and how do I do that?

    In general, can you walk me through the process of building the SLAA621 code base I can run on the EVM? I believe I read instructions somewhere that said to build the emeter-toolkit first, then the emeter-metrology, then the emeter-app project. Is that the correct sequence?

    You help is greatly appreciated!

  • Hi David,

    David Parenti said:
    Back to CCS issues, when doing a build of the emeter-toolkit project, the MSP430 compiler can not handle the IAR .s43 assembly files (obviously). Should I exclude those from the build and how do I do that?

    Looking in the SLAA621 folder under the Source > emeter-toolkit > src > ccs folder, you should find CCS assembly files. However, I'm not sure these were ever tested. You should be able to add them to the toolkit project in CCS and remove the other IAR files by right-clicking them in CCS and clicking "Exclude from Build".

    David Parenti said:
    In general, can you walk me through the process of building the SLAA621 code base I can run on the EVM? I believe I read instructions somewhere that said to build the emeter-toolkit first, then the emeter-metrology, then the emeter-app project. Is that the correct sequence?

    Yes, that's correct.

    Regards,

    James

  • Thank you again James, hopefully you can keep helping me to get this working.

    I appear to be missing some library files. uart_comms.h is not supplied with slaa621 or the MSP430 library. Can you point me to where it might be?

    I'm not sure if these defs reside in the above file or other missing library files?

    "../emeter-app/debounce.c", line 51: error #20: identifier "BUTTON_PERSISTENCE_CHECK" is undefined
    "../emeter-app/debounce.c", line 54: error #20: identifier "DEBOUNCE_JUST_HIT" is undefined
    "../emeter-app/debounce.c", line 57: error #20: identifier "DEBOUNCE_RELEASED" is undefined
    "../emeter-app/debounce.c", line 64: error #20: identifier "BUTTON_PERSISTENCE_CHECK" is undefined
    "../emeter-app/debounce.c", line 67: error #20: identifier "DEBOUNCE_JUST_RELEASED" is undefined
    "../emeter-app/debounce.c", line 74: error #20: identifier "DEBOUNCE_HIT" is undefined

    And can you tell me why these errors occur?

    "../emeter-toolkit/src/accum48.c", line 59: fatal error #35: #error directive: "Don't know how to accum48"

    "../emeter-toolkit/src/bin2bcd16.c", line 72: error #2632: Modifiers are not allowed in printf_support=minimal mode

  • Hello David,

    I see that you've started a new thread for this question. Thus, I'll be closing this thread since the original question was about EMDC supporting MSP430F67641(A). Thanks.

    CCS/EVM430-F67641: Missing MSP430 Library files

    Regards,

    James

**Attention** This is a public forum