Other Parts Discussed in Thread: MSP-FET
The system that we're developing uses two MSP430F5359 microprocessors running in tandem. We maintain a continuous integration test system that has 20 or more of these modules continuously running test programs. The CI system occasionally reprograms the modules-under-test using MSP-FET flashers and MSPFlasher_1.3.20.
Occasionally, attempts to reprogram a module-under-test result in the MSP-FET flasher returning “Error 59: Could not write device memory”. According to my test engineer, once a module has started returning this error, it persists until corrective action is taken. We're a little unclear on exactly what action actually clears the failure but it may be some combination of 1) unplugging and replugging the MSP-FET flasher from its USB cable; 2) powering down and repowering the module-under-test; and 3) perhaps leaving it all unit unpowered and/or unplugged for as long as 30 minutes. (The problem hasn't occurred so frequently that we've been able to narrow this list down much.)
I've tried to read the source code for the MSPFlasher and for the (apparently appropriate) DLL but between the app, the DLL(s), Windows USB (HID?) support, firmware in the MSP-FET flasher, and funclets loaded into the target device, it's quite the twisty-turny maze of passages, all alike.
Can anyone state, in simple language, what is the approximate root cause of “Error 59: Could not write device memory”? At which of those many functional levels is this error occurring/being detected?
