cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot connect PC to STM32MP157x-EV1 board through ST-LINK/V2-1

mbovero
Associate II

I have carefully followed the getting started guide for the STM32MP157x-EV1 board. All the steps I took were successful until I reached the "Execute basic commands" section where I am instructed to run the following command:

ls /dev/ttyACM*

The expected output is

/dev/ttyACM0

but when I tried running it, no such file was found. With the evaluation board recently connected to my PC through the board's ST-LINK/V2-1 port, the "sudo dmesg" command reveals the following issues:

 

 

 

 

[ 2144.431929] usb 5-1: new full-speed USB device number 9 using xhci_hcd
[ 2144.563977] usb 5-1: device descriptor read/64, error -71
[ 2144.803980] usb 5-1: device descriptor read/64, error -71
[ 2145.039934] usb 5-1: new full-speed USB device number 10 using xhci_hcd
[ 2145.171984] usb 5-1: device descriptor read/64, error -71
[ 2145.411986] usb 5-1: device descriptor read/64, error -71
[ 2145.524053] usb usb5-port1: attempt power cycle
[ 2145.935943] usb 5-1: new full-speed USB device number 11 using xhci_hcd
[ 2145.936037] usb 5-1: Device not responding to setup address.
[ 2146.144071] usb 5-1: Device not responding to setup address.
[ 2146.351947] usb 5-1: device not accepting address 11, error -71
[ 2146.479952] usb 5-1: new full-speed USB device number 12 using xhci_hcd
[ 2146.480048] usb 5-1: Device not responding to setup address.
[ 2146.688038] usb 5-1: Device not responding to setup address.
[ 2146.895953] usb 5-1: device not accepting address 12, error -71
[ 2146.896088] usb usb5-port1: unable to enumerate USB device

 

 

 

 

 

I spent a couple hours digging through numerous posts/discussion/threads, trying many different solutions, but none seemed to have worked.
My fruitless efforts include...

  • Using various other micro USB Type-B to USB Type-A cables
  • Using different USB ports on my PC
  • Restarting & power cycling both the PC and the board
  • Disabling usbcore autosuspend (set to -1)
  • Unloading and reloading the USB kernel module
  • Re-flashing the board

Some of my sources include:
https://ubuntuforums.org/archive/index.php/t-797789.html

https://www.linuxquestions.org/questions/linux-hardware-18/usb-5-1-device-descriptor-read-64-error-71-a-4175640937/

https://unix.stackexchange.com/questions/91027/how-to-disable-usb-autosuspend-on-kernel-3-7-10-or-above

 

I am unsure of what further steps I might take to diagnose this problem. Let me know what information I might provide to clarify this issue. Any help is appreciated, thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

Hi,

unfortunately, you symptom seems to show that the embedded STLINK is somewhat faulty (corrupted FW or HW issue).

I fear board should be replaced.

 

Regards,

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

5 REPLIES 5
PatrickF
ST Employee

Hi @mbovero 

Are you using a Linux virtual machine or native Linux PC ?

Did you try on another PC (e.g. Windows) ?

Please check the JP1 is not populated (control STLINK reset).

Could you try upgrading STLINK (https://www.st.com/en/development-tools/stsw-link007.html) ?

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Hey @PatrickF,
I was unable to get the STM32CubeProgrammer functioning on my VM, so I switched to a desktop PC with Ubuntu 22.04 (which is where I faced my current problems).
I tried connecting my Windows laptop to the evaluation board through the ST-Link port, but I just get a notification indicating that the "USB device was not recognized."
I have made sure that JP1 is not populated.
I've attempted to upgrade STLINK using both computers, but it doesn't seem possible without the device being recognizable. Is there any other way to do this?

Many thanks.

Obviously, you should have the STLINK driver installed prior to anything else https://www.st.com/en/development-tools/stsw-link009.html

 

Could you try using MB1263C alone (removed from motherboard) ?

- plugin 5V on CN1 without any USB should make at least LD1 green fixed (power) and LD6 green slow blink (not connected)

- with or without 5V on CN1, plugging USB CN4 (STLink) to PC would make LD6 green fixed (correctly connected)

 

Are you able to connect with CubeProgrammer using the STM32MP15 USB OTG on motherboard (as STLINK is only for debug and serial console and does not work with CubeProgrammer) ?

https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Unpack_the_STM32MP157x-EV1_board

 

 

If nothing work in the end, the board might have been damaged.

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Thanks for the quick response Patrick,

I double-checked that the correct drivers were installed, and the device still appears to be unrecognizable upon connection.

I tried using the daughter board separate from the motherboard:
- Upon providing 5V through CN1 without any USB connections, the LD1 appeared green fixed, but LD6 exhibits a very dim red fixed
- With and without 5V on CN1, connecting USB CN4 to each computer resulted in USB device recognition errors and the same dim red fixed LD6

The only connection I've been able to establish through CubeProgrammer (using the STM32MP15 USB OTG on the motherboard) was during the process of populating the SD card and booting the image:
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Populate_the_target_and_boot_the_image


I assume the fact that my LD6 is never lighting up green indicates some predominant issue. Is there anything else I might do to troubleshoot this problem? Or is it simply time to look into getting a new board?

Hi,

unfortunately, you symptom seems to show that the embedded STLINK is somewhat faulty (corrupted FW or HW issue).

I fear board should be replaced.

 

Regards,

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.