Modified 13-12-2005

1ARM development environment

Content

• Philips LPC2106 ARM chip • ARM target board• PSPad customised development environment• Troubleshooting

www.voti.nl/hvu/arm

Modified 13-12-2005

2ARM development environment

Philips LPC2106 ARM chip

http://www.semiconductors.philips.com/pip/LPC2106.html

• LQFP48 (7 x 7 mm2) package • 16/32 bit ARM7TDMI-S processor• 64 kB Static RAM, 128 kB Flash Program Memory.• In-System Programming (ISP) and In-Application Programming

(IAP) via on-chip boot-loader software. • Vectored Interrupt Controller, two UARTs (16C550), Fast I²C (400

kbits/s) and SPI™. • Two 32-bit timers (7 capture/compare channels), PWM unit (6

outputs), Real Time Clock and Watchdog. • Up to thirty-two 5 V tolerant general purpose I/O pins. • Dual power supply: CPU 1.8 V, I/O 3.3 V with 5 V tolerant I/O pads.

Modified 13-12-2005

3ARM development environment

ARM target board

Modified 13-12-2005

4ARM development environment

ARM target board

• ARM LPC2106 chip• USB connector for power only• Parallel JTAG interface (’wiggler’)• Serial interface (RS232, can be disconnected)• 8 LEDs• 16 pushbuttons• 16 x 1 or 16x 2 Character LCD• Small loudspeaker• Reset button• Jumpers select JTAG or bootloader• Extension connector

Modified 13-12-2005

5ARM development environment

PSPad customised development environment

• PSPad editor / user-interface• GCC compiler (Assembler, C, C++)• Insight debugger• MAC_MOT TCP-to-parallel JTAG interface

Modified 13-12-2005

6ARM development environment

Use - preparation

• Install the development environment• Create an empty project directory

no spaces in the pathname!• Unzip a project zip file into that directory• Connect the board (USB + parallel)• Open the project (.ppr) file to start the environment

Modified 13-12-2005

7ARM development environment

Use – build

• Build the project

Modified 13-12-2005

8ARM development environment

Use – start JTAG debugger

• Start the debugger

Modified 13-12-2005

9ARM development environment

Use – configure the debugger interface

• If this screen appears: enter the settings as shown

Modified 13-12-2005

10ARM development environment

Use – (debugger) - download

• Start downloading your code

Modified 13-12-2005

11ARM development environment

Use – (debugger) - start your program

• Run your code

Modified 13-12-2005

12ARM development environment

Use – debugger - stepping

• Single step, step into functions

• Single step, step over functions

Modified 13-12-2005

13ARM development environment

Use – debugger - stepping

• Run up to end of current function

Modified 13-12-2005

14ARM development environment

Use – debugger - stop

• Stop your code, then close the debugger

Modified 13-12-2005

15ARM development environment

troubleshooting

If you see this you must set the MAC_MOT driver to auto-start:

control panel > system > hardware > device manager (select view > show hidden devices) > non plug-and-pray devices > MAC_MOT > driver status = started, type = automatic

Modified 13-12-2005

16ARM development environment

Installing the development environment installs the MAC_MOT driver. If it somehow disappears from your PC you could install the Macraigor OCD commander.

troubleshooting

http://www.macraigor.com/ocd_cmd.htm

Modified 13-12-2005

17ARM development environment

If you try to build while the debugger is still active, you will get this error because the debugger has locked the executable file so the compiler can not write to it.

troubleshooting

Modified 13-12-2005

18ARM development environment

If nothing else seems to help: disconnect the PCB, reset your PC, and start all over.

Don’t use an unpowered USB HUB between your PC and the ARM board. If possible, connect directly to your PC.

troubleshooting