Posted on July 12, 2018 at 18:58I'm not paid to perform others job function. I'm quite capable of writing windows applications and device drivers, and using ethernet interfaces to pull configuration data, and stream firmware images to devices under test.
If you want to go the JTAG/SWD route, Segger has hardware and software, but personally I find that expensive to scale to large numbers of test stations. ST has ST-LINK and assorted command line and DLL, sure there is a workable solution there, but that's all pretty pedestrian compared to other JTAG and boundary scan solutions available to me.
The STM32 parts have well documented system loaders, which can be readily automated and scaled using other simple micro-controller boards that can either hold the entire payload, or sufficiently boot strap a system so it can pull from a more native interface, be that Ethernet, or SD/MMC cards. The type of interfaces the end-user would expect to be tested.
Even if you have to write scripts or spawn multiple applications there's never an expectation that a line operator would need to edit a file, they'd get PASS/FAIL indications, and status about serial numbers and calibration data, and then that would get pushed into a test database, and label printers for the product.
At the end of the day I'm here to provide directions, like the man on the street who knows the town, but I'm not looking to drive you to your destination.
