In a later step we plan to flash several chips in parallel on one Windows host system. For this it is necessary to be able to assign connected boards clearly.

[_MHeuc.1]

External memory, connected to a STM32MP1, is written with the STM32CubeProgrammer via USB. Here the chip to be written is written with "usb1" (STM32_Programmer.sh -c port=usb1 -d some.tsv").

Here we could notice the following behavior: If more than one STM32MP1 is connected to the host system via USB, another label (usb2) is assigned. If a higher serial number is connected later, it will be assigned to usb1, and the already connected device will be assigned the new label usb2. The connected devices are displayed in the device manager as DFU Devices. There is no COM port assignment.

This raises the question of how several devices can be connected to a host at the same time and assigned uniquely to enable several devices to be flashed in parallel.

What is the best practice to guarantee consistent addressing of the boards.

[Olivier GALLIEN · Accepted solution]

Hi @_MHeuc.1​ ,

Sticking to STM32CubeProgrammer I think that answer is in um2237-stm32cubeprogrammer-software-description-stmicroelectronics.pdf page 83

Note: For the parallel programming of more than one STM32 device using multiple instances of 
STM32CubeProgrammer, it is mandatory to add the serial number of each device in the 
suitable instance, as shown in the following example:
 “ –c port=swd/usb sn=SN1�? (instance 1 of STM32CubeProgrammer)
 “ –c port=swd/usb sn=SN2�? (instance 2 of STM32CubeProgrammer)
 “ –c port=swd/usb sn=SN3�? (instance 3 of STM32CubeProgrammer)

But you should know that STM32CubeProg is not a mass production tool.

ST recommend to use the ST partner solution from Elprotonics : the gangflasher-st with

https://www.elprotronic.com/pages/gangflasher-st

Olivier