Follow the steps below to create a new project file and to specify
and organize your source (and debug) files that are a part of this
project.
Create a New Project File with the µVision menu
command Project — New Project. Select a microcontroller from the Device Database™. Use the
MCB2103 Board to develop code for the LPC2101, LPC2102, or
LPC2103 devices.
Add Startup Code.
The Startup file provides pre-configured startup code for the
MCB2103 board. The Startup file you use varies depending on the
toolset you select.
For Keil tools:
C:\KEIL\ARM\BOARDS\KEIL\MCB2103\BLINKY.
For GNU toolset:
C:\KEIL\ARM\GNU\BOARDS\KEIL\MCB2103\BLINKY.
For ARM/ADS tools:
C:\KEIL\ARM\ADS\BOARDS\KEIL\MCB2100\BLINKY.
Copy the appropriate Startup file to your project
folder and add it to your project.
Add a Linker Control Script to control the link process
for the GNU tools. Two pre-configured linker control script files
are available are located in the same folder as the Startup file
(see the previous step). They are:
Flash.ld configures the linker for program code in
Flash ROM (typical configuration).
RAM.ld configures the linker for program code in RAM
(used for more extensive debugging).
Copy the linker control script file of your choice to
your project folder. This file is required to set up the linker
controls.
Add your own Source Code to the project using the µVision
editor (or any editor of your choice) by either:
Right-clicking a group in the Project Window,
and selecting Add Files to Group from the context
menu,
Or
Use the Components,
Environment and Books toolbar button (or select Project —
Components, Environment and Books — Project Components) to
display the dialog below.
Within this dialog you may create and organize files into groups
or create new project targets that have different tool
configurations.
This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.
ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.