AnsweredAssumed Answered

ST-LINK is broken by VCP via USB activity

Question asked by yakovlev.oleg on Jan 23, 2014
Latest reply on Jan 23, 2014 by yakovlev.oleg
Hi All,
I've ported the VCP to F3DISCOVERY ([DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Discovery/STM32F3DISCOVERY%20USB%20CDC%20%28Virtual%20COM%20port%29%20Example&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800084C20D8867EAD444A5987D47BE638E0F&TopicsView=https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/AllItems.aspx&currentviews=1013]taken from here) board but the one problem has been raised - application has broken SWD. As fact reprogramming (from Keil) and debug is impossible. I'm getting error "Cannot access target. Shutdown debug session" when I'm trying start the application in debug mode. And I'm getting "Internal communication error" for any other attempts. After it any other deals with board via ST-LINK are impossible due to following error: Target DLL has been cancelled. Debugger aborted! The ST-STUDIO doesn't work also.

But the application is working properly and board can be reprogrammed directly via ST-LINK utility.

How I can fix it? I have suspicion that application is using the wrong USB but I don't know how it can be checked. I've went the extra mile and can't sort out with these. :(

I'm so sorry for new topic, but it may be common problem.

Thanks in advance

Outcomes