-
Notifications
You must be signed in to change notification settings - Fork 80
Description
Trying to flash SuperLongBoard_B5.0.5b-as.hex to my brand new SLB. Trying to do it through gSender just hangs. At the point the progress bar pops up nothing else happens, it just hangs. Pressing the X button in the upper right corner exists that window and things continue normally. Sometimes when selecting the USB port it shows the correct port AND something called SLB_DFU. No mater which one you pick the attempt to flash fails.
I also tried using STM32CubeProgrammer. It shows the message No DFU detected on the port select widget. Pressing the retry button to the right of that message has no effect. It shows PID 0xDF11 and VID 0x0483. lsusb shows
Bus 001 Device 019: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Which would indicated that the SLB is properly booted into the correct mode. As instructed I used a piece of metal (I used a large nail, those worked 40 years ago and they still work today) to short out the jumper while booting. After a normal boot lsusb shows
Bus 001 Device 020: ID 0483:5740 STMicroelectronics Virtual COM Port
Notice that the VID is the same but the PID is not. I'm guessing this is how STM32CubeProgrammer detects that the device is in DFU mode.
Since I am using Ubuntu 25.10 I went through the process of adding the recommended udev rule. It tells you to add a rule for 0483:5740 but not for 0483:DF11. Should both rules be added? I am also a member of the dialout group so the ubev rule should not be needed. Please let me know if I am wrong about that.