In this article you’ll find some information about how to configure GNUARM toolset for compiling ARM7 microcontrollers.
GNUARM is the open source toolset for ARM7 MCUs. It has GCC compiller and debugger. Our purpose now is to set up tools in Windows environment and compile one project.
First of all download compiled toolset from https://www.gnuarm.com:
Select the newest [GCC-4.0 toolchain] located bellow Cygwin.
After it is downloaded, start the installation:
- Start window
- Accept license agreement.
- Select folder where do you want GNUARM to be installed:
- Select the components. You can select all of them.
- Chose Start menu folder name – just leave as it is.
- Select desktop shortcut to be placed. I higly recoment to check Cygwin DLL, because despite I had cygwin installed, but I had to copy DLLs to copy manually. If this option ischecked, DLL files will be copied without bothering you.
- And press install..
- Select checkbox in order to create system variable: PATH=c:\gnuarm\bin
After we have GNUARM installed, download binutils from https://optimize.ath.cx/ARM7/src/utils.zip. Download this archive and unpack all contents to c:\gnuarm\bin folder. Also download https://optimize.ath.cx/ARM7/src/cygncurses-8.dll and put it in c:\gnuarm\bin folder. Now we are set to start compillation.
Lets try test compillation. Jus download project from https://optimize.ath.cx/ARM7/src/lpc2214_blink.zip and extract in any folder. Here you’ll find few files:
|lpc2214.h||LPC2214 header. You can also download from www.gnuarm.com page where support files are.|
|blink.c||LED blink example program.|
|boot.s||The startup routine which first is executed after the resetting CPU. From among these C main function is called.|
|lpc2214-rom.ld||The load script file which linker usesThe start address size and the like of ROM/RAM is described. Necessity to ROM conversion binary is drawn up.|
|setenv.cmd||Configuration file, where you have to show path to C:\GNUARM\bin and bin C:\GNUARM\bin\utils|
|jtag_flash.exe||The tool, which writes the flash by way of jtagWriting the hex file, which it appoints, it executes.When ‘N’ is appointed in 2nd parameter, after the writing in, it does not execute.|
|jtag_stub.exe||The JTAG debugger for GDB/Insight.|
Because setenv.cmd is used to show path to C: when GCC is installed in different location, you have to edit it. If you left default settings, then don’t edit this file.
Lets try to compile this program. Start DOS console window:
Lets create hex file. I leave make file not edited. So I will have to use commands: make and once again make.hex. That’s it hex is done.
Here is a table with most common make commands:
|Make||Compiling & linking and forming the elf file|
|Make clean||The formation file (o lst elf hex bin) it deletes|
|Make hex||Hex (forming the hexa-) file|
|Make bin||Bin (binary) forming the file|
|Make lst||Listing (assembling) formation of file|
|Make run||Compiling & linking and it writes in to the flash, starts the program|
|Make debug||Compiling & linking and it writes in to the flash, starts Insight/GDB. Because it does not start the program automatically, you indicate with the debugger|
If you have programmer adapter, you can flash you ARM7 microcontroller with only one command – make run.