Last week my debug/development environment was working. My laptop is connected to a docking station. I have a long USB-A to USB-A extension cable (15 feet) to an unpowered USB hub with 5 ports. My 'scope, power supply, DVM, and STLINK-V3MINIE are connected to the hub. My board uses an STM32L031 device with SWD debugging.
After a week of reviewing analog circuit designs I am ready to continue development on my board but cannot get the STLINK to connect anymore.
Errors from the programmer with everything connected as it was before:
15:23:50 : STM32CubeProgrammer API v2.18.0 | Windows-64Bits
15:23:50 : ST-LINK error (DEV_USB_COMM_ERR)
15:24:03 : UR connection mode is defined with the HWrst reset mode
15:24:03 : ST-LINK error (DEV_USB_COMM_ERR)
Errors from the programmer with all USB cables except STLINK removed from the hub:
15:24:03 : Error: Problem occured while trying to connect
15:24:38 : UR connection mode is defined with the HWrst reset mode
15:24:38 : ST-LINK error (DEV_USB_COMM_ERR)
15:24:38 : Error: Problem occured while trying to connect
Connection made when hub is removed and the STLINK is connected to the extender cable:
15:24:54 : UR connection mode is defined with the HWrst reset mode
15:24:54 : Warning: Device changed, refreshing...
15:24:54 : UR connection mode is defined with the HWrst reset mode
15:24:55 : ST-LINK SN : 0029004B3033511735393935
15:24:55 : ST-LINK FW : V3J15M6
15:24:55 : Board : STLINK-V3MINIE
15:24:55 : Voltage : 2.50V
15:24:55 : SWD freq : 8000 KHz
15:24:55 : Connect mode: Under Reset
15:24:55 : Reset mode : Hardware reset
15:24:55 : Device ID : 0x425
15:24:55 : Revision ID : Rev X
Between the last time this setup worked and today, there was a firmware update pushed out to the docking station. I, of course, don't know what the firmware update did to either the laptop and/or the docking station -- I just know a "critical update" was installed.
I hope to get a powered USB hub tomorrow but I doubt that will solve the problem since the setup worked last week with the un-powered USB hub. Note: I did change from the original un-powered USB hub to a different un-powered USB hub just in case the original HUB finally died (it's several years old and gets 'new' and 'under-development' boards plugged into it frequently.
Any suggestions for what to try next if the powered hub doesn't resolve the situation? I need at least the 'scope on the USB bus so I can document the board bring-up test results.
