Update to 3.15.1.1. While here, add a patch that affects me: I have a MSP430F5529 Launchpad connected via USB. Besides the issue where the devd config creates a broken symlink (PR 251616), I can't connect to my launchpad using mspdebug and tilib: $ mspdebug tilib 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.15.0.1 Copyright (C) 2013 TI, Inc. Using new (SLAC460L+) API MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: mspfet0013 MSP430_Initialize: mspfet0013 tilib: MSP430_Initialize: Interface Communication error (error = 35) tilib: device initialization failed With this attached patch that adds an additional delay to resetCommunication(): $ mspdebug tilib 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.15.0.1 Copyright (C) 2013 TI, Inc. Using new (SLAC460L+) API MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: mspfet0013 MSP430_Initialize: mspfet0013 Firmware version is 31501001 MSP430_VCC: 3000 mV MSP430_OpenDevice MSP430_GetFoundDevice Device: MSP430F5529 (id = 0x002f) I'm not really sure why this additional delay is needed, but since tilib seems to be littered with these, I'm not sure it would hurt.
Created attachment 220294 [details] Patch