- ATOLLIC TRUESTUDIO CONNECT ST LINK SERIAL
- ATOLLIC TRUESTUDIO CONNECT ST LINK DRIVERS
- ATOLLIC TRUESTUDIO CONNECT ST LINK DRIVER
ATOLLIC TRUESTUDIO CONNECT ST LINK DRIVER
ATOLLIC TRUESTUDIO CONNECT ST LINK DRIVERS
Try the latest firmware and drivers from ST’s website, instead. On some ST-Link versions, multiple drivers are loaded, from the debug unit itself, when the ST-Link is first connected to a PC.
ATOLLIC TRUESTUDIO CONNECT ST LINK SERIAL
There is a low level issue if, this entry is missing, there is a "caution" symbol on the USB icon, or there is an entry under the Universal Serial Bus controllers section labeled USB Composite device with a "caution" icon. Windows device manager should show under the Universal Serial Bus devices section a STM32 STLINK. If unsuccessful, this test shows that either the board, the jumper configuration, the windows drivers, the board firmware or the USB interface has an issue. If you are using a recent version of MDK.ĭownload, install, and open the ST-Link Utility. What’s the reason for this error and how do you troubleshoot it? ANSWER Using a ST-Link with MDK, when starting a debug session or a flash downloading, µVision issues the following error: Information in this knowledgebase article applies to: I am also powering my board separately from the programming interface, so would it matter if I connect the Nucleo to the board before I power the board? Could I damage it by doing that? Are there debug settings or configurations in Atollic TrueStudio that could prevent me from being able to reprogram a chip? Is it possible to recover the chip? To my knowledge I followed the same procedure for programming the board on all my attempts, so I am confused as to why it suddenly fails now. I get this error in Atollic TrueStudio and when I try to connect to the board from ST-LINK Utility.
![atollic truestudio connect st-link atollic truestudio connect st-link](https://visserslatijn.files.wordpress.com/2019/01/usb_nucleo.jpg)
I have double-checked that my wiring is the same as on the previous successful times. I was testing some minor firmware changes and re-programming the board three or four times successfully before I suddenly just got the error "USB communication error". I have set all the jumpers and connected my PCB to the Nucleo. I am using Atollic TrueStudio on Windows 10 and programming it through the ST-LINK on the Nucleo board (header CN6). I have a custom PCB (based heavily on the Nucleo board) using the STM32F767II.