Linux cannot set up ST-Link

[jindo85547]

Hello,

I am trying flash my STM32F746G Discovery board with new code from Linux. I run into this issue after running "dmesg -w": "can't set config #1, error -32". ST-Link is not being detected by either STMCubeIDE and STMCubeProgrammer. Has anyone run into this issue before?

Furthermore, I had code flashed to the Discovery board that had a screen show, but I am met with a black screen when I connect it to power. The LED next to the ST-Link flashes red. I've also tried changing my debugger from ST-Link to SEGGER, but I met with the error "Could not determine GDB version using command: arm-none-eabi-gdb --version," and I am currently looking into this. 

I'm hoping that this is not a board issue but rather a software issue, but at this point it seems like this may be a board issue.

Regardless, has anyone had any issues like this, and can provide any tips on what to do from here?

[Ozone]

Does the ST-Link show up in the  lsusb command output ?

Are the required udev rules in place, to allow access in general ?

> I checked the voltage across the power pins of the ST-Link (Pins 1 and 4 according to this link ... and I'm getting fluctuating values of DC Voltage around 0 volts (ranging from around 0 - 0.1 Volts).

Not sure what you mean.
Like other debug pods, the ST-Link has the optional capability to supply +3.3V to the target.
I would recommend to not try this in this case. You are dealing with a relatively large board with a LCD display here.

Usually, both the ST-Link and the target are supplied from the ST-Link USB connection.

[jindo85547 · Accepted solution]

I had tried 2 wires before making this post. I tried a third out of desparation. The ST-Link is detecting.

To everyone who responded to this post, I am thankful and also sorry that I ended up wasting your time.

I learned a lot from those who responded, thank you again.