STM32F4 Discovery Dev Board

From BUILDS

(Difference between revisions)
Jump to: navigation, search
Revision as of 16:26, 23 May 2012
Cwoodall (Talk | contribs)
(Open Source Toolchain)
← Previous diff
Revision as of 00:25, 26 May 2012
Cwoodall (Talk | contribs)

Next diff →
Line 2: Line 2:
= Open Source Toolchain = = Open Source Toolchain =
 +
 +== Linux ==
Under linux this is rather straightforward. I was able to compile with toolchain without a hitch using [http://cu.rious.org/make/stm32f4-discovery-board-with-linux/ these instructions], under OS X I would imagine its a tad more of a pain in the ass. The programs/scripts being used are the following: Under linux this is rather straightforward. I was able to compile with toolchain without a hitch using [http://cu.rious.org/make/stm32f4-discovery-board-with-linux/ these instructions], under OS X I would imagine its a tad more of a pain in the ass. The programs/scripts being used are the following:
Line 10: Line 12:
* [http://www.st.com/internet/mcu/product/252149.jsp#SOFTWARE_AND_DEVELOPMENT_TOOLS The official STM32F4 header files and libraries] : Not sure how compatible these are with our toolchain, but its probably worth grabbing them. * [http://www.st.com/internet/mcu/product/252149.jsp#SOFTWARE_AND_DEVELOPMENT_TOOLS The official STM32F4 header files and libraries] : Not sure how compatible these are with our toolchain, but its probably worth grabbing them.
 +
 +
 +== OS X ==
 +
 +Thanks to [[Alex Whittemore]] there is some good documentation [here http://www.alexwhittemore.com/open-source-ide-and-toolchain-for-the-stm32f4-discovery-on-mac-osx-lion/] on one method of getting set up with Eclipse. [[Chris Woodall]] would prefer to use emacs + a makefile to do his development, so the methodology is a little different.
 +
 +First, you should make sure you have XCode installed, because that will install gcc and all of the development tools you need for some of the future steps.
 +
 +Now, lets get [http://www.macports.org/ macports] if you have a Mac and some self respect you should already have macports anyway (or [http://mxcl.github.com/homebrew/ homebrew]). Then we will install the arm-none-eabi toolchain, this might take awhile if you have never used macports before, while you are at it you should install git:
 +
 +<pre>
 +$ sudo port install arm-none-eabi-*
 +$ sudo port install git # optional
 +</pre>
 +
 +Now we will use git to grab texane's great [https://github.com/texane/stlink stlink program]:
 +
 +<pre>
 +$ mkdir ~/src #optional, but my preferred working directory for installations like this
 +$ cd ~/src # optional
 +$ git clone https://github.com/texane/stlink.git
 +$ cd stlink/gdbserver
 +$ make
 +</pre>
 +
 +Now you should have everything to follow [http://cu.rious.org/make/stm32f4-discovery-board-with-linux/ these instructions] from Rious.
== Makefile == == Makefile ==
...Coming soon... ...Coming soon...

Revision as of 00:25, 26 May 2012

Contents

Specs

Open Source Toolchain

Linux

Under linux this is rather straightforward. I was able to compile with toolchain without a hitch using these instructions, under OS X I would imagine its a tad more of a pain in the ass. The programs/scripts being used are the following:

  • summon-arm-toolchain : Downloads and compiles the arm-none-eabi toolchain which we will be using. I am not sure if it compiles with the STM32F4's FPU support.
  • Texane's stlink : Allows us to program using the stlink on the STM32F4 Discovery board. We program using gdb to load the program into SRAM for now. If you link correctly you can flash too. In the future this should work to program other STM32 chips via the SWD link (if the jumpers are set correctly).


OS X

Thanks to Alex Whittemore there is some good documentation [here http://www.alexwhittemore.com/open-source-ide-and-toolchain-for-the-stm32f4-discovery-on-mac-osx-lion/] on one method of getting set up with Eclipse. Chris Woodall would prefer to use emacs + a makefile to do his development, so the methodology is a little different.

First, you should make sure you have XCode installed, because that will install gcc and all of the development tools you need for some of the future steps.

Now, lets get macports if you have a Mac and some self respect you should already have macports anyway (or homebrew). Then we will install the arm-none-eabi toolchain, this might take awhile if you have never used macports before, while you are at it you should install git:

$ sudo port install arm-none-eabi-*
$ sudo port install git # optional

Now we will use git to grab texane's great stlink program:

$ mkdir ~/src #optional, but my preferred working directory for installations like this
$ cd ~/src # optional
$ git clone https://github.com/texane/stlink.git
$ cd stlink/gdbserver
$ make

Now you should have everything to follow these instructions from Rious.

Makefile

...Coming soon...

Personal tools