cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to read which product part number is connected via DFU bootloader?

BPric.557
Associate II

I'm looking for a way to detect which device part number (EX: STM32F765...) is connected via the USB DFU bootloader before programming the device (as a sanity check to make sure the file is appropriate/compatible). I can see the VID/PID/REV and Option Bytes, but that is not specific enough.

Is there any way to do this? Or are there other recommended ways to check device compatibility with a target .DFU file?

For context, I'm envisioning a situation where I have 2 very different STM32 devices that support the USB DFU bootloader but require different DFU files.

3 REPLIES 3
Uwe Bonnes
Principal III

dfu-util -l lists the exported memory regions like for a F303:

Found DFU: [0483:df11] ver=2200, devnum=29, cfg=1, intf=0, path="2-2.1", alt=1, name="@Option Bytes /0x1FFFF800/01*016 e", serial="FFFFFFFEFFFF"

Found DFU: [0483:df11] ver=2200, devnum=29, cfg=1, intf=0, path="2-2.1", alt=0, name="@Internal Flash /0x08000000/064*0002Kg", serial="FFFFFFFEFFFF"

This gives at least some hints on the attached device

Thanks! Do you know what that "devnum" identifier represents?

Uwe Bonnes
Principal III

The devnum is something from the Linux USB handling.