STM32 ST-Link How to

Follow

saiRam

• June 15, 2011 12:24

I am trying to add a target for STM32 ST-Link debugger.. There is no information on this other than some scribble by Paul that it is supported and we can add it as a new target. I have not been successful in doing this. Any pointers are appreciated. 

 

My Crossworks version 2.0.1

 

Thx

0

• 

  Michael Johnson

  • June 15, 2011 13:37

  ST-Link is supported (Windows only) from version 2.0.8

  0

  Comment actions Permalink
• 

  saiRam

  • June 16, 2011 02:45

  Indeed when I upgraded the Crossworks to the latest one things started to move..  Thanks..

  0

  Comment actions Permalink
• 

  Sobellinni

  • August 27, 2011 21:50

  Just downloaded 2.1 stlink does not work and have no idea how to make it work. I went to target, New Target Interface, Generic, set Stlink.dll, imported STLinkUSBDriver.dll to the bin directory and get USB communication failure

   

  0

  Comment actions Permalink
• 

  Michael Johnson

  • August 30, 2011 13:34

  Don't copy the stlinkusbdriver.dll to the bin directory just refer to it using the path to the installation directory.

  0

  Comment actions Permalink
• 

  Peter Harrison

  • October 24, 2011 19:01

  Is there any chance that support for the ST-LINK will be extended to the Mac?

  0

  Comment actions Permalink
• 

  Michael Johnson

  • October 24, 2011 20:17

  The st-link/v2 is supported on windows/linux/macos in version 2.1.2.

  We don't plan to support the st-link other than via the stlinkusbdriver.dll which is only available on windows.

  0

  Comment actions Permalink
• 

  Peter Harrison

  • October 24, 2011 22:21

  Ah - I had not registered the fact that there was a V2 of st-link.

  When do you expect to release V2.1.2?

  0

  Comment actions Permalink
• 

  Michael Johnson

  • October 25, 2011 08:15

  Hopefully this week - (that's what I said last week :-<)

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Peter Harrison

  • October 25, 2011 08:24

  Excellent! My STM32F4 discovery arrived yesterday. Can't wait to get going.

  0

  Comment actions Permalink
• 

  Michael Johnson

  • October 25, 2011 08:35

  There's another message where I specified where to get hold of the nightly build if you want to get started.

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Peter Harrison

  • October 26, 2011 20:42

  Well, that all went rather well. Thank you.

  I have the STM32F4 discovery connected and working on Mac and Windows. 

   

   

  0

  Comment actions Permalink
• 

  Ian Garcia

  • November 01, 2011 23:24

  I also want the support for V2. How do I get the nightly build? :/

  0

  Comment actions Permalink
• 

  Michael Johnson

  • November 02, 2011 07:30

  It's here

  http://www.rowleydownload.co.uk/snapshots/arm_crossworks_crossworks_v2_win_x86_setup.exe

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Ian Garcia

  • November 04, 2011 16:09

  Thanks!

  0

  Comment actions Permalink
• 

  Andy Kobyljanec

  • December 02, 2011 05:36

  I pointed the STLink to the correct dll file, but when I try to connect I get a DEV_CONNECT_ERR. The ST Link Utility works fine though. Is there anything else that could possibly be wrong? Thanks

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 02, 2011 07:16

  Did you set the target interface type to be SWD rather than JTAG.

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Andy Kobyljanec

  • December 02, 2011 12:27

  Yes it was in SWD mode, and this is on the Crossworks version 2.1.2. Just trying to get some code on the STM32F4 discovery board, last night I was able to compile successfully thanks to your helpful advice!

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 15, 2011 06:22

  I'm having problems getting my Crossworks (on Ubuntu Linux 10.04 LTS to support the STM32F407 discovery board... I think I followed the posts above, I found and installed the nightly build Release 2.1.2.2011120900.13079 for linux, but I still see and error whenever I try to attache to the STlinkV2 target "Generic .dll is not open", I alsos always see errors int he output window one Crossworks startup saying "Cannot access usr/share/crossworks_for_arm_2.1/bin/STLink.dll" and the same for PandE.dll.

  Is there a quick fix or am I doing something wrong ?

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 15, 2011 12:42

  Try right clicking in the targets window and select "Restore Defaults".

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 16, 2011 07:50

  Sorry, i tried that and it made no difference, even after restarting Crossworks, and following a system reboot.

   

  I've attached a screenshot of the CW window with the errors showing (the STM32F4 Discovery bopard is attached and functioning during these test, but is still invisible to CW.

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 16, 2011 10:36

  You'll need to wait for a new nightly build - try again tomorrow.

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 17, 2011 08:58

  OK so i downloaded Release 2.1.2.2011121501.13218

  Once updated I had to reinstall my licence activation code (thats a first for any upgrade I've applied to this point)

  But I have the exact same errors with no changes to the symptoms or errors displayed...

  The files in question simply don't exist (as .dll's in any case, which would be very out of place on a linux machine), the relevant files DO exist as .so files on that path  (much more in line with linux), is there a problem with my install that for some reason is trying to load windows DLL's rather than linux shared libraries ?

  Peter

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 17, 2011 09:01

  In fact the license key needs re-installing on every invocation of the CrossStudio now... thats a little annoying ;-), 

  0

  Comment actions Permalink
• 

  Igor Pokorny

  • December 19, 2011 07:58

  Hello Peter,

  I observed same problems after downloading last release of the Crossworks. Reconnecting the USB cable of the  target (STM32F4DISCOVERY)  solved all problems. I am using linux (Ubuntu 10.4 LTS) too.

  Regards Igor.  

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 20, 2011 13:28

  If you right click in the targets window and select "Restore Default Targets" then the .so files will be accessed rather than the .dll files.

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 21, 2011 05:38

  Nope, still having problems.

  Sequence I see is .

  Disconnect STM32F4 board.

  On loading CW,i see the "cannot load .DLL errors" in the output window... always.

  right click in the targets window and restore defaults (I get the Ubuntu "busy spinning mouse pointer" for a few seconds outside of the CW window)

  Connect STMF4 Discovery board,

  try to connect to the target in the targets window

  get an "Unrecoverable failure, Crossstudio must close error" dialogue

  I doo see a "st-link log" entry in the output window but I can;t look at is as the only thing crossstudio will do is close competely.

   

  I'm building a new machine and I'll transfer the license over to it an see if a fresh clean install fixes the issues I'm seeing, this 10.04.LTYS release hae been faithful but its getting very long in the tooth perhaps something is running interference here.

   

  Peter

  IPerhaps I have bigger probelms, but this is ticking me off 

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 21, 2011 08:00

  Could you try the latest build

  http://www.rowleydownload.co.uk/snapshots/arm_crossworks_crossworks_v2_linux_x86.tar.gz

  Thanks

  Michael

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 22, 2011 08:20

  Michael, thanks for persisting with this..

  Definite progress but still not success.. I installed the latest nightly  2.1.2.2011122100.13292

  I no longer see the "cannot load .DLL errors", but each time I attempt to connect to the STlinkV2 target I get an immediate  "Unrecoverable failure, Crossstudio must close error" dialogue and crossstudio aborts. In the output window it looks like there might be a st-link log file written somewhere but I can;t get to it before crossstudio aborts and I can't find it, is there likely to be anything interesting in that file ?

  I did try restoring target defaults with no difference in behaviour.

  Also I still have to re-activate the license every time I load Crossstudio.

  
  

  0

  Comment actions Permalink
• 

  Peter Alexander Wilson

  • December 22, 2011 08:21

  Actually the error is " internal error detected, Crosstudio must close"

  0

  Comment actions Permalink
• 

  Michael Johnson

  • December 22, 2011 09:25

  What happens if you try to connect to the ARM Simulator target?

  0

  Comment actions Permalink

Please sign in to leave a comment.