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.

MSP-EXP430G2ET: Error: Could not set device VCC

Part Number: MSP-EXP430G2ET
Other Parts Discussed in Thread: IO-EXPANDER-EVM, MSP430G2553, TCA9555, UNIFLASH

I have MSP430G2553 and IO-Expander-EVM. When I execute IO-Expander Flash.bat, I get the following in cmd window: 

Programing IO_Expander.txt into MSP430G2553 ......
* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP430 Flasher v1.3.0 *
* | / *
* -----|/-------------------------------------------------------------------- *
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM5.
* Initializing interface on TIUSB port...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Reading HW version...done
* Setting VCC to 3000 mV...
# Exit: 44
# ERROR: Could not set device Vcc
* Starting target code execution...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (Could not find device (or device not supported))
* ----------------------------------------------------------------------------
*/
Press any key to continue . . .

---------------------------------------------------------------

The MSP430 executes the OOBE demo (leds and Temperature documented in User Guide doc.) without problems. This controller is M430G2553 a newer version than one shown in TI slvua59a  July 2014 page 5. The UART jumpers are different on the previous MSP430 from the one I have.

Could you provide guidance on solving this problem. I plan to evaluate the TCA9555 expander once the EVM is functioning.

  • Hi Ted,

    I recommend that you use our Uniflash tool to program our micro-controllers:

    https://www.ti.com/tool/UNIFLASH

    This tool is updated to address our new products.  Let me know if you have any problems flashing your board with this tool.

    BR,
    Leo

  • Download and installed UniFlash ver 6.1.0.2829 

    When using UniFlash to load file IO_Expander.txt. In UniFlash I select:
    TI MSP430 USB1>MSP430G2553
    I select image file: IO_Expander.txt  This file is located in folder MSP430 Flash and is the one received in slvc564a.zip 
    Action: I select Verify image in Uniflash

    Get this error:

    9/5/2020, 11:08:35 AM] [ERROR] MSP430: File Loader: Verification failed: Values at address 0xC006 do not match Please verify target memory and memory map.

    --

    It would help if you tell me why the original error occurs. Secondly has the expander software been verified with the MSP controller version that I received in the iO_expander evm product. I hope you can provide help with this issue.

  • Hi Ted,

    I don't know exactly which images were used to test with our Uniflash utility. This tool is updated and continues to be supported with our new devices. Before verifying the image, you need to load the image onto your device. Can you confirm that you were able to load the image to your device before trying to verify it?  

    BR,
    Leo

  • Hi Ted,

    From your original message, it looks like the MSP flasher utility didn't recognize the device.  The Uniflash utility should be able to scan and identify the device if it is properly inserted into the socket.  The older version of the G2 Launchpad(which I have here) comes with a G2452 and a G2553 micro-controller. Can you confirm that the chip on your board is the G2553 and not the G2452?  

    BR,
    Leo

  • The Uniflash has worked by reporting that I to update to the MSP. Once update completed, the Uniflash detected the comport and the MSP430G2553. I used Uniflash to load the IO_Expander.txt image file and the file loaded without errors. Therefore I will consider this request closed, thank you for your help.

    I still have questions regarding the Expander EVM GUI software that control the ports because that is not working but I will submit another request after I explore that further.

**Attention** This is a public forum