Posted on May 17, 2011 at 13:28It's been a while since I played with it, but Segger's J-Flash program for the J-Link should support reading and writing of the device. It would probably be usable by production staff.
The old Realview AXD debugger could download the memory from the debugger. In Keil uVision you can create a HEX file from the debug command window (lower left - Output Window) using a ULink, the following with pull 128KB slowly (will appear to hang for 20-30 seconds) from the STM32 flash.
save c:\foo.hex 0x8000000,0x8020000
Keil generates a Intel Hex file as part of the compile/link process, you should be able to use that as a master. Pulling binary data from a working/golden device wouldn't provide the level of source code control I'd be looking for.
The user code running within the STM32 could output data out of memory, could checksum the flashed image, and also be set to update it self from an external source. In designing a board for manufacture and test, the BOOT0/1 and UART1 TX/RX, RESET and JTAG signals should reach test points.
Even without control of the BOOT0/1 pins code running within the FLASH or RAM of the STM32 can execute the System Boot Loader in ''ROM''. If UART1 is not available you could create an equivalent loader/monitor using a UART of your choice.
-Clive
