Help! Flashing for a blank BluePill but stop at STEP2 "Waiting for device" forever

[AiGeekNet]

Before try to make a BlueSCSI, I want to flash a blank BluePill first.

Select Mode2 and get STEP1 successful, but stop at STEP2 forever.

I have done everythings as notes but no luck, and the LED keep flashing ( that means the part1 boot loader working right?)

I try to plug a TF card or not, but no help.

  ____  _             _____  _____  _____ _____
 |  _ \| |           / ____|/ ____|/ ____|_   _|
 | |_) | |_   _  ___| (___ | |    | (___   | |
 |  _ <| | | | |/ _ \\___ \| |     \___ \  | |
 | |_) | | |_| |  __/____) | |____ ____) |_| |_
 |____/|_|\__,_|\___|_____/ \_____|_____/|_____|

     Welcome to the BlueSCSI Firmware BBS!
          Flasher Version 2022-04-11

Choose an option:

[1] Upgrade via USB.
 - You must have BlueSCSI v1.1-20220404-USB or greater already flashed.
[2] Prepare a blank BluePill or older BlueSCSI firmware for USB support.
 - You must have a STLink v2.

[H] Help
[P] Page Sysop
[Q] Hang Up

Choice?2
Flashing the generic_boot20_pc13.bin
* Move BOOT0 to 1 (Jumper furthest from the RESET button on the BluePill)
* Connect the ST-LinkV2 to your BlueSCSI and connect it to your computer.
Press anykey to continue. . .
Starting flash...
NOTE: Some BulePills can take up to 2 minutes to flash.
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-17:32)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
0
Info : auto-selecting first available session transport "hla_swd". To override u
se 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results mi
ght differ compared to plain JTAG/SWD
Info : DEPRECATED target event trace-config; use TPIU events {pre,post}-{enable,
disable}
Warn : Transport "hla_swd" was already selected
hla_swd
Info : clock speed 1000 kHz
Info : STLINK V2J27S6 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.120308
Info : [stm32f1x.cpu] Cortex-M3 r1p1 processor detected
Info : [stm32f1x.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32f1x.cpu on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1ffff020 msp: 0x200001fc
** Programming Started **
Info : device id = 0x20036410
Info : flash size = 64kbytes
** Programming Finished **
** Verify Started **
** Verified OK **
** Resetting Target **
shutdown command invoked
Check output if successful (Windows...)
* Move the BOOT0 Jumper back to position 0
* Disconnect the BlueSCSI from the STLink
Ready to flash BlueSCSI firmware.
Press anykey to continue. . .
Flashing BlueSCSI-v1.1-20220917-STM32F1-USB.bin
* Move BOOT1 to 1 (Jumper nearest the RESET button on the BluePill)
* Connect via USB to the BluePill
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Waiting for device, exit with ctrl-C

---

Then I try to flash BlueSCSI-v1.1-20220917-STM32F1.bin directly by ST-LINK V2, it's work. I get LED flashing 5 times without TF card and right log with card.

---

Now that the firmware has been successfully flashed, I tried to use Mode2 for the USB upgrade, but still no luck, just stop the same place.

Anythings wrong?

[erichelgeson]

I would try a different USB cable - some are power only. Also see the help in the README of the Updater repo. If you are on windows you'll need to install the drivers as mentioned in the readme as well.

[AiGeekNet]

Awesome!

Unexpectedly, the Micro USB charging cable from my mom's old Android phone was the matter. IT was really just the charging cable (albeit with 5 contacts).

Changed a Micro USB data cable and additionally installed the maple-usb-drivers-win.7z driver in the BlueSCSI-Updater Repo.

Restart Mode2 flashing, the STEP2 flashing process continue finally... until the Download progress reaches 97% and an error occurs:

Error sending completion packet (LIBUSB_ERROR_IO)

Waiting for device, exit with ctrl-C
Cannot open DFU device 1eaf:0003 found on devnum 1 (LIBUSB_ERROR_NOT_SUPPORTED)
Opening DFU capable USB device...
Device ID 1eaf:0003
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #2 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download        [======================== ]  97%        48128 bytes
Error sending completion packet (LIBUSB_ERROR_IO)
Check output if successful (Windows...)
* Move BOOT1 back to 0
* Disconnect USB
Happy scuzzing!

The BlueSCSI at this level already has the ability to:

• Can be re-flashed with Flash Mode1 (but still gives an error at 97%)
• If the TF Card is not inserted, the "five flashes" will continue
• Insert the TF Card, LOG.TXT will be created, showing that the image file has been recognized, and the firmware version shows the end of -USB

Does it OK?

[erichelgeson]

Please fully review the readme, it addresses your questions https://github.com/erichelgeson/BlueSCSI-Updater#q-getting-error-sending-completion-packet-libusb_error_io

[AiGeekNet]

Great!

I just restall the maple-usb driver as admin user and get rid of "Getting Cannot open DFU device 1eaf:0003 found on devnum 9 (LIBUSB_ERROR_NOT_SUPPORTED)". Happy to know the "Getting Error sending completion packet (LIBUSB_ERROR_IO)" just OK.

So the happy scuzzing processing... Thanks a lot!

Flashing BlueSCSI-v1.1-20220917-STM32F1-USB.bin
* Move BOOT1 to 1 (Jumper nearest the RESET button on the BluePill)
* Connect via USB to the BluePill
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Waiting for device, exit with ctrl-C
Opening DFU capable USB device...
Device ID 1eaf:0003
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #2 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download        [======================== ]  97%        48128 bytesError sending
 completion packet (LIBUSB_ERROR_IO)
Check output if successful (Windows...)
* Move BOOT1 back to 0
* Disconnect USB
Happy scuzzing!