• State Not Answered
  • Replies 8 replies
  • Subscribers 62 subscribers
  • Views 7076 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 105676
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can an STLINK be used with nRFgo Studio?

Steven Grunza

The JLINK is costs hundreds of dollars, the STLINK is less thank $20 USD (available on ST's Discovery boards). I would really prefer to use the STLINK. Is there a way to program the SoftDevice and the Application without using JLINK? My target is the nRF51422.

Parents
  • 0

    Is there a list of supported/tested programmers? JLink is expensive ($1000). STLink would be nice if it works as it's proliferate.

    /update Nevermind, I realized there is the edu version of the J-Link. $60 USD is very cheap.

  • 0 in reply to Bigtuna

    2 answers to that, yes and no. OpenOCD offers compatibility with more programmers and thus more target devices. Segger offers compatibility with a large range of ARM devices. So you'd say there that OpenOCD is 'better'. However OpenOCD's breadth of coverage gives it a steeper learning curve and it requires a bit more tuning to get it to go with some chips. Also support relies on 3rd parties adding it and it's not always correct or fast, and for proprietary emulators, non-existant. Only recently is STLINKv2 supported, after being reverse engineered.

    I like JLink because it's supported, natively, by the IDEs I use, it's multi-platform and I know if the boards I'm using is listed and I plug the JLink into it, it's going to work, and if it's not supported, but is ARM, it soon will be and I don't have to mess with it.

    if you 'get good' at OpenOCD you probably find it just as easy.

Reply
  • 0 in reply to Bigtuna

    2 answers to that, yes and no. OpenOCD offers compatibility with more programmers and thus more target devices. Segger offers compatibility with a large range of ARM devices. So you'd say there that OpenOCD is 'better'. However OpenOCD's breadth of coverage gives it a steeper learning curve and it requires a bit more tuning to get it to go with some chips. Also support relies on 3rd parties adding it and it's not always correct or fast, and for proprietary emulators, non-existant. Only recently is STLINKv2 supported, after being reverse engineered.

    I like JLink because it's supported, natively, by the IDEs I use, it's multi-platform and I know if the boards I'm using is listed and I plug the JLink into it, it's going to work, and if it's not supported, but is ARM, it soon will be and I don't have to mess with it.

    if you 'get good' at OpenOCD you probably find it just as easy.

Children
No Data
Related