The Installation of Embest IDE Pro Education version

The Embest IDE Pro Education version does not require a license and only works with
the EasyICE download/emulation tool. The Embest IDE Pro version requires a special
license file granted by Embest that is specific to your personal computer and to your
specific PowerICE tool. The non-educational version will not work with the EasyICE
tool. It only works with the PowerICE. These instructions only apply to the educational
version.

To install the Embest software, Insert the CD marked “ENCE 3231 Embedded Systems”
into your CD-ROM. Open the CD, go to the “Embest Products/IDEProEdu2004” directory and
double-click on IDEProEdu.exe.

Click next, and click Yes when the license disclaimer appears.
There will be requirement for you to enter your user name and company name, you can
just input DU as company name, username can be anything if you want. Then click next.

After that, the destination folder screen appears. The default is C:\EmbestIDE, but you
can choose any directory that does not include a space in the name. (Do not choose
C:\Program Files\EmbestIDE but you may choose
C:\pgmfiles\EmbestIDE.) These instructions assume you use the default directory.

Choose full installation. Click next.

Then click next again.

Click next again.

The installation process then displays a progress screen.

Click Finish to restart the computer.

After restarting your computer, copy the S3CEV40\common directory from the CD
(under \Software) to your EmbestIDE root directory. (The default root directory is
C:\EmbestIDE.)

To run the IDE, double click the “EmbestIDE Pro Education Edition for ARM” which
should appear on your desktop. It is also accessible from
Start/Programs/EmbestIDEProEducationEditionforARM.
Project Basic Settings
When creating a new project or running an existing project there are several settings that affect the
generation of code and the environment within which your code will execute. These settings are saved
with each project but the Remote settings may need to be changed periodically for each lab exercise.
You must open a workspace, either new or existing, for the project settings menu to appear.
1. Processor Settings
Select Project-> Settings. The IDE will open a new dialog box. Select the
“Processor” page and adjust the settings as shown in the Figure below. The “Build Tools”
option must be set to “GNU Tools for ARM”.
2. Emulator Settings
Select Project->Settings… The IDE will open a new dialog box. Select the “Remote” tag shown as
below.

The IDE provides two methods to test your software: hardware download or software emulation. If the
S3CEV40 ARM board is not attached to your computer, you can test your code using software
emulation of the ARM7 processor. To do this, choose the “SimArm7” option from the drop-down
menu under “Remote Device:”. Using the software emulator makes the “Speed:” and
“Communication type:” options irrelevant.
If the S3CEV40 board is attached to your computer via the parallel port, choose the
“EasyICEArm7” option. This permits download of your compiled code to the hardware for testing on
the physical device with physical I/O. The EasyICE is the interface between the S3CEV40 board and
your computer. The DB-25 connector plugs into the parallel port on your PC while the 20-pin female
header plugs into the “JTAG” port on the S3CEV40 board. Only LPT1 and LPT2 are supported.

WARNING: If the SimArm7 option is chosen, your code will not be downloaded to the
board even if the board is connected to the EasyICE, yet it will appear to be running properly.
This small error has caused many frustrating hours for students. Be conscious of where your
code is executing!
3. Debugging Settings
The debug related settings are shown below. There are the following three options:
1) General

Download file: Symbol file name and its directory. Symbol file includes debug information.
Normally symbol file is an *.elf format file or a coff format file. This part can be put a little later,
but remember to do it. The *.elf file can be generated after compile.

Action after connected: There are three ways for selection:

1. None -- No actions after the IDE connected to target.

2. Auto download – After the IDE is connected to the target, the file will be automatically
downloaded to the board.

3. Command script -- After the IDE is connected to the target, a script file will be executed first.

Choose “Command Script” and select the file “ev40boot.cs” in “[your installation directory]\
S3CEV40\common” as the command script. This command script is critical as it starts and configures
the board first before running your own code.
 2) Download
Choose “Download” from the “Category:” drop-down menu and the Download settings page is shown
in Figure below.

Download file: Symbol file name and its directory. Symbol file includes debug information.
Normally the symbol file is an elf format file or a binary file. When downloaded as an elf file the
system will automatically convert it into a binary file.

Download verification: Automatically compare the downloaded file if it is the same as the original
file.
Download address: The downloaded file will be stored from this address.

Execute program from:

1. Don’t care – After download the system’s PC (program counter) will not change.

2. Download address – After download the system will execute from this address.

3. Program entry point -- After download, the system will set the PC to the program entry point.

Execute until: The last symbol the system will execute after the download.

After compilation, you will set the Download File. The Download Address should be 0xC000000 as
shown in the Figure with “Program Entry Point” selected.
 3) Memory Map
If the memory map file is used, select this item. Map file is used to control the memory read and write.
But normally, in our experiment we do not use Memory Maps, so we choose “No map file”.
5. Directory Settings
If the user wants to include source files in other directories add them as shown below and click the
“Include Subdirectories” check-box if appropriate.

6.1 Compiler: General

Include the directory of common.

6.2 Compiler: Target Specific Options Settings

The compiler target specific options setting is shown in Figure below.

6.3 Compiler: Code Generation Settings

The code generation setting is shown in Figure below.
7. Assembler Settings
The assembler settings are shown in Figure below. All the settings in this page will be displayed in the
“Assemble Options” window. The users can manually edit the “Assemble Options” but need to follow
the GNU rules.
7.1 Assembler General Settings
The assembler general settings are shown in Figure below.

Include Directory – header files directory.

Object files location – the directory of object files.

Predefinitions – Define the pre-compile macros.

7.2 Assembler Code Generation Settings

The assembler warning setting is shown in Figure below.
7.3 Assembler Target Specific Settings
The assembler target specific setting is shown in Figure below.
7.4 Assembler Warning Options Settings
The assembler warning options setting is shown in Figure below.

8. Linker Settings
The linker settings are shown in Figure below. All the settings in this page will be displayed in the
“Link Options” edit window. The users can manually edit the Link Options but need to follow the
GNU rules.
8.1 Linker General Settings
The linker general setting is shown in Figure.

Executable file – generate executable file.

Library – generate library file.

Linker script file – select this item only when executable output file is selected.

Output file name – could be elf or lib file.

The linker script file is critical. Find the path of “common\ram_ice.ld” and add it to the linker script
file.
8.2 Linker Image Entry Options Settings
The assembler warning settings are shown in Figure below.

Select Entry file – select one of the files listed in the List Box as the first parameter file in the linker
command. When the Image Entry Point is set, this item can be empty.

Image entry point – the entry point of executable file

Notice: Please choose 44binit.o (if it has on the list) as entry file otherwise, you can choose the one
listed, because it contains start up codes.
8.3 Add Library Searching path
Add : -L C:\EmbestIDE\Build\xgcc-arm-elf\arm-elf\lib
-L C:\EmbestIDE\Build\xgcc-arm-elf\lib\gcc-lib\arm-elf\3.0.2
This step is very important. C: is the directory you installed the embest software. As a demo, I
installed on C:, so if you didn’t choose the default installation directory, you need to modify it to fit
your computer.