I have a project that uses 2 separate MSP430 microcontrollers. Both of them need to have different firmware uploaded to them. My place of work use the 8-way MSP-GANG programmers to program instruments in production.
The annoying thing with this, is you cannot put different firmware on different ports (or there isn't a way I could see), so I would be forced to program one, change the 'image file' and program the other.
The way I have got around it is to write a script by following the instructions in the USER GUIDE (page 24 – 30). Now, via the MSP-GANG software, I can press the 'GO' button and the script runs, programming the first microcontroller on one port, then the second one on another port. This is fine, but via this software, you can also edit the image files and change memory locations of different images. We would rather the production staff not have the ability to access any of this, so I have been trying to find a way to have the script run on a standalone unit.
I cannot seem to be able to save the script to any image file, and when putting it on an SD card, it just comes up with an error.
Does anyone know if it is possible, and how to run a script on a standalone GANG programmer?
Best Answer
The user guide certainly makes it sound like your options are "standalone" or "script" and not a combination.. but your TI rep might have a work-around.
That being said I figured I would offer some suggestions based on some previous programming setups:
1) In the past, we would create a batch file to call the programming utility via command line. That way, the Contract Manufacturer (CM) just has to hit a button that says "PROGRAM FOR COMPANY X". If the concern is what the tool opens up in script mode, that might be an option.
If the concern is your CM modifying the script, I wouldn't be super concerned. In general CM's want to minimize how much they mess with stuff, since any "tweaking" might result in a negative impact to their business. I would worry more about scripts getting mixed up and them having to call you rather than someone messing with the file.
2) Especially since we're talking about a company with an actual production process, it might not be a bad solution to just get two programmers in standalone mode and key /color-code / poka-yoke the crap out of it so they can't mix up the programmers. That way a technician can just hit the button on both programmers, and there's really no impact beyond having to plug in two cables rather than one.