New USB MSP-FET: tilib: MSP430_VCC: Could not set device Vcc

[tmanaud]

I'm trying to use the "new" MSP-FET (black usb box), with the msp430.dll compiled from source available on TI (MSPDS-OPEN-SOURCE, v3.10.001.000)

And encounter this error:

MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer dlbeer@gmail.com
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

Using new (SLAC460L+) API
MSP430_GetNumberOfUsbIfs
MSP430_GetNameOfUsbIf
Found FET: ttyACM0
MSP430_Initialize: ttyACM0
Firmware version is 31001600
MSP430_VCC: 3000 mV
tilib: MSP430_VCC: Could not set device Vcc (error = 10)
tilib: device initialization failed

Is this in any way related to:
https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/614826
As the serial number of my MSP-FET is indeed starting with 17

[dlbeer]

On Thu, Oct 19, 2017 at 02:32:26PM +0000, Tweepy wrote: I'm trying to use the new MSP-FET (black usb box), with the msp430.dll compiled from source available on TI. And encounter this error: > MSPDebug version 0.25 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2017 Daniel Beer ***@***.***> > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. > > Using new (SLAC460L+) API > MSP430_GetNumberOfUsbIfs > MSP430_GetNameOfUsbIf > Found FET: ttyACM0 > MSP430_Initialize: ttyACM0 > Firmware version is 31001600 > MSP430_VCC: 3000 mV > tilib: MSP430_VCC: Could not set device Vcc (error = 10) > tilib: device initialization failed Is this in any way related to: https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/614826 As the serial number of my MSP-FET is starting with 17

Yes, it possibly is, although I have no information on what the newer versions of CCS do differently. If somebody who has time can trace the DLL calls (or otherwise knows what sequence of calls should be used at startup), then I can replicate it. Cheers, Daniel

…

-- Daniel Beer <dlbeer@gmail.com> http://dlbeer.co.nz/ PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B