2 Jun
2025
2 Jun
'25
3:19 a.m.
I am running DFU-util -d with my vid and pid for my device as parameters.
The response is that the device is in runtime mode.
When I use the update utility supplied by the chip manufacturer, the device programs and
restarts (as per code in the bootloader)
I cannot change the USB enumeration details at this point since too many devices have been
deployed with existing bootloader code.
How can I “fake out” DFU-util to accept a Vid/pid match and run the update?
Please advise
Bruce Doan
4 Jun
4 Jun
12:10 p.m.
On Mon, Jun 2, 2025 at 3:19 AM Bruce Doan wrote:
I am running DFU-util -d with my vid and pid for my device as parameters.
The response is that the device is in runtime mode.
I am not sure I understand, can you please post the full command line
and output?
When I use the update utility supplied by the chip
manufacturer, the device programs and restarts (as per code in the bootloader)
I cannot change the USB enumeration details at this point since too many devices have
been deployed with existing bootloader code.
How can I “fake out” DFU-util to accept a Vid/pid match and run the update?
Is is this a device with DFU-mode and runtime-mode or is it always in
DFU-mode and reports run-time mode?
I am unsure what the connection with VID/PID is here. Can you try
without -d VID:PID? The -d option only serves to filter out any other
DFU devices and make sure that the right device will be used. It is
possible to filter on DFU mode descriptors and/or run-time
descriptors.
Tormod
27
days inactive
29
days old
1 comments
2 participants
participants (2)
-
Bruce Doan -
Tormod Volden