All was fine, until I flashed custom firmware. Didn't like it, tried to go back to stock.
Basically, on Windows 10, when I connect USB to PC and try to enter DFU mod, it throws me right back out of the DFU mode. If I disconnect USB cable, TinySA Ultra enters DFU mode, screen stays black. Also, if I connect to Linux, it enters DFU mode (but dfu-util does not work).?
?
How to approach this situation? Let's focus on windows, what can I do so that TinySA Ultra stays in DFU when I connect USB cable? For in case I'll include the output from Linux.
?
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
Bus 001 Device 003: ID 0408:5222 Quanta Computer, Inc. HP Webcam
Bus 001 Device 008: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
?
?
dfu-util 0.11-dev
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/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations
Clearing status
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash ?"
Downloading element to address = 0x08000000, size = 181632
Erase ? ? ? [ ? ? ? ? ? ? ? ? ? ? ? ? ] ? 0% ? ? ? ? ? ?0 bytesdfu-util: ERASE_PAGE not correctly executed
