New Micros TiniARM User manual

TiniARM Development Kit: User Manual Jan 3, 2005
TiniARM Development Kit
User Manual V.3

TiniARM Development Kit: User Manual Jan 3, 2005 1
Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Get (with) the Program(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 LPC2000 Flash Utility Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Installing gnude on W2K. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Included Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.0 Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 simple.cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 main.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 ivt.s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 start.s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.0 Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.0 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.0 Final Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.0 Helps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Compiler: arm-elf-gcc --help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1.1 Compiler Target: arm-elf-gcc --target-help
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2 Assembler: arm-elf-as --help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3 Loader: arm-elf-ld --help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.4 Translation: arm-elf-objcopy --help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

TiniARM Development Kit: User Manual Jan 3, 2005 2
Compiling an Application for the TiniARM From Scratch
Programming the Arm processor in C can be done for free with the use of the freely available and multi-optioned GNU compilers. It can
be a little daunting with 70MB downloads and thousands of pages of text to wade through to find the essential ingredients to make the
recipe you're trying to implement. This manual assumes a neophyte level user and walks through the paces to get a bare application
running on the TiniARM. With the knowledge of this journey, it is hoped that you will be able to forge your own.
NOTE: Changes from first manual (V.1) are marked with a change bar like the one on the left.
1.0 Introduction
The first job is to get programs and documentation. Some comes with the software but sometimes they need documentation. Don't get
me wrong, it's great that there is a lot of documentation but it is vast and too many variables lie in the way of getting what I want. Where's
my hello world program with an interrupt for only 234 bytes? Not 42K of behemoth layers of OS parts and services (which have their own
empire of documentation). I often have to dig for a nugget of info to let me know which variable to modify each time something goes
wrong in compiling, but to find that nugget again would be almost impossible. So here are the steps and nuggets (most of them) I took to
get to the finish line.
To work with the target board you will need:
• the target board
• the development board
• power supply
• rs232 cable
• PC with COM port
• compiler
• downloader
• terminal program
• patience, luck and the NMI help forum
1.1 Overview
First, edit your source code;compile it with a compiler; link it and write it out with a loader; possibly translate the output to one
suitable for downloading; download the result to the target board; attach test equipment and reset board to test it out.
Note all the steps and also note that this is a command line affair, no GUI. Although some are available, I have none to recommend
yet.So crack the knuckles, rub the palms rapidly and push up the sleeves.In addition to being command line user interface (CLUI),
it is Unixish and needs a Unix-like environment to run in. This means using the terminal window in Mac OSX and an extra download
in Windows.
1.2 Get (with) the Program(s)
Whether you are running MacOSX, Windows or Linux, there's a precompiled application out there waiting to be downloaded. These
are big and always come with many more things that you and all of your related family would never be able to use, so be prepared for
a long download even on high speed connections. This document is tied to the gnude 1.2/1.1 release on Windows 2000 and
MacOSX. Search for gnude download or if this link is valid:
http://sourceforge.net/projects/gnude/
Page down and download the appropriate version for your platform(s).
In addition, for the Windows platform you will also need to download from redhat:
http://www.redhat.com/download/cygwin.html
To communicate with the board you will need to run another program on the PC available from Philips at:
http://www.semiconductors.philips.com/files/products/standard/microcontrollers/utilities/
lpc2000_flash_utility.zip
Download what you need and install (cygwin first on Windows).

TiniARM Development Kit: User Manual Jan 3, 2005 3
A web page for the LPC2106 at Philips contains a useful number of links:
http://www.semiconductors.philips.com/pip/LPC2106.html
1.3 LPC2000 Flash Utility Notes
This tool is used to interact with the TiniARM processor over the serial port to move data between it, RAM, flash and the host
computer. It is mainly used to program the processor. The following points will save some time working with this tool.
• The utility for communicating with the processor for transferring data to and from the chip cannot be used to create a file which
is downloadable back to the chip because the first 0x3F bytes are not from the program in the rest of flash but are from the flash
bootloader and when the contents of flash is transferred to the program buffer, it takes the first 0x3F bytes from the bootloader
program and the rest of flash from whatever program is there. If this hex file is then put back into flash, the chip will not boot. To
fix it, the first 0x3F bytes must come from a file source which has the values figured. Or the bytes can be edited in the buffer.
The vector block has been shifted to 0x1E000 but the program prevents the user from seeing that part of flash.
• This has been fixed as of versionV2.2.0 and is available from the LPC2000 files section inYahoo groups:
http://groups.yahoo.com/group/lpc2000/files/
• There is a button to calculate the security code at 0x14 but it is on the flash buffer tool and is not needed for normal downloads.
• The tool cannot handle files which are both RAM and Flash. You will get messages complaining about memory out of range.
This could be something destined for RAM space like an initialized variable and could warrant a second look or it might not
bother you at all.
1.4 Installing gnude onW2K
Download and install cygwin to create a unix environment under windows. Put gnude under “ /cygwin ”. This is seen as just “ / ”
inside a cygwin shell. To set the PATH variable:
export PATH=$PATH:/gnude/bin:/gnude/arm-elf/bin
This will give you access to the tools with or without their prefixes. This means if there is no other gcc tools installed in your paths,
then gcc will be the same as arm-elf-gcc and can be used as a shortcut.
1.5 Included Files
• a.lst - assembly listing of example
• ivt.o - object file from compiling ivt.s
• ivt.s - source code containin the exception vectors for the beginning of flash
• libc.a - C library precompiled archive for use if needed
• lpc210x.h - header file with names for all the registers
• main.c - test program in C
• main.cmd - extra complicated loader script adapted from the tools
• main.hex - final output from compilation process
• main.map - map of symbols and memory
• main.o - compiled object from main.c
• main.out - the output from the loader/linker
• makefile - the script on how to make the test application
• simple.cmd - the script for where the test application fits in memory
• start.o - compiled object file for start.s
• start.s - start up code to set up the micro and transition into main in
2.0 Compiling
All the pieces for compiling in this example reside in one directory. This makes compiling simple. Just enter this command in the
directory with everything in it:
make test

TiniARM Development Kit: User Manual Jan 3, 2005 4
Like magic all the (and only the) required steps are executed to get from multiple source files and libraries to a singular hex file ready for
download along with a memory map file and an assembled code listing. For the first run you should see something like this:
arm-elf-as -o start.o start.s
arm-elf-as -o ivt.o ivt.s
.compiling
..linking
arm-elf-ld -v -Map main.map -nostartfiles -T simple.cmd -o main.out start.o ivt.o main.o libc.a
GNU ld version 2.14 20030612
...copying
arm-elf-objcopy -O ihex main.out main.hex
As projects go, they are seldom simple, once underway for any length of time, so it is best to have some organization up front in terms of
structure. This is where the makefile and loader script come in. The makefile provides a singular point of controlling the compiling
process and a way of managing compiler options and file groupings. The loader script is the recipe for all the ingredients from the
compiler output and other precompiled archives (.a). The two files for these included here are simple and will need to be augmented as
an application grows. Probably the next best thing to add to the makefile is some semblence of proper directory structure where source
is kept separate from all the other pieces. The libc.a file is in the source directory for the simple directory structure in the makefile.
The following code example has been taken from application note 10254 and modified for this document and for the GNU compiler. But
it is a working example which can be built upon. The interrupt does not work yet and has not been debugged other than a test to see if
the interrupt routine was ever called (it wasn’t), indicating probably a configuration problem.
2.1 Makefile
# for making arm code Rob Chapman Apr 1, 04
NAME = test io
CC = arm-elf-gcc
LD = arm-elf-ld -v
AR = arm-elf-ar
AS = arm-elf-as
CP = arm-elf-objcopy
.SUFFIXES : .o .c .s
CFLAGS = -I./ -c -O3
AFLAGS = -ahls -mapcs-32
CAFLAGS = $(CFLAGS) -Wa,-ahls,-mapcs-32
LFLAGS = -Map main.map -nostartfiles -T simple.cmd
CPFLAGS = -O ihex
test: main.out
@ echo "...copying"
$(CP) $(CPFLAGS) main.out main.hex
main.out: start.o ivt.o main.o simple.cmd
@ echo "..linking"
$(LD) $(LFLAGS) -o main.out start.o ivt.o main.o libc.a
.c.o:
@ echo ".compiling"
@ $(CC) $(CAFLAGS) $< > a.lst
mainin: start.s ivt.s main.c

TiniARM Development Kit: User Manual Jan 3, 2005 5
@ echo ".compiling"
$(CC) $(CFLAGS) start.s ivt.s main.c
2.2 simple.cmd
/* Simple command script for organizing memory Rob Chapman Apr 1, 04 */
SECTIONS
{
/* interrupt vectors */
. = 0x0; /* start of flash */
.interp :
{
*(.interp)
}
/* code and constants */
.text :
{
*(.text)
*(.strings)
*(.rodata.*)
*(.init)
*(.comment)
}
/* uninitialized data */
. = 0x40000000; /* start of ram */
.bss :
{
*(.bss)
*(COMMON)
*(.data)
}
}
2.3 main.c
/* code originally from phillips appnote 10254 */
/* *********************************************************
Function declarations
********************************************************* */
void IRQHandler(void);
void feed(void);
void Initialize(void);
/**********************************************************
Header files
**********************************************************/
#include "LPC210x.h"
#include <string.h>
// serial port
#define RDR 0x01

TiniARM Development Kit: User Manual Jan 3, 2005 6
#define THRE 0x20
char rx_query(void)
{return UART0_LSR & RDR;
}
char tx_query(void)
{return UART0_LSR & THRE;
}
void tx(char c)
{UART0_THR = c;
}
char rx(void)
{return UART0_RBR;
}
void tx_str(char *s) // send a string
{while(*s) if (tx_query())
tx(*s++);
}
/**********************************************************
MAIN
**********************************************************/
void __main (void)
{char *x = (char *)0, *y = (char *)0x1000;
/* Initialize the system */
Initialize();
/* Start timer */
// Interrupts not working yet so this code is commented out for now
// TIMER1_TCR=0x1;
// For testing library inclusion
// memcpy(x,y,100);
// test banner
tx_str("\n\rTest echo\n\r");
// echo for main loop
while(1)
if (rx_query() && tx_query()) // received and ready to send
tx(rx()); // get and send
}

TiniARM Development Kit: User Manual Jan 3, 2005 7
/**********************************************************
Initialize
**********************************************************/
extern const char _text_start, _text_end;
extern char _data_start, _data_end;
#define PLOCK 0x400
void Initialize(void)
{
// memcpy(&_data_start, &_text_end, &_data_end - &_data_start);
// set io pins for leds red off, yellow off, green on
IODIR |= 0x03800000; // 23-25 are outputs
IOSET = 0x00800000; // green led on
IOCLR = 0x03000000; // red and yellow off
/*
* Initialize PLL (Configured for a 10MHz crystal) to
* boost processor clock to 60MHz
*/
/* Setting Multiplier and divider values */
PLLCFG=0x25;
feed();
/* Enabling the PLL */
PLLCON=0x1;
feed();
/* Wait for the PLL to lock to set frequency */
while(!(PLLSTAT & PLOCK)){}
/* Connect the PLL as the clock source */
PLLCON=0x3;
feed();
/*
* Enabling MAM and setting number of clocks used for
* Flash memory fetch
*/
MAMCR=0; // make sure MAM is off before adjusting
MAMTIM=0x3;
MAMCR=0x2;
/*
* Setting peripheral Clock (pclk) to System
* Clock (cclk)
*/
VPBDIV=0x1;
/* Initialize GPIO */
// IODIR=0xFFFF;
// IOSET=0xFFFF;
/* Initialize Timer 1 */

TiniARM Development Kit: User Manual Jan 3, 2005 8
TIMER1_TCR=0x0;
TIMER1_TC=0x0;
TIMER1_PR=0x0;
TIMER1_PC=0x0;
/* End user has to fill in the match value */
TIMER1_MR0=0x123456;
/* Reset and interrupt on match */
TIMER1_MCR=0x3;
/* Initialize VIC */
VICIntSelect=0x0; /* Timer 1 selected as IRQ */
VICIntEnable= 0x20; /* Timer 1 interrupt enabled */
VICVectCntl0= 0x25;
/* Address of the ISR */
VICVectAddr0=(unsigned long)IRQHandler;
/* initialize serial port */
// initialize UART
PINSEL0 = 5; // enable UART0 in/out
UART0_FCR = 0x7; // enable and reset fifos
UART0_LCR = 0x83;// 8 bits; enable divisor latches
UART0_DLL = 0x87; // LSB divider for 60mhz to be 9600x16
UART0_DLM = 0x01; // MSB
UART0_LCR = 0x3; // disable divisor latches
}
/**********************************************************
Timer 1 ISR
**********************************************************/
void __attribute__((interrupt)) IRQHandler(void)
{
/*
* The Interrupt Service Routine code will come here. The
* interrupt needs to be cleared in Timer1 and a write must
* be performed on the VIC Vector Address Register to
* update the VIC priority hardware. Here the user could
* blink a few LED’s or toggle some port pins as an
* indication of being in the ISR
*/
IOSET = 0x01000000; // yellow led on
TIMER1_IR=0x1;
VICVectAddr=0xff;
}
void feed(void)
{
PLLFEED=0xAA;
PLLFEED=0x55;
}

TiniARM Development Kit: User Manual Jan 3, 2005 9
2.4 ivt.s
@ code originally from phillips appnote 10254
@ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––
@ Assembler Directives
@ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––
.section .interp,"ax" @ alocateable and executable New Code section
@ compiler option : CODE32 @ ARM code
.extern start @ start symbol not
@ defined in this
@ section
Entry: @ Defines entry point
@ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––
LDR PC, =_start
LDR PC, Undefined_Addr
LDR PC, SWI_Addr
LDR PC, Prefetch_Addr
LDR PC, Abort_Addr
@ At 0x14 the user should insert a signature (checksum).
@ This signature enables the bootloader to determine if
@ there is valid user code in the Flash. Currently most of
@ the Flash programming tools (debuggers and ISP utility)
@ have this feature built–in so the end user need not worry
@ about it. If the tool does not provide this feature then
@ the value has to be computed manually and has to be
@ inserted at 0x14. Details on computation of checksum
@ could be found in the Flash programming chapter in the
@ LPC2104/5/6 User Manual.
NOP @ for code to be
LDR PC, [PC, #0xFFFFF010] @ load irq vector from vic
LDR PC, FIQ_Addr
Undefined_Addr: .word Undefined_Handler
SWI_Addr: .word SWI_Handler
Prefetch_Addr: .word Prefetch_Handler
Abort_Addr: .word Abort_Handler
FIQ_Addr: .word FIQ_Handler
@ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––
@ Exception Handlers
@ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––
@ The following dummy handlers do not do anything useful in
@ this example. They are set up here for completeness.
Undefined_Handler:
B Undefined_Handler
SWI_Handler:
B SWI_Handler
Prefetch_Handler:
B Prefetch_Handler
Abort_Handler:
B Abort_Handler
FIQ_Handler:
B FIQ_Handler