Tool chains For the STM32F4

Status
Not open for further replies.

be80be

Well-Known Member
I was wondering whats the best set for the STM32F4


Tool chains Iar, Keil, Atollic, Altium.
 
Last edited:
If you're looking for compiler/linker/debuggers.
IAR/Keil both have limited size free options. They are expensive commercial products though without any kind of non-commercial licensing, so if you want to go all out you pay thousands of dollars for the system.
Rowley Crossworks: This is what I use. Based on the GCC compiler, but the IDE/debugger are simple to use, pretty powerful, and there is a $150 full working non-commercial license option.
You can also try Codered, which is similar GCC based.
GCC/Eclipse/OpenOCD: I have not looked at this option in a while, so I don't know if anyone has made this any easier, but I found it very difficult to get this working. At the time OpenOCD had some troubles with 64bit systems as well. I'm sure they've worked that out. Anyway, totally free.

Those are the only ones I have had experience with.
 
I've used CodeRed but what I have doesn't work with the on board programmer. I looked at Rowley Crossworks it looks good CodeRed is great but it cost a lot to.

But I found A tool that lets you load with the programmer that's on the ST board could use that with CodeRed
 
Hi Burt,

I installed the Atollic IDE but I'm still struggling. I have not been able to install a valid driver for the ST-Link USB interface so far.

Regards, Mike
 
Mike I had a problem like that with a board I have that used LPCXpresso's It was the Link
 
Hey i just got that stm32F4 board a few days back and havent had much time to play. i couldnt get it working at all in crossworks. Even with the correct tools installed. I get a USB error. Sucks!...
Since i have the weekend off i dont have to sleep much. Hence i can play with it now. So ill give you guys some updates real soon.. hopefully good news
 
So far kind of good news... no usb error but yet another error...
 

Attachments

  • 1.jpg
    220.4 KB · Views: 456
Mines is different... (Sorry for late reply, i didnt get a email on new post )

 

Attachments

  • DONGLE.jpg
    30 KB · Views: 952
Last edited:
Jason did yours work mine said that at first but it was the wrong driver? When I got it to work it shows up as posted

Or let me rephrase that it shows up as a ST-Link dongle till it loads the driver after that it loads the right driver from the start. when plugged in
 
Last edited:
Ok I still get the DEBUG error thing but i think i know why. Crossworks supports the STM32F407VG but these are different they are STM32F407VGT6.

Perhaps thats why it cant find the ROM stuff. Its too new for crossworks. I know its not the ST-LINK itself because i can read/write to the MCU using the "STM32 ST-LINK Utility" program itself.
 
Arg! im going to give up for tonight perhaps heh.. I cant even get uVision to work right with it. Gives me a cant load afx or something like that. So for now ill stop to rest my poor brain.
 
OK here is a conversation with Crossworks support.

ME:
Rowley:
Michael Johnson, Oct-29 08:49 am (BST):

You'll need to use the 2.1.2 release a preview is here

**broken link removed**
Downloading it now and will give my update shortly
 
OK More bad new but im sure its probably something i did or didnt do.
Code:
#include "stm32f4_discovery.h"

void main()
{
  while(1)
  {
  
  }
}

I tried to compile the above and get errors:
 
Jason,

Thank you so much for the effort so far. I have a couple mid-terms on Monday but I'm looking forward to getting back to this afterwards.

Cheerful regards, Mike
 
Ok if i change the architecture to V7m it compiles but not sure how this affects the MCU? ... googling now
 
Jason,

Thank you so much for the effort so far. I have a couple mid-terms on Monday but I'm looking forward to getting back to this afterwards.

Cheerful regards, Mike

No Problem! Im glad i can help anyone I still feel like a HUGE nooB! heh
 
Here my first go with TrueStudio so far so good it complied
 

Attachments

  • build.jpg
    161.6 KB · Views: 439
Last edited:
Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…