|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#14
|
||||
|
||||
|
Re: TI Launchpad "Bricked"?
Quote:
Update: Energia could update the firmware to get something on the board again. Now, I can detect it in the Gamepad Tool. However, when I try to program via the GT, we get: The program encountered an error: Error 5000 Gamepad Tool.vi<ERR> Programmer did not succeed. Check the log for details. Looking at the log I see: tilib: MSP430_Initialize: Interface Communication error (error = 35) tilib: device initialization failed MSPDebug version 0.20 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 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. MSP430_Initialize: COM8 If I try the technique listed in post #7, I get: C:\Users\mike>"C:\Program Files (x86)\FRC Gamepad Tool\Tools\mspdebug\mspdebug.exe" --allow-fw-update tilib "prog ../../Firmware/MSP430-GamePad-Option1.hex" MSPDebug version 0.20 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 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. MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: COM8 MSP430_Initialize: COM8 tilib: MSP430_Initialize: Interface Communication error (error = 35) tilib: device initialization failed Still no joy. My other two work fine. But, this is the one from the KOP. TIA. Mike |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|