Pricing of the various IDE/tools for STM32

[relaxe]

Posted on September 15, 2009 at 20:02

Pricing of the various IDE/tools for STM32

[jschatz]

Posted on May 17, 2011 at 13:01

What about Code Blocks (IDE) running with GNUARM?

This appears to be a little strange, because of the Cygwin interface, but we have multiple platforms, Linux and WindowsXP that we use for other processors.

Anybody know of a decent debugger or simulator? I noticed that there is a JLINK-style interface on the STM3210B primer that has an ARM7-USB JTAG interface which might work for production.

I would welcome comments---

[guyvo67]

Posted on May 17, 2011 at 13:01

hi all,

Does anybody know if the R-LINK (32k limited version) from Raisonance IDE is supported in other environments like eclipse (OCD) or keil ?

-G

[st3]

Posted on May 17, 2011 at 13:01

Quote:

Does anybody know if the R-LINK (32k limited version) from Raisonance IDE is supported in other environments

Almost certainly not.

All of these debug adaptors - RLink, uLink, JLink, et al - tend to be proprietary and closed.

[raptorhal]

Posted on May 17, 2011 at 13:01

Here is an inexpensive development configuration that is currently working well for me:

Anglia IDEaliST V1.61 plus Tools V1.62

FTDI MProg3.5 utility (to set dongle device ID/Code)

Olimex ARM USB OCD load/debug dongle

My design PCB with STM32F105RCT6 processor

My cost is a reasonable $69 for the dongle. I also have a PCB cost, but that is independent of the tool selection.

IDEaliST is not code limited. It uses the Insight user interface for the OpenOCD debugger. The only significant disadvantages to IDEaliST is that it does not have the V3 Firmware Library yet, and support is minimal if you are not an Anglia customer.

Cheers, Hal

[slawcus]

Posted on May 17, 2011 at 13:01

J-link can be used with almost every debug sw: gdb, IAR, keil, Rowley,...

Except for RVDS v3.1 and newer.

[st3]

Posted on May 17, 2011 at 13:01

Quote:

J-link can be used with almost every debug sw

Ah, you may well be right there.

The RLink is definitely proprietary to Raisonance, and the uLink is definitely proprietary to Keil but, now that you come to mention it, I think the ''IAR'' JLink is actually just a ''badged'' product from a 3rd party - and they provide support for the other, non-IAR tools...

[martindavey9]

Posted on May 17, 2011 at 13:01

I work for the same company which produces the Idealist toolchain. www.anglia.com/software.asp

We are developing a microcontroller plugin for codeblocks which supports OpenOCD. It allows you to select a micro, and automatically generates the OpenOCD script, and launch/control OpenOCD automatically. It is currently being tested, and need to add a few more features like option bytes etc...

My personal opinion is that the simulation features present in Keil and IAR can be very valuable.

Also OpenOCD at the moment is yet to support SWD.

I think it's sensible to say in our experience, unless you take the time understand GCC and OpenOCD enough, you can get in a bit of a mess.

[slawcus]

Posted on May 17, 2011 at 13:01

Quote:

definitely proprietary to Keil but, now that you come to mention it, I think the ''IAR'' JLink is actually just a ''badged'' product from a 3rd party - and they provide support for the other, non-IAR tools...

Yes, it's badged. JLink is a Segger product. They make special versions for IAR and Atmel (SAM-ICE).

[guyvo67]

Posted on May 17, 2011 at 13:02

hi,

I got some pricing from Raisonance to upgrade the r-link to unlimited debugging. It 's priced at 700€ which is a little high in my opinion because the Ride 7 IDE must get a more professional touch.

Therefore I was wondering if I could use the Amontec JTAGkey2 ( price 115€ ) for STM32 devices using eclipse and openocd ? I didn't see the cortex in the supported device list.( only ARM7/9/STR ) But I guess this is only a config file as long the JTAG pins are well connected.

Anyone experience with using amontec and STM32 ?

thanks

Guy

[st3]

Posted on May 17, 2011 at 13:02

Quote:

it's sensible to say in our experience, unless you take the time understand GCC and OpenOCD enough, you can get in a bit of a mess.

I think it's fair to say that the same is true of any software development tools!

[rant]

Too many people look at the gadgets available today, see that they are small, cheap, and easy to use - and jump to the false conclusion that they must, therefore, be easy to make!

[/rant]