diff options
author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2009-10-04 17:48:35 +0000 |
---|---|---|
committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2009-10-04 17:48:35 +0000 |
commit | 365ffcd212b8836b7dce5ec21ea4205148bc85e5 (patch) | |
tree | fc0e1809da973d97a51a1dd2de77c9fe29628a55 /nuttx/configs/stm3210e-eval/README.txt | |
parent | d977e1c8ff3fa9f8186a0f0e65612d0d2bf2309b (diff) | |
download | nuttx-365ffcd212b8836b7dce5ec21ea4205148bc85e5.tar.gz nuttx-365ffcd212b8836b7dce5ec21ea4205148bc85e5.tar.bz2 nuttx-365ffcd212b8836b7dce5ec21ea4205148bc85e5.zip |
Started a RIDE project for STM32
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2120 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/configs/stm3210e-eval/README.txt')
-rwxr-xr-x | nuttx/configs/stm3210e-eval/README.txt | 34 |
1 files changed, 29 insertions, 5 deletions
diff --git a/nuttx/configs/stm3210e-eval/README.txt b/nuttx/configs/stm3210e-eval/README.txt index d955a7c14..0a2cc0b1a 100755 --- a/nuttx/configs/stm3210e-eval/README.txt +++ b/nuttx/configs/stm3210e-eval/README.txt @@ -7,7 +7,7 @@ Development Environment Either Linux or Cygwin on Windows can be used for the development environment. The source has been built only using the GNU toolchain (see below). Other toolchains will likely cause problems. Testing was performed using the Cygwin - environment because the Raisonance R-Link emulate and some RIDE7 development tools + environment because the Raisonance R-Link emulatator and some RIDE7 development tools were used and those tools works only under Windows. GNU Toolchain Options @@ -78,6 +78,25 @@ GNU Toolchain Options the paths to Cygwin's /bin and /usr/bin directories appear BEFORE the devkitARM path or will get the wrong version of make. +IDEs +^^^^ + + NuttX is built using command-line make. It can be used with an IDE, but some + effort will be required to create the project (There is a simple RIDE project + in the RIDE subdirectory). Here are a few tip before you start that effort: + + 1) Select the toolchain that you will be using in your .config file + 2) Start the NuttX build at least one time from the Cygwin command line + before trying to create your project. This is necessary to create + certain auto-generated files and directories that will be needed. + 3) Set up include pathes: You will need include/, arch/arm/src/stm32, + arch/arm/src/common, arch/arm/src/cortexm3, and sched/. + 4) All assembly files need to have the definition option -D __ASSEMBLY__ + on the command line. + + Startup files will probably cause you some headaches. The NuttX startup file + is arch/arm/src/stm32/stm32_vectors.S + NuttX buildroot Toolchain ^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -118,11 +137,16 @@ NuttX buildroot Toolchain DFU ^^^ - The linker files in these projects assume that you will be loading code - using STMicro built-in USB DFU loader. In this case, the code will not + The linker files in these projects can be configured to indicate that you + will be loading code using STMicro built-in USB DFU loader. You can specify + that by adding: + + CONFIG_STM32_DFU=y + + To you .config file. If CONFIG_STM32_DFU is defined, the code will not be positioned at the beginning of FLASH (0x08000000) but will be offset - to 0x08003000. If you need to change that origin, you will need to - edit the file(s) ld.script for each configuration. + to 0x08003000. If you need to change that origin for some other bootloader, + you will need to edit the file(s) ld.script.dfu for each configuration. The DFU SE PC-based software is available from the STMicro website, http://www.st.com. General usage instructions: |