• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 79 subscribers
  • Views 273 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-F6779: Unable to Evaluate Using EMDC

Abram Early
Prodigy 130 points
Part Number: EVM430-F6779
Other Parts Discussed in Thread: MSP-EXP430F5529LP, MSP-FET, UNIFLASH

I have been unable to get any response out of the evaluation kit or the launchpad after flashing the latest firmware to them. There is no communication on the UART, no LCD response, and no LEDs. (Only the launchpad blinks)

I've uploaded the following into the EVM430: "C:\ti\msp\EnergyMeasurementDesignCenter_1.40.00.03\EnergyMeasurementDesignCenter\example_projects\EnergyMeasurementDesignCenterWorkspace\EVM430-F6779_CT_3V_3C_60Hz\EVM430-F6779_CT_3V_3C_60Hz.txt"

And the following into the launchpad: "C:\ti\msp\EnergyMeasurementDesignCenter_1.40.00.03\EnergyMeasurementDesignCenter\hidbridge\TI_MSP_HIDBRIDGE__1_00_04_00__MSP-EXP430F5529LP.txt"

The launchpad shows the slow blinking LED, and the Energy Measurement Design Center is able to connect to the launchpad correctly. But there is NO communication across the UART except when unchecking "Connected" in the controller properties.

At this time, only Line 3 of the EVM is connected to a standard 120V outlet for availability and convenience reasons. Otherwise, I would have to spend all of my time in the cold warehouse. The out-of-box firmware worked in this configuration and gave accurate voltage and wattage output, so I expected it to work with the updated EMDC firmware.

I've double checked the connections for the UART according the documentation, and ran through the steps at least twice. The MSP-FET is able to connect to and flash the EVM, but nothing happens.

Is there something I'm missing here?

  • 0
    Prodigy 50 points

    I posted this question using the wrong account (It was from my previous company). This account that I'm replying with is with the relevant company.

  • 0
    Prodigy 50 points

    I have finally managed to get some response out of the device. However, the resulting figures aren't even close to correct, and I can't configure EMDC to reflect my board.

    Specifically, I cannot seem to configure EMDC to use an MSP430-67791 (Which is what is present on the board according to Uniflash and CCS, not an MSP430-67791A). Using the example project EVM430-F6779_CT_3V_3C_60Hz as a base, I open the properties for the controller, change "Device" and reconnect all of the connections. The wires will show up in the main diagram window. But as soon as I press OK, the wires are removed, and the controller is reset back to "MSP430-6779" and the connections are removed. And even if I generate code while the device says "MSP430-67791", the resulting code is targeting an MSP430-6779. MSP430-6779 is not even a selectable device when starting a new project.

  • 0 in reply to Abram Early
    TI__Mastermind 35150 points

    I think you may miss the HID bridge:

  • 0 in reply to Eason Zhou
    Prodigy 50 points

    No, the HID bridge is hooked up. Otherwise, I wouldn't have been able to get the values I did in my most recent update. Right now my questions revolve around the completely inaccurate readings and the inability to configure the EMDC for an MSP430-67791.

  • 0 in reply to Abram Early
    TI__Mastermind 35150 points

    It seems you have try to reselect the device. Have you try to generate code?

  • 0 in reply to Eason Zhou
    Prodigy 50 points

    I have, but both CCS and UniFlash report that the chip on the EVM is an MSP430-67791 (Without "A"), and complains when the binary is targeting a MSP430-67791A (With "A"). And MSP430-67791 (Without "A") is not a selectable device in EMDC. The change does not persist, and is not reflected in the generated code, or when reopening the properties.

  • 0 in reply to Abram Early
    TI__Mastermind 35150 points

    Do you mean that the reason why the detection result is not right may lies on the device part number is not supported by EMDC?

    To see the difference between A and no A, you can refer to this document:https://www.ti.com/lit/an/slaa666a/slaa666a.pdf

    As I tried, 67791 is a selectable device. Can you double check?

     

**Attention** This is a public forum