Skip to main content
Visitor II
January 12, 2021
Question

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

  • January 12, 2021
  • 2 replies
  • 1265 views

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.

    This topic has been closed for replies.

    2 replies

    Graduate II
    January 21, 2021

    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

    BPric.557Author
    Visitor II
    January 21, 2021

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

    Graduate II
    January 21, 2021

    The devnum is something from the Linux USB handling.