Parallel Programmer Considerations
Kye
Posts: 2,200
I'm using a prop chip rig to load firmware for 5 ARM devices in parallel using the SWD protocol. The prop chip will be on a test rig that can program 5 boards at out of a panel of 20. The operator will position the rig above 5 boards, program them, and then move to the next 5.
Does anyone have experience designing firmware loaders for production? What types of things should I consider beyond just loading the firmware. Like, power issues, shorts, connectivity, etc.
Any thoughts would be appreciated.
Does anyone have experience designing firmware loaders for production? What types of things should I consider beyond just loading the firmware. Like, power issues, shorts, connectivity, etc.
Any thoughts would be appreciated.
Comments
I presume your rig is providing power to the target boards during the firmware loading, five plugs? Power control would allow for automatic post-programming power cycle testing. Hot plugging connector design could be warranted. Wear and tear will need to be addressed, spare leads usually solves this.
Current limiting via resistors is easy on the data lines but requires more work for power supply. Power up voltage measuring of all pins could help with fault reporting. Zenor diode clamping of all lines.
Search for smoke here - http://yro.slashdot.org/story/01/07/08/1425206/telocity-wants-its-gateways-back
I assume that 30 mA is the steady state current draw once all of the bypass capacitors are fully charged? Not the measured maximum in-rush current?
I've passed the board design off to a professional.
Thanks for your help,