I just did another test with a Nucleo64-F103 which also shows the same issue. After cube programmer reports device ID 0x00000 other programs show me problem with the USB communication to ST-Link. I have to unplug the ST-Link to get it back working.
I have the same issue. STM Cube Programmer ready always device ID 0x0000 from my BluePill Boards as well as Nucleo64-F103 Boards via SWD but other Programs work fine.
You need to start the STM32 Cube Programmer with Oracle Java 8. See https://community.st.com/s/question/0D50X00009q3X4jSAE/stm32cubeprogrammer-for-linux?t=1593874663726 where the same topic is discussed.
I have no Android device with USB host, but I use Linux computers daily. I tried the CDC code from Cube HAL a few days ago and it worked out of the box. So you may retry with the current Cube HAL release.I also developed an independent driver that yo...
