Iw EMDBY UM 01 R1.0 REL2.0 - Stub

Stub Control Panel user manual for Mission 10x-Unified Learning Kit
R 2.0
Stub Control Panel user manual for

Mission 10x-Unified Learning Kit
iW-EMDBY-UM-01-R1.0REL2.0_stub
14th Feb. 11
Authors
Supreet
APPROVAL
Name
Function
Organisation
Date
Signature
Wipro
Mr. Sebikumar Kuruvilla
Distribution
Mr. Abdullah Khan

Mr. Mohammed Saliya
Contact Info
Name
Telephone
iWave Systems Tech. Pvt. Ltd.

7/B, 29th Main,
BTM Layout, 2nd Stage,
Bangalore 560 076, India.
+91-80-2668-3700
+91-80-2678-1643
e-mail
emdby@iwavesystems.com
iWave Systems Technologies Pvt. Ltd.

(Confidential)
R 2.0
DOCUMENT IDENTIFICATION
Project Name
Document Name
Document Home
iW-EMDBY
iW-EMDBY-UM-01-R1.0-REL1.0
//server/emdby/svn/trunk/iW-EMDBY-PF-01-R1.0/iW-EMDBYSF-01-R1.0/iW-EMDBY-UM-01-R1.0/iW-EMDBY-UM-01-R1.0RELx.yz-ULK/iW-EMDBY-UM-01-R1.0-REL2.0-ULK/iWEMDBY-UM-01-R1.0-REL2.0_stub.doc
2.0
Final version
Wipro
Revision No
Status
Audience
Document Revision History

Revision
Date
Description
Author
1.0
13th July 2010 Initial Draft Version
2.0
14th Feb 2011 Final Version
PROPRIETARY NOTICE: This document contains proprietary material for the sole use of the
intended recipient(s). Do not read this document if you are not the intended recipient. Any
review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), you are hereby notified that any disclosure,
copying distribution or use of any of the information contained within this document is
STRICTLY PROHIBITED. Thank you. iWave Systems Tech. Pvt. Ltd.

(Confidential)
R 2.0
Table of Contents
1.
PROCEDURE TO USE THE ULK CONTROL PANEL.................................................................................6

1.1.
LAUNCHING ULK CONTROL PANEL..............................................................................................................6
1.2.
LIST ULK BUTTON.......................................................................................................................................8
1.3.
LIST UNNAMED...........................................................................................................................................15
1.4.
ULK NAMING..............................................................................................................................................17
1.5.
FIND ULK....................................................................................................................................................21
1.6.
CONNECT.....................................................................................................................................................24
1.7.
DISCONNECT................................................................................................................................................27
1.8.
LOAD............................................................................................................................................................29
1.8.1.
ARM Binary Download.....................................................................................................................30
1.8.2.
FPGA Download................................................................................................................................33
1.9.
RUN..............................................................................................................................................................36
1.9.1.
RUN(Execute) ARM Binary..............................................................................................................37
1.9.2.
Run(Execute) FPGA...........................................................................................................................38
1.10. CONTINUE....................................................................................................................................................40
1.11. MEM R/W....................................................................................................................................................41
1.11.1.
Mem Read..........................................................................................................................................44
1.11.2.
Mem Write..........................................................................................................................................50
1.12. NAND READ.................................................................................................................................................52
1.13. REG R/W ARM/DSP...................................................................................................................................55
1.14. BANKED REG R/W ARM/DSP....................................................................................................................59
1.15. FLASH..........................................................................................................................................................63
1.15.1.
Flashing X Loader..............................................................................................................................66
1.15.2.
Flashing U Boot..................................................................................................................................69
1.15.3.
Flashing Linux Image.........................................................................................................................72
1.15.4.
Flashing Root File System..................................................................................................................76
1.15.5.
Flashing FPGA...................................................................................................................................80
1.15.6.
Flashing General.................................................................................................................................83
1.16. FLASH RELEASE...........................................................................................................................................86
1.17. ADVANCED...................................................................................................................................................90
1.17.1.
General options...................................................................................................................................91
1.17.2.
Boot Modes Option............................................................................................................................97
1.18. SEND..........................................................................................................................................................102
1.19. SAVE LOG..................................................................................................................................................106
1.20. STOP.........................................................................................................................................................108
2.
STUB CONTROL PANEL APIS...................................................................................................................110

2.1.
2.2.
2.3.
2.4.
ULK_PRINTF...............................................................................................................................................110
ULK_CPANEL_PRINTF.................................................................................................................................110
ULK_SCANF_HEX........................................................................................................................................111
ULK_SCANF_STRING...................................................................................................................................111

(Confidential)
R 2.0
2.5.
2.6.
3.
PROCEDURE TO CREATE AND COMPILE ECLIPSE APPLICATION..............................................113

3.1.
3.2.
3.3.
4.
EX_CPANEL_PRINT.....................................................................................................................................143
EX_DEBUG_BREAK.....................................................................................................................................147
EX_GPIO_INTERRUPT..................................................................................................................................156
EX_LED......................................................................................................................................................162
EX_SERIAL_PRINT......................................................................................................................................170
EX_SW_INTERRUPT....................................................................................................................................174
DIP SWITCH SETTING FOR DIFFERENT BOOT MODES...................................................................180

5.1.
5.2.
5.3.
5.4.
5.5.
6.
PROCEDURE TO LAUNCH ECLIPSE TOOL....................................................................................................113

PROCEDURE TO CREATE A NEW C PROJECT:..............................................................................................116
PROCEDURE TO COMPILE THE C PROJECT.................................................................................................137
PROCEDURE TO EXECUTE AND TEST SAMPLE ULK APPLICATIONS.........................................143

4.1.
4.2.
4.3.
4.4.
4.5.
4.6.
5.
DEBUG_BREAK......................................................................................................................................112
DEBUG_BREAK_INTR..........................................................................................................................112
BOOT MODE 2............................................................................................................................................180

BOOT MODE 3............................................................................................................................................181
BOOT MODE 4............................................................................................................................................182
BOOT MODE 5............................................................................................................................................183
BOOT MODE 6............................................................................................................................................184
TECHNICAL SUPPORT................................................................................................................................185

(Confidential)
R 2.0

(Confidential)
R 2.0
User Manual for ULK Control Panel

Note: Make sure that Toggle switch is set to Normal (Stub) mode when running the
Control panel. Refer the indication provided in acrylic. If it is not set, Control panel will
not work. Please Refer the figure below to set the Target Board in Normal (Stub) Mode.
The Lab Operating mode is where user gets the control of u-boot command prompt.

(Confidential)
R 2.0
1. Procedure to use the ULK Control Panel

This manual contains the procedure to use the ULK Control panel
1.1. Launching ULK Control Panel

1. Click on the ULK control panel icon on the Desktop or from the Desktop toolbar to
Launch the ULK control panel as shown in figure below.

(Confidential)
R 2.0
2. Ulk Control Panel will be launched as shown in figure below. Initially it will be in Not
Connected State as shown in ULK Device Status Field.

(Confidential)
R 2.0
1.2. LIST ULK Button

This button is used to find all the Connected Stub clients. The Maximum Number of Stub Clients
that can be detected is 200. The Number of stub clients that will be detected/displayed depends
on the value set in the ULK Count field. If ALL is selected, it will try to detect 200 Stub
Clients if it is connected.
1. Before Sending any commands to the Connected Client Stub, Make sure that ULK Host
PC is configured properly with IP address. If the IP address is not set in the Host PC,
When we click on the List ULK button, the following error will be displayed.

(Confidential)
R 2.0
2. Select the Number of Stub Clients to be detected from the Stub Host in the ULK
Count field. For eg: In the figure below, ULK Count is selected as 1 which means
that Stub host will send the Broadcast message to all the Stub Client and once Stub Host
gets the response from any 1 Stub client, it will not accept the response from any other
Stub client. And hence only 1 Stub client Will be displayed in the List Down menu.

(Confidential)
R 2.0
3. Click on the List ULK Button as shown in figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
4. Once the List ULK button is clicked with ULK Count set to 1, Host Stub will wait
for the response from the Stub client for broadcast packet.The Host Stub will start
scanning for the Stub Client as shown in figure. The ULK Device Status will be
updated as Scanning.

(Confidential)
R 2.0
5. Once the Host Stub gets the response from the Stub client, it will Display the Number of
ULK detected (in our case 1) in the list down menu as shown in figure below.

(Confidential)
R 2.0
List Down Menu
6. If we Click on the List Down menu, it will show the details about the Detected Client
Stub. For eg: In the Figure below, ULK Stub Client Name is NO-NAME, IP- Address
is 192.168.2.80 and MAC- Address is 11:22:33:44:55:67.

(Confidential)
R 2.0

(Confidential)
R 2.0
7. If the Stub Host is not able to detect the Stub client when the List ULK button is
clicked, the below shown error No ULKs Found During Scan will be displayed.This
may occur if not Client Board is connected or if the network is not up in the Client board
or Stub mode is not set using Toggle switch in client board.

(Confidential)
R 2.0
1.3. List UnNamed

This Button is used to detect all the Un-Named Stub Client. The Stub Host will wait for 60
seconds to get the responses from all the Un-Named Stub Clients. After 60 seconds, Stub Host
will display all the Stub clients detected in the List Down menu.
1. Click on the List UnNamed button as shown in figure below.

(Confidential)
R 2.0
2. It will Display the Un-Named Stub client in the List Down menu as shown in figure
below. The Stub Client Name is NO-NAME, IP-Address is 192.168.2.80 and MACAddress is 11:22:33:44:55:67.

(Confidential)
R 2.0

(Confidential)
R 2.0
1.4. ULK Naming

This is used to Assign the name to the Un-Named Stub Client/ to change the name of stub
Client.
1. Select the Stub client from the list-down menu whose Name has to be changed and Click
on the ULK Naming button as shown in figure below.

(Confidential)
R 2.0
2. The following window will be displayed as shown in figure below. It will display the
Stub Client IP-Address and Existing ULK Name. For eg: In our case IP Address is
192.168.2.80, ULK Name is NO-NAME.
3. Change ULK Name. For eg: In our case, ULK Name is set to ULK1 and Time Out is
set to 60 seconds. This Timeout means that After issuing the Name ULK command, How
much time to wait for the response from Stub client .Once it changes the Name, it will
return immediately. Click on Name ULK as shown in figure below.

(Confidential)
R 2.0
4. Once the Name ULK button is clicked, a warning message will be displayed asking
whether Name can be changed or not. Click on OK as shown in figure below.

(Confidential)
R 2.0
5. If the ULK Naming is successful, Below shown message ULK Naming Completed
Successfully will appear.

(Confidential)
R 2.0
After Changing the Stub Client Name, Stub Host will again scan for the Stub client and
will display in the List down menu. For eg: In our case ULK name is changed from NONAME to ULK1 and is displayed in the List down menu as shown in figure below.

(Confidential)
R 2.0
1.5. Find ULK

This is used to Find any Particular Stub Client by name.
1. Click on the Find ULK button as shown in figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
2. The below Shown window will be displayed when Find ULK button is clicked. Enter
the ULK Stub Client Name to be found and click on Scan Button. For Eg: in our case
ULK Name is ULK1.
3. The Stub host will search for the Stub client with name ULK1 and if it finds, it will
display the Stub client details in the List Down menu as shown in figure below.

(Confidential)
R 2.0
4. If the Stub Host is not able to find the particular stub client(for eg ULK1), the below
shown error message will be displayed.

(Confidential)
R 2.0
1.6.Connect
This is used to connect the Stub Host to the Stub Client displayed in the list down menu.After the
connection is established, user can do all the operations on the Stub Client.

(Confidential)
R 2.0
1. After selecting the Stub client from the list down menu, Click on the Connect button to
connect to the Stub Client as shown in figure below.
2. If the Connection is successful, the below Shown ULK information Connection

Established will be displayed.

(Confidential)
R 2.0
3. After Establishing the connection, the ULK Device Status will be updated as
Connected - Idle as shown in figure below.

(Confidential)
R 2.0
1.7. DisConnect
This is used to Disconnect the Previous connection between Stub Client and Stub Host.
1. Click on the DisConnect button as shown in figure below.

(Confidential)
R 2.0
2. After the Disconnection is successful, the ULK Device Status will be updated as Not
Connected as shown in figure below.

(Confidential)
R 2.0
1.8.Load
This is used to download the user application binary/srec or FPGA XSVF file in the SD-RAM
location for execution.

(Confidential)
R 2.0
1. Click on Load button as shown in figure below..

(Confidential)
R 2.0
1.8.1. ARM Binary Download

1. When the Load button is clicked, the following window will be displayed. Make sure that
ARM tab is selected. Enter the SD RAM Load Address where the ARM binary has
to be downloaded. By Default its 0x82000000.
2. Select the ARM binary file name as shown in figure below. Click on Load Button to
load the ARM binary in the SD-RAM location 0x82000000.Note that File with extension
.bin(binary) and .srec(srecord) will only be supported.

(Confidential)
R 2.0
3. Once the Load Button is clicked, the Below Shown ULK Warning message will be
displayed. Click on OK .

(Confidential)
R 2.0
4. Once the File is downloaded in the SD-RAM location successfully, the below shown
message File Successfully Sent to Stub Client will be displayed .

(Confidential)
R 2.0

(Confidential)
R 2.0
1.8.2. FPGA Download

1. When the Load button is clicked, the following window will be displayed. Make sure that
FPGA tab is selected. Enter the SD RAM Load Address where the FPGA file
(XSVF) has to be downloaded. By default its 0x82000000.
2.
Select the FPGA file name(ulk_fpga_led.xsvf) as shown in figure below. Click on

Load Button to load the FPGA File in the SD-RAM location 0x82000000.Note that
File with extension .XSVF will only be supported.

(Confidential)
R 2.0
3. Once the Load button is clicked, the below shown warning message will be displayed.
Click on OK to continue the file download.
4. Once the FPGA file is successfully downloaded in the SD_RAM, the below shown
message File Successfully Sent to Stub Client will be displayed. Click on OK and
then on Cancel to enter the main application page.

(Confidential)
R 2.0
1.9.Run
This is used to Run(execute) the user application binary/srec or FPGA XSVF file from the
previously downloaded SD-RAM location.
1. Click on the Run button as shown in figure below.

(Confidential)
R 2.0
1.9.1.
RUN(Execute) ARM Binary
1. Enter the SD-RAM Address from which the ARM binary has to be executed. Default is
0x82000000. Also Make Sure that ARM tab is selected. Click on Execute button.

(Confidential)
R 2.0
2. When the Execute button is Clicked, the below message will be displayed.Click on
OK to Execute the Application from the SD-Ram Location 0x82000000.
3. Once the execution of the Application is completed successfully, the below shown
message Program Execution Completed will be displayed as shown in figure below.

(Confidential)
R 2.0
1.9.2.
1.
Run(Execute) FPGA
Enter the SD-RAM Address from which the FPGA has to be executed. Default is
0x82000000. Also Make Sure that FPGA tab is selected. Click on Execute button.

(Confidential)
R 2.0
2. When the Execute button is Clicked, the below message will be displayed.Click on
OK to Execute the FPGA Application from the SD-Ram Location 0x82000000.

(Confidential)
R 2.0
3. Once the execution of the FPGA Application is completed successfully, the below shown
message FPGA Programming Success will be displayed as shown in figure below

(Confidential)
R 2.0
1.10. Continue
If the User application enters in the Debug Trap mode, User has to Click on the Continue
button to continue the Program Execution as shown in figure below.

(Confidential)
R 2.0
1.11. Mem R/W

This is used to read /write the data in the peripheral registers(including DDR) present in the
board. This is possible only when the Stub host has established the connection with Client
Stub(using Connect button).
1. Click on the Mem R/W button to read/ write in the peripheral register as shown in
figure below.

(Confidential)
R 2.0
2. When Mem R/W button is clicked, the below shown ULK Mem R/W Operation
window will be displayed. This window consists of
a. Address - This is the peripheral address from which data has to be read/written.

(Confidential)
R 2.0
b. Data In case of Read operation, data read from the specified address will be
displayed in this field if no of words to be read is 1. In case of write, we have to fill
this field with the value which has to be written in the pheriperal address.
c. No of Words The number of words of data to be read from the specified address
should be mentioned in this field. Note that we can write only 1 word data in the
peripheral address at a time but we can read any number of words.
d. Mode This field should be set to specify in which mode(32 bit,16 bit,8 bit) data has
to be read/written. The Mode for most of the peripheral is 32 bit.
3. The Mode Field(32,16,8 bit) can be Selected by clicking on the arrow in the Mode
field as shown in figure below.

(Confidential)
R 2.0
1.11.1. Mem Read

1. Enter the peripheral address from which data has to be read. For e g: In our case, address
entered is SD-RAM address 0x83000000 ,No of Words is 1, Mode is 32 Bit. Click
on Read button to read the data as shown in figure below.

(Confidential)
R 2.0
2. Once the Read button is clicked, Data read from the Specified Address will be
displayed in the Data field. For e.g.: In our case data present in the SD-RAM address
0x83000000 is 0xFFFFFFFF as shown in Data field below.

(Confidential)
R 2.0
3. If the User wants to read more words of data from the DDR Address, change the No of
Words Field to the number of words to be read. For eg: In our case No of Words is set
to 10 which indicates that 10 words of data will be read starting from 0x83000000. Click
on Read button to read 10 words of data.

(Confidential)
R 2.0
4. The Data read from the peripheral register address will be displayed as shown in figure
below. If the user wants to save the Read data, Click on Save button .

(Confidential)
R 2.0
5. Once the Save button is clicked, the below shown window will appear. Enter the Name
by which the file has to be saved and also select the directory where the file will be
saved. Click on Save button again.
6. Once the file is saved successfully, the below shown message Log File Saved will be
displayed .

(Confidential)
R 2.0
7. If the user wants to clear the data shown in the text box, Click on Clear button as
shown in figure below.
8. After Clicking on the Clear button, all the data shown in the text boxes will be
displayed as shown in figure below. After Doing all the Mem R/W Operation, Click on
Cancel to enter into main Application page.

(Confidential)
R 2.0
1.11.2. Mem Write

1. Enter the Peripheral register address where the data has to be written in Address field.
Enter the data to be written in the specified address in the Data Field. For eg: In our
case, Data 0x12345678 will be written in the address location 0x83000000.Click on
Write button to write the data in the location 0x83000000 as shown in figure below.

(Confidential)
R 2.0
2. Once the Write button clicked, the below shown warning message will be displayed.
Click on OK button to continue the data writing.
3. Once the data is written successfully in the user mentioned memory address, the below
shown message Write Operation Completed will be displayed as shown in figure
below.

(Confidential)
R 2.0
1.12. Nand Read

This is used to read the data from the Nand Flash.
1. Click on the Nand Read button as shown in figure below.

(Confidential)
R 2.0
2. Once the Nand Read button is clicked, the ULK Flash Read Operation window will
appear as shown in figure below.This windows contains Flash address field which
should contain the address of the Nand flash from which data has to be read, No of
Words field which should contain the no of words of data to be read.

(Confidential)
R 2.0
3. Enter the Flash address from which data has to be read and also enter the number of
words of data to be read. For eg: In our case , Flash Address is 0x00080000 and No of
Words is 1. Click on Read button to read the data as shown in figure below.

(Confidential)
R 2.0
4. Once the read button is clicked, the below shown confirmation message will be
displayed. Click on OK to read the data from the nand flash.
5. The data read from the Nand Flash address will be displayed in the text box as shown in
figure below.User can also save this values in the file for further usage.

(Confidential)
R 2.0
1.13. Reg R/W ARM/DSP

This is used to read and write into all the registers(R0 R12),SP,LR,SPSR and PC. These
registers can be read/written only if the user application has entered in the Debug trap mode by
calling DEBUG_BREAK or DEBUG_BREAK_INTR in the application code.
1. Load the Arm Debug break application binary in the SD_RAM location using Load
button. Once the binary is loaded in the SD-RAM , Run(Execution) the application using
RUN button. While executing the application, once it comes across DEBUG_BREAK/
DEBUG_BREAK_INTR,the Stub Client will enter into the Debug Trap. When the Stub
client is in Debug trap, Stub host can read all the registers(r0 -12 etc). The ULK
Device Status will be updated as Debug Trap. The text box will show at what address
DEBUG_BREAK macro is called as shown in figure below.

(Confidential)
R 2.0
Debug Trap is caused at address 0x82000014

2. Click on Reg R/W ARM/DSP button to read/write into the register values as shown in
figure below. When the Reg R/W ARM/DSP button is clicked, it will automatically
read all the register values and will get displayed. So no need to click on Read Reg
button again.

(Confidential)
R 2.0
3. If the user wants to write in any of the registers, Enter the value in that register field and
select the corresponding check boxes and then Click on Write Reg button to update
the register values.For eg: In our case , value entered in the Reg R0 field is 99 and
corresponding check box is selected. Click on Write Reg button to write into that
register as shown in figure below.

(Confidential)
R 2.0
4. Once the Register is written successfully, the below shown message Register Write
Completed will be displayed as shown in figure below. Click OK. Once all the
read/write operation is done, Click on Cancel button to enter into main window.

(Confidential)
R 2.0
1.14. Banked Reg R/W ARM/DSP

This is used to read and write into all the Banked registers(FIQR8 R12),IRQ SP,IRQ LR,IRQ
SPSR , FIQ SP,FIQ LR and FIQ SPSR . These Banked registers can be read/written only if the
user application has entered in the Debug trap mode by calling DEBUG_BREAK or
DEBUG_BREAK_INTR in the application code.

(Confidential)
R 2.0
1. Stub client has to enter into Debug trap mode as mentioned in (1.13 point 1). Once debug
trap is entered, Click on Banked Reg R/W ARM/DSP button to read all the banked
register values as shown in figure below.
2. When the Banked Reg R/W ARM/DSP button is clicked, it will read all the register
values and will be displayed. No need to click on Read Reg button again as shown in
figure below.

(Confidential)
R 2.0
3. If the user wants to write in any of the registers, Enter the value in that register field and
select the corresponding check boxes and then Click on Write Reg button to update
the register values. For e.g.: In our case , value entered in the FIQR8 field is 12345678
and corresponding check box is selected. Click on Write Reg button to write into that
register as shown in figure below.

(Confidential)
R 2.0
4. Once the Banked Register is written successfully, the below shown message Register
Write Completed will be displayed as shown in figure below. Click OK. Once all
the read/write operation is done, Click on Cancel button to enter into main window.

(Confidential)
R 2.0
1.15. Flash
This is used to program the X-Loader,U-Boot, U-Image, Root file system,FPGA, General file in
the Nand Flash individually.

(Confidential)
R 2.0
1. Click on Flash button to program the X-Loader,U-Boot, U-Image, Root file

system,FPGA, General file in the Nand Flash Individually as shown in figure below.
2. Once the Flash button is clicked, the below shown ULK Flash Operation window will
be displayed .

(Confidential)
R 2.0
3. User has to select the Component(X-Loader,U-Boot,U-Image,Root file

system,FPGA,General) from the Component field which has to be flashed. Click to
Select Component.. to select the Component which has to be programmed in NAND
Flash as shown in figure below. Note the NAND Flash Programming address is fixed for
X-Loader, U-Boot, Linux Image , Root File System and FPGA component. User Can
program any other file in any NAND Flash location by selecting General component.

(Confidential)
R 2.0
1.15.1. Flashing X Loader

1. Select the X Loader component in the Component field, Select the X Loader file
in the File Name field using Browse button which has to be programmed in NAND
Flash. Note that X Loader file with the extension .bin.ift has to be selected. If any
other file with different extension is selected, it will display error message. The X-Loader
will be first loaded in the SD-RAM location 0x82000000 when Load button is clicked
and can then be programmed in the fixed NAND Flash location 0x00000000 when
Flash button is clicked . Once the File and X Loader component is selected, Click on
Load button. The memory space allocated for X Loader is 512 KB starting from
0x00000000 (i.e from 0x00000000 0x00080000).

(Confidential)
R 2.0
2. Once the Load button is clicked, the below shown ULK Warning message will be
displayed. Click on OK to continue the Load operation.
3. Once the X-Loader File is successfully loaded in the SD RAM location , the below
shown success message will be displayed.Click on OK.

(Confidential)
R 2.0
4. Once the X Loader file is successfully loaded, Click on Flash button to program the XLoader in the NAND Flash as shown in figure below.
5. Once the Flash button is clicked, the below shown ULK Warning message will be
displayed. Click on OK to continue the NAND Flash Programming.

(Confidential)
R 2.0
6. Once the X Loader is successfully programmed in NAND Flash, the below shown
Success message X Loader Successfully Flashed will be displayed . Click OK.
1.15.2. Flashing U Boot

1. Select the U Boot component in the Component field as shown in figure below.

(Confidential)
R 2.0
2. Select the U Boot file in the File Name field using Browse button which has to be
programmed in NAND Flash. Note that U Boot file with the extension .bin has to be
selected. If any other file with different extension is selected, it will display error
message. The U Boot will be first loaded in the SD-RAM location 0x82000000 when
Load button is clicked and can then be programmed in the fixed NAND Flash location
0x00080000 when Flash button is clicked . Once the File and U Boot component is
selected, Click on Load button as shown in figure below. The memory space allocated
for U BOOT is 2 MB starting from 0x00080000 (i.e from 0x00080000 0x00280000).

(Confidential)
R 2.0
4. Once the U Boot File is successfully loaded in the SD RAM location , the below shown
success message will be displayed. Click on OK.

(Confidential)
R 2.0
5. Once the U Boot file is successfully loaded, Click on Flash button to program the U
Boot in the NAND Flash as shown in figure below.

(Confidential)
R 2.0
7. Once the U Boot is successfully programmed in NAND Flash, the below shown Success
message U BOOT Successfully Flashed will be displayed . Click OK.
1.15.3. Flashing Linux Image

1. Select the Linux Image component in the Component field as shown in figure
below.

(Confidential)
R 2.0
2. Select the Linux Image file in the File Name field using Browse button which has to
be programmed in NAND Flash. The Linux Image will be first loaded in the SD-RAM
location 0x82000000 when Load button is clicked and can then be programmed in the
fixed NAND Flash location 0x00280000 when Flash button is clicked . Once the
File and Linux Image component is selected, Click on Load button as shown in figure
below. The memory space allocated for Linux Image is 4 MB starting from 0x00280000
(i.e from 0x00280000 0x00680000).

(Confidential)
R 2.0
4. Once the Linux Image File is successfully loaded in the SD RAM location , the below
shown success message will be displayed. Click on OK.

(Confidential)
R 2.0
5. Once the Linux Image file is successfully loaded, Click on Flash button to program the
Linux Image in the NAND Flash as shown in figure below.

(Confidential)
R 2.0
7. Once the Linux Image is successfully programmed in NAND Flash, the below shown
Success message Z Image Successfully Flashed will be displayed . Click OK.
1.15.4. Flashing Root File System

1. Select the Root File System component in the Component field as shown in figure
below.

(Confidential)
R 2.0
2. Select the Root File System file in the File Name field using Browse button which has
to be programmed in NAND Flash. Note that Root File system file with the extension
.gz has to be selected. If any other file with different extension is selected, it will
display error message. The Root File System will be first loaded in the SD-RAM
location 0x82000000 when Load button is clicked and can then be programmed in the
fixed NAND Flash location 0x00680000 when Flash button is clicked . Once the
File and Root File System component is selected, Click on Load button as shown in
figure below. The memory space allocated for Root File System is 10 MB starting from
0x00680000 (i.e from 0x00680000 0x01080000).

(Confidential)
R 2.0
4. Once the Root File System File is successfully loaded in the SD RAM location , the
below shown success message will be displayed. Click on OK.

(Confidential)
R 2.0
5. Once the Root File System file is successfully loaded, Click on Flash button to
program the Root File System in the NAND Flash as shown in figure below.

(Confidential)
R 2.0
7. Once the Root File System is successfully programmed in NAND Flash, the below
shown Success message Initrd Successfully Flashed will be displayed . Click OK.
1.15.5. Flashing FPGA

1. Select the FPGA component in the Component field as shown in figure below.

(Confidential)
R 2.0
2. Select the FPGA file in the File Name field using Browse button which has to be
programmed in NAND Flash. Note that FPGA file with the extension .XSVF has to be
selected. If any other file with different extension is selected, it will display error
message. The FPGA file will be first loaded in the SD-RAM location 0x82000000 when
Load button is clicked and can then be programmed in the fixed NAND Flash location
0x01080000 when Flash button is clicked . Once the File and FPGA component is
for Root File System is 2 MB starting from 0x01080000 (i.e from 0x01080000
0x01280000).

(Confidential)
R 2.0
4. Once the FPGA File is successfully loaded in the SD RAM location , the below shown

(Confidential)
R 2.0
5. Once the FPGA file is successfully loaded, Click on Flash button to program the
FPGA file in the NAND Flash as shown in figure below.

(Confidential)
R 2.0
7. Once the FPGA file is successfully programmed in NAND Flash, the below shown
Success message FPGA Successfully Flashed will be displayed . Click OK.
1.15.6.
Flashing General
This is used to program any user file in the NAND Flash.

1. Select the General component in the Component field as shown in figure below.

(Confidential)
R 2.0
2. Select the user file in the File Name field using Browse button which has to be
programmed in NAND Flash. Note that user file with any extension/no extension can be
programmed in the NAND Flash. Enter the NAND Flash Location where the user file has
to be download in Address field. For eg: In our case , address entered is
0x030a0000 .The user file will be first loaded in the SD-RAM location 0x82000000
when Load button is clicked and can then be programmed in any NAND Flash
location when Flash button is clicked . Once the File and General component is
for User is 79.375 MB starting from 0x030A0000 (i.e from 0x030A0000 0x08000000).

(Confidential)
R 2.0
4. Once the User File is successfully loaded in the SD RAM location , the below shown
5. Once the User file is successfully loaded, Click on Flash button to program the user
file in the NAND Flash as shown in figure below.

(Confidential)
R 2.0
7. Once the User file is successfully programmed in NAND Flash, the below shown Success
message File Successfully Flashed to general area of nand flash will be displayed .
Click OK.

(Confidential)
R 2.0
1.16. Flash Release

This is used to program the final Released binary into the Nand Flash. The Final released binary
consists of X-Loader + U-Boot + U-Image.
1. Click on the Flash Release button to program the Final released binary in the Nand
Flash as shown in figure below.

(Confidential)
R 2.0
2. When the Flash Release button is clicked, the below shown ULK Flash Release
Operation window will be displayed as shown in figure below.

(Confidential)
R 2.0
3. Select the final released binary filename by using browse button and click Load as
shown in figure below. When the Load button is clicked, the Final release binary will
be downloaded in the SD-RAM location which can then be programmed in Nand Flash.

(Confidential)
R 2.0
4. Once the Load button is clicked, the below shown confirmation message will be
displayed. Click OK to continue the loading process. It will take 3 5 minutes to load
the final released binary in the SD-RAM.
5. Once the Final released binary is successfully loaded, the below shown message File
Successfully Sent to Stub Client will be displayed.

(Confidential)
R 2.0
6. Once the final released binary is loaded in SD- RAM, it can be then programmed in
NAND Flash. Click on Flash button to program into the NAND Flash as shown in
figure below.
7. Once the Flash button is clicked, the below shown confirmation message will be
displayed. Click on OK to program the final released binary from SD_RAM to NAND
Flash.

(Confidential)
R 2.0
8. After the Final released binary is programmed successfully in the NAND Flash, the
below shown message Nand Flash Successfully Updated will be displayed. Click on
OK.
1.17. Advanced
This is used to set the IP-Address of the Stub client either statically or dynamically and also to
program the ARM and FPGA applications in the boot modes.
1. Click on Advanced button as shown in figure below.

(Confidential)
R 2.0
1.17.1. General options

This is used to set the IP-Address of the Stub Client either statically or dynamically.

(Confidential)
R 2.0
1. When the Advanced button is clicked, the below shown Window will be displayed.
Make sure that General tab is selected.
2. If the user want to set Static IP-Address for the Client Stub, Enter the IPAddress to
be set in the Static IP Address field and select the Static radio button. For eg: In
our case IP-Address is set to 192.168.2.80 . Click on Save button to save the IPAddress as shown in figure below.

(Confidential)
R 2.0
3. Once the Save button is clicked, the below shown confirmation message will be
displayed .Click on OK to save the Static IP-Address.
4. After the Static IP-Address is set successfully, the below shown message Boot
Mode set to Static!! will be displayed.

(Confidential)
R 2.0
5. If the user want to set the IP-Address Dynamically(DHCP),select the DHCP radio
button and click on Save button as shown in figure below.
6. Once the Save button is clicked, the below shown confirmation message will be
displayed. Click on OK to take the IP_Address from DHCP.
7. After the DHCP Boot Mode is set successfully, the below shown success message
Boot Mode set to DHCP!! will be displayed.

(Confidential)
R 2.0
8. To Set all the Subnets for scanning the ULK / ULK Naming, select the All Subnets
radio button and click on Save button as shown in figure below.
9. Once the Subnets configuration is successful, the below shown success message will
be displayed.

(Confidential)
R 2.0
10. To Set the Default Subnet for scanning the ULK / ULK Naming, select the Default
radio button and click on Save button as shown in figure below.
11. Once the Subnets configuration is successful, the below shown success message will
be displayed.

(Confidential)
R 2.0
1.17.2. Boot Modes Option

This is used to program the ARM and FPGA applications in the NAND flash which can be
executed anytime Depending on the Dip Switch setting on the target board. There are totally 5
boot modes(2- 6).
1. Select the Boot Modes tab in the Advanced window. When the Boot Modes tab is
selected, the below shown window will be displayed.

(Confidential)
R 2.0
2. The ARM and FPGA applications can be programmed in different boot modes. To select
the boot mode in which application can be programmed, Click on the Select Boot
Mode and select the Boot Mode where the application binary will be programmed.
There are 5 Boot Modes(Boot Mode 0x02 Boot Mode 0x06) as shown in figure below.

(Confidential)
R 2.0
3. To program the ARM/ FPGA application binary in the Boot Mode 0x02, select Boot
Mode 0x02 from the Select Boot Mode list down menu. The Boot Mode Usage
field will tell currently which application is programmed in Boot Mode 0x02.Since
initially there is no application programmed in the Boot Mode 0x02, it will display
Inactive.. as shown in figure below. The Current Operation field will tell the
current operation status. Since now no operation is going on, it will display Idle. ..
4. Select the ARM application binary by using browse button in the ARM field and also
select the Check box. Select the FPGA application binary by using browse button in the
FPGA field and also select the Check box. Click on Set Boot Mode button to
program the ARM/FPGA application binary in the NAND flash. Note that only

(Confidential)
R 2.0
ARM/FPGA can also be programmed in NAND Flash. No compulsory to program both.

Support for DSP download is not provided.
5. Once the Set Boot Mode button is clicked, the below shown confirmation message will
be displayed. Click on OK to continue the programming.

(Confidential)
R 2.0
6. The current programming operation will be displayed in the Current Opertion field as
7. Once the programming is done successfully, the below shown success message will be
displayed.
8. Once the programming is done, cancel the current window and re-enter again in the same
window by selecting Advanced->Boot Modes->Boot Mode 0x02. Since
previously we had downloaded ARM and FPGA application, it will show in the Boot

(Confidential)
R 2.0
Mode Usage as ARM and FPGA applications is currently programmed in Boot Mode
0x02 as shown in figure below.
1.18. Send
This is used to send the hex value or string from Stub Host to the Stub Client. When the Stub
Client executes ulk_scanf_hex/ulk_scanf_string, the stub client enters in the receive mode
waiting for the data from the Stub Host.
1. When the Stub Client enters in the hex value receive mode(via ulk_scanf_hex), one
message will be displayed in the ULK Device Status as Console Scan Hex
which mean that Stub client is waiting for hex value from Stub Host as shown in figure
below.

(Confidential)
R 2.0
2. Once the Stub Client is Waiting for hex Data from the Stub Host, Enter the hex data in
Enter Scanf Data field and click on send button. For eg: In our case data entered is
7as shown in figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
3. When the Stub Client enters in the String receive mode(via ulk_scanf_string), one
message will be displayed in the ULK Device Status as Console Scan String
which mean that Stub client is waiting for Character or a string from Stub Host as shown
in figure below.

(Confidential)
R 2.0
4. Once the Stub Client is Waiting for Char/String Data from the Stub Host, Enter the
Character/string data in Enter Scanf Data field and click on send button. For eg:
In our case data entered is n as shown in figure below.

(Confidential)
R 2.0
1.19. Save Log

This is used to save the Log message in the text file.
1. Click on Save Log button to save the log messages as shown in figure below.

(Confidential)
R 2.0
2. Once the Save Log button is clicked, the below shown window will be displayed.
Enter the file name to be saves in Name field and also the directory path in Save in
folder field as shown in figure below.
3. Once the Log file is saved successfully, the below shown window will be displayed.Click
on OK.
1.20. STOP
This is used to stop the Stub Client scanning process.
1. If the user want to stop the Stub Client scanning process(List ULK/Find ULK/List
Unnamed) , Click on Stop button as shown in figure below.

(Confidential)
R 2.0
2. Once the stop button is clicked , the below shown message will be displayed.

(Confidential)
R 2.0

(Confidential)
R 2.0
2. Stub Control Panel APIs

2.1.ulk_printf
Syntax:
uint8 ulk_printf (const char *fmt, ...)
Input parameter:
const char *fmt String of characters
Description:
This is used to display the Debug message(prints) on the Serial console.
Return Value:
Always 0.
Example:
ulk_printf( This string will be displayed on serial console \n);
2.2.ulk_cpanel_printf
Syntax:
void ulk_cpanel_printf (const char *fmt, ...)
Input parameter:
const char *fmt String of characters
Description:
This is used to display the Debug message(prints) on the Control panel console and Serial
console.
Return Value:
NONE.
Example:

(Confidential)
R 2.0
ulk_cpanel_printf( This string will be displayed on Control panel console and serial
console \n);
2.3.ulk_scanf_hex
Syntax:
void ulk_scanf_hex (unsigned long *hex_variable)
Input parameter:
unsigned long *hex_variable Hex Value.
Description:
This is used to Scan a hex value from the ULK control panel(Stub host) and sent to the Stub
Client.
Return Value:
NONE.
Example:
unsigned long a = 0;
ulk_scanf_hex (&a);
2.4.ulk_scanf_string
Syntax:
void ulk_scanf_string (char* user_string)
Input parameter:
char* user_string a character or a string .
Description:
This is used to Scan a character or a string from the Ulk control panel(Stub host) and sent to
the Stub Client.

(Confidential)
R 2.0
Return Value: None

Example:
char user_string[100];
ulk_scanf_string (&user_string[0]);
2.5.DEBUG_BREAK
This should be called inside main function where the user wants to Debug the application
by
reading/writing in the registers(r0 r12, LR,Pc etc).
Example:
DEBUG_BREAK;
2.6.DEBUG_BREAK_INTR
This should be called inside Interrupt /fast interrupt ISR function where the user wants to
Debug the application by reading/writing in the registers(r0 r12, LR,Pc etc).
Example:
DEBUG_BREAK_INTR;

(Confidential)
R 2.0
3. Procedure to create and compile Eclipse Application

3.1.Procedure to Launch Eclipse Tool
1. Click on the Eclipse icon from the desktop to launch the Eclipse. Eclipse will start
launching as shown in figure below.
2. It will ask for the workspace where projects has to be saved. By default it will save in
/home/test/workspace. If the user wants to save the projects in some other folder,give the
appropriate path and press OK.

(Confidential)
R 2.0
3. Eclipse will start launching as shown in figure below.

(Confidential)
R 2.0
4. Once the Eclipse is launched, the below shown window will be opened. It will have 6
sample applications as shown in below figure.

(Confidential)
R 2.0

(Confidential)
R 2.0
3.2. Procedure to Create a new C project:

1. Click on File ->New -> C Project to create a new C Project as shown in figure below.

(Confidential)
R 2.0
2. Enter the Name of the project to be created in the Project name Field , for eg: test
as shown in figure below. Make sure that Toolchains is selected as Linux GCC and
then press Next> button

(Confidential)
R 2.0
3. The Below screen will appear when next button is clicked. Make sure that Default
button is selected. Press Finish button.

(Confidential)
R 2.0

(Confidential)
R 2.0
4. The new C project will be created and will be added to the Project Explorer tab as
Newly Created Project(test)

(Confidential)
R 2.0
5. Right Click on the newly created project(test) and then select New -> File as shown in
figure below.

(Confidential)
R 2.0
6. Write the File name as project.lds in the File name Field and click on Finish.

(Confidential)
R 2.0

(Confidential)
R 2.0
7. Copy the below patch of code into the newly created file project.lds as shown in
figure below.
OUTPUT_FORMAT("elf32-littlearm", "elf32-littlearm", "elf32littlearm")
OUTPUT_ARCH(arm)
ENTRY(main)
MEMORY
{
ram
: o = 0x82000000, l = 30k
usrstack : o = 0x82007800, l = 20k
}
SECTIONS
{
/* Code and Constants */
.text :
{
. = 0x00;
__text_start = .;
*.o(entry)
*.o(.text)
*.o(.strings)
*.o(.rodata)
*.o(.rodata.*)
*.o(.comment)
*.o(.debug*)
*(.rodata.*)
*(.rodata)
*(.eh_frame)
. = ALIGN(32);
__text_end = .;
} > ram
/* Initialized data */
.init :
{
. = ALIGN(32);
__data_start = .;

(Confidential)
R 2.0
. = ALIGN(32);
/* nk.o(.data)*/
*(.data)
*(.glue_7)
*(.glue_7t)
. = ALIGN(32);
__data_end = .;
. = ALIGN(32);
} > ram
.bss :
{
__bss_start = .;
*(.bss)
*(COMMON)
. = ALIGN(32);
__bss_end = .;
} > ram
/* Application stack */
.stack :
{
__stack_start = .;
*(.stack)
__stack_end = .;
. = ALIGN(32);
} > usrstack
}

(Confidential)
R 2.0

(Confidential)
R 2.0
8. Right Click on the newly created project(test) and then select New -> Header File as

(Confidential)
R 2.0
9. Write the Header file name as macros.h and press Finish as shown in figure below.

(Confidential)
R 2.0
10. Copy the below patch of code into the newly created file macros.h as shown in figure
below.
/* Use PROGRAM_ENTRY to make the entry function (first function
to be executed)
* to come in "entry" section. The "entry" section is mapped to
the initial
* section of lds file
* .text :
* {
*
__text_start = .;
*
*.o(entry)
*
*.o(.text)
*
*/
#define PROGRAM_ENTRY __attribute__ ((section("entry")))
#define DEBUG_BREAK { \
__asm (" STMFD
sp!, {r14} "); \
__asm (" swi #0x10 "); \
__asm (" LDMFD
sp!, {r14} "); \
}
#define DEBUG_BREAK_INTR { \
__asm (" swi #0x10 "); \
}

(Confidential)
R 2.0

(Confidential)
R 2.0
11. Right Click on the newly created project(test) and then select New -> Source File as

(Confidential)
R 2.0
12. Write the Source file name as main.c and press Finish as shown in figure below.

(Confidential)
R 2.0
13. Before writing any application code, user have to add the below patch to their main file.
Only after adding this 3 lines, created application will work properly.
#include "macros.h"
#include <ulk.h>
int main(void) PROGRAM_ENTRY;
Note that user can write code inside this file but the above 3 lines should be included in
this main file.

(Confidential)
R 2.0
14. Right Click on the newly created project(test) and then select New -> File as shown in
figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
15. Write the file name as Makefile and press Finish as shown in figure below.

(Confidential)
R 2.0
16. Copy the below patch of code into the newly created file Makefile as shown in figure
below.
CROSS_COMPILE=/ulk/toolchain/CodeSourcery/Sourcery_G+
+_Lite/bin/arm-none-linux-gnueabiINCL = /usr/include/ulk
TOOLCHAIN=gcc
OUTFILE_SDRAM=test
AS=$(CROSS_COMPILE)as
CC=$(CROSS_COMPILE)gcc
LD=$(CROSS_COMPILE)ld
NM= $(CROSS_COMPILE)nm
SIZE=$(CROSS_COMPILE)size
OBJCOPY=$(CROSS_COMPILE)objcopy
OBJDUMP=$(CROSS_COMPILE)objdump
CCFLAGS=-I$(INCL) -c -O3 -Wall -mcpu=arm9
LIBS_PATH1=/ulk/toolchain/CodeSourcery/Sourcery_G+
+_Lite/lib/gcc/arm-none-linux-gnueabi/4.2.1
LIBS_PATH2=/usr/lib
LIBS = -L$(LIBS_PATH2) -lulk -L$(LIBS_PATH1) -lgcc
LDFLAGS+=-T project.lds -Map test.map
OBJS= main.o
rebuild: clean all
all: sdram
sdram: $(OBJS)
$(LD) $(OBJS) $(LDFLAGS) $(LIBS) -Ttext 0x82000000 -n
-O elf32-arm -o $(OUTFILE_SDRAM).elf
$(OBJCOPY) --strip-debug --strip-unneeded $
(OUTFILE_SDRAM).elf -O binary $(OUTFILE_SDRAM).bin

(Confidential)
R 2.0
$(OBJCOPY) $(OUTFILE_SDRAM).elf -O srec $

(OUTFILE_SDRAM).srec
main.o: main.c
$(CC) -c $(CCFLAGS) main.c -o main.o
clean:
rm
rm
rm
rm
-rf
-rf
-rf
-rf
*.bin
*.elf
*.map
*.o
In the Above Contents, the text marked in red color should be the project name (For eg:
in our case project name is test). The text marked in Green color should be the SDRAM Address where the Application has to be Loaded and Run.If this Make address
doesnot match with the address used while loading the Binary(using Load), application
will not work properly.

(Confidential)
R 2.0
NOTE: User has to always create the 3 files project.lds,macros.h and Makefile
when new project is created.

(Confidential)
R 2.0
3.3. Procedure to Compile the C project

1. Right click on the newly created project(test) and click on Clean Project . This will
clean and build the newly created project.

(Confidential)
R 2.0
2. Once the build is succeeded without any error , the below shown screen will be
displayed.

(Confidential)
R 2.0
3. When the project is compiled successfully,it will create a .bin and .srec files. For eg: In
our case, its test.bin and test.srec. Double click on test.bin to see the contents of the
test.bin file as shown in figure below.

(Confidential)
R 2.0
4. Double click on test.srec to see the contents of the test.bin file as shown in figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
5. If the user want to Close the Eclipse Development Tool, Click on X(close Window) in
the top right corner in eclipse window as shown in figure below.

(Confidential)
R 2.0
6. Once the close button is pressed, the below shown confirmation message will be
displayed. Click on OK to close the eclipse tool.

(Confidential)
R 2.0
4. Procedure to Execute and test Sample ULK Applications

4.1. ex_cpanel_print
This is the sample application to show how to print the Debug Message on ULK Control panel.
Main Code:
#include "macros.h"
#include <ulk.h>
int main()
{
ulk_cpanel_printf(" This is a demo application to print the debug
message on Control panel\n");
return 0;
}
1. Detect the Stub Client connected using either of List ULK/ Find Unnamed/Find ULK as
mentioned above in section (1.2/1.3/1.5 ). Once the the Connection is established, Select
the Stub client from Drop down menu list and connect to it as mentioned in section (1.6).
Once the Connection is established, Click on Load button. Select the binary file
ex_cpanel_print.bin from the workspace in the Select File field. Enter
82000000 in the Load Address Field and Click on Load to load the Control panel
print application in the SD-RAM location 0x82000000.Since while creating the
application we have given load address as 0x82000000 in the Makefile,the binary
has to be loaded in 0x82000000 to execute the application properly.

(Confidential)
R 2.0
2. Once Load button is pressed, the below shown Confirmation message will be
displayed. Click OK to continue the loading process.

(Confidential)
R 2.0
3. Once the File is successfully loaded, the below Shown success message will be
displayed. Click OK.
4. Once the Load is successful, Click cancel button in Load window and click on Run
button. Enter the Run Address as 82000000 and click on Execute button.
5. Once Execute button is clicked, Confirmation message will be displayed. Click on

OK to execute.

(Confidential)
R 2.0
6. Once the Application executes, the Debug message written in the Code will be displayed
in the ULK Control panel and pop up message will be displayed telling that Program
Execution is completed as shown in figure below.

(Confidential)
R 2.0
4.2. ex_debug_break
This is the sample application to show how to enter in the Debug Trap Mode in the Client
Stub. This is done for debugging purpose.
Main Code:
#include "macros.h"

(Confidential)
R 2.0

int main ()
{
/* View and Modify Registers using DEBUG_BREAK */
__asm (" MOV r2, #0x55");
__asm (" MOV r3, #0x44");
__asm (" MOV r6, #0x7");
__asm (" MOV r4, #0x53");
DEBUG_BREAK;
__asm (" MOV r4, #0x8");
__asm (" MOV r6, #0x6");
DEBUG_BREAK;
return 0;
}
ex_debug_break.bin from the workspace in the Select File field. Enter

(Confidential)
R 2.0

(Confidential)
R 2.0

OK to execute.

(Confidential)
R 2.0
6. Once the Application executes, the Stub Client enters in the Debug trap mode when it
comes across first DEBUG_BREAK macro . Debug trap address will be shown in text
box (0x82000014), ULK Device Status will be updated as Debug Trap as shown in
figure below.

(Confidential)
R 2.0
7. When Debug Trap mode is entered, user can read all the Register values. Click on Reg
R/W ARM/DSP to read/write the register values.In the Code we are writing the below
data in the registers.
r2 = 0x55 ; r3 = 0x44 ; r6 = 0x7 ; r4 = 0x53 . So when we read the registers, same data
will be displayed.
8. User can also change the register values. As shown in figure below Register R0 is set to
99 and R2 is set to 88. Select the corresponding check boxes and click on Write Reg
as shown in below figure.

(Confidential)
R 2.0
9. Once the register is written successfully, the below shown message will be displayed.
Click OK

(Confidential)
R 2.0
10. Once all the register updates are done, Click on Continue button to continue the
program execution as shown in figure below.

(Confidential)
R 2.0
11. When the Continue button is pressed, the program execution continues and enters
again in Debug trap when it comes across second DEBUG_BREAK macro.Click on
Reg R/W ARM/DSP button to read the register values. After the first debug break, we

(Confidential)
R 2.0
are updating the register value r4 to 8 and r6 to 6. And when we read the registers, same
updated value will be displayed in Second debug break.
12. Click on Continue to continue the program execution. Once Continue button is
clicked, program execution will be completed as shown in figure below.

(Confidential)
R 2.0
4.3.ex_gpio_interrupt
This is the sample application to show how to register the ISR and generate the interrupt When
lab interrupt Switch is pressed.
Main Code:
#include "macros.h"

(Confidential)
R 2.0
#include <ulk.h>
void ulk_gpio_stub_isr(void *pointer);
int main ()
{
unsigned char temp=0;
/* Generation of interrupt through GPIO */
int *interrupt_pointer = (int *)0x80700000;
// for interrupt switch pin
ulk_sys_pad_set_mux_mode( 170, 4);
ulk_gpio_set_dir(170 , 1);
ulk_sys_pad_set_pull(170 , 2);
ulk_sys_pad_set_dir(170 , 1) ;
ulk_gpio_get_data_in(170 , &temp);
ulk_cpanel_printf("press user switch to trigger the interrupt and press
Continue------\n");
ulk_gpio_irq_trig_edge_r( 170, 1);
ulk_gpio_irq_enable_mpu(170,1,(int)&ulk_gpio_stub_isr);
irq_installer (0x22,(unsigned long)&ulk_gpio_stub_isr,interrupt_pointer);
DEBUG_BREAK;
return 0;

(Confidential)
R 2.0
void ulk_gpio_stub_isr(void *pointer)

{
ulk_gpio_irq_clear_mpu(170 );
ulk_cpanel_printf (" Interrupt switch IRQ interrupt Triggered,Pointer is
%lx\n",pointer);
}
ex_gpio_interrupt.bin from the workspace in the Select File field. Enter

(Confidential)
R 2.0

(Confidential)
R 2.0

(Confidential)
R 2.0

OK to execute.
6. Once the Application executes, the Lab GPIO interrupt will be enabled, ISR will be
registered and enters in the debug trap mode as shown in figure below. Now Press the
LAB GPIO Interrupt pin on the target board. When the Stub Client is in Debug trap
mode, interrupts will be disabled. So interrupts will not be generated immediately.

(Confidential)
R 2.0
7. Click on Continue Button to continue the program execution. Once Continue button
is pressed, ISR will be called for the LAB Interrupt pin. The Message inside the ISR is
displayed along with the ISR argument(pointer) as shown in figure below.

(Confidential)
R 2.0
4.4.ex_led
This is the sample application to show how to Scan the user input(hex/string) from the Stub
Host and sent to Stub Client. This also demonstrates the Glowing of the Processor LED.
Main Code:

(Confidential)
R 2.0
#include "macros.h"
#include <ulk.h>
int main ()
{
char user_string[100];
unsigned long a = 0;
/* User input and Display*/
while(1)
{
ulk_cpanel_printf ("Enter the LED number to glow \n");
ulk_scanf_hex (&a);
ulk_cpanel_printf ("Value is %lx\n", a);
ulk_led_config(a-1);
ulk_led_on(a-1,1);
ulk_cpanel_printf ("Do u want to test LED again? Press 'y' or else 'n'
\n");
ulk_scanf_string (&user_string[0]);
ulk_cpanel_printf ("Entered String is %s \n", user_string);
ulk_led_on(a-1,0);
if (user_string[0] == 'n')

(Confidential)
R 2.0
break;
}
return 0;
}
mentioned above in section (1.2/1.3/1.5 ). Once the Connection is established, Select the
Stub client from Drop down menu list and connect to it as mentioned in section (1.6).
ex_led.bin from the workspace in the Select File field. Enter 82000000 in the
Load Address Field and Click on Load to load the Control panel print application in
the SD-RAM location 0x82000000.Since while creating the application we have given
load address as 0x82000000 in the Makefile, the binary has to be loaded in
0x82000000 to execute the application properly.

(Confidential)
R 2.0

(Confidential)
R 2.0

OK to execute.
6. Once the Application executes,it will come across first Hex scanf function. The ULK
Device Status will be updated as Console Scan Hex which means that Client Stub
is waiting for Hex value from the Stub host. The message Enter the LED number to
glow will be displayed in the text box as shown in figure below.

(Confidential)
R 2.0
7. Enter the Led(hex) number which user wants to wants to glow in the Enter Scanf
Data Field . For eg: in our case number entered is 7. Once the number is entered, Click
on Send button to send the data to Stub client as shown in figure below.

(Confidential)
R 2.0
8. Once the Send button is clicked, the 7th pin Led Light will glow. Check on the Board
whether the LED light is glowing properly. The program execution will then come across
String scanf function. The ULK Device Status will be updated as Console Scan
String which means that Stub client is waiting for String data from the Stub Host. If the

(Confidential)
R 2.0
user wants to test more LEDs, press y or if the user wants to end the program
execution, press n in the Enter Scanf Data field as shown in figure below.
9. Once the Send button is clicked with string data as n , program execution will be
terminated as shown in figure below.

(Confidential)
R 2.0
4.5.ex_serial_print
This is the sample application to show how to print the Debug Message on serial console.
Main Code:
#include "macros.h"
#include <ulk.h>
int main()
{
ulk_printf(" This is a demo application to show the debug print over
serial(console)\r\n");
return 0;
}
ex_serial_print.bin from the workspace in the Select File field. Enter 82000000
in the Load Address Field and Click on Load to load the Control panel print
application in the SD-RAM location 0x82000000.Since while creating the application we
have given load address as 0x82000000 in the Makefile,the binary has to be loaded
in 0x82000000 to execute the application properly.

(Confidential)
R 2.0

(Confidential)
R 2.0

OK to execute.

(Confidential)
R 2.0
6. Once the Application executes, the Debug message written in the Code will be displayed
in the Serial console(hyperterminal or minicom) and pop up message will be displayed
telling that Program Execution is completed as shown in figure below.

(Confidential)
R 2.0
4.6.ex_sw_interrupt
This is the sample application to show how to register the software interrupt ISR and
generate the software interrupt.
Main Code:

(Confidential)
R 2.0
#include "macros.h"
#include <ulk.h>
void callback_swi15 (void *pointer);
void callback_swi16 (void *pointer);
int main ()
{
int *interrupt_pointer = (int *)0x80700000;

/* Software Interrupt */
swi_installer (0x15, (unsigned long)&callback_swi15,(void*)
interrupt_pointer);
swi_installer (0x16, (unsigned long)&callback_swi16,(void*)
interrupt_pointer);
__asm ( "swi 0x15 ");
__asm ( "swi 0x16 ");
/* Pop up window with user message */
ulk_cpanel_printf ("Program Execution Completed\n");
return 0;
}

(Confidential)
R 2.0
void callback_swi15 (void *pointer)

{
ulk_cpanel_printf ("SWI 0x15 Interrupt Triggered, Pointer is %lx\n", pointer);
}
void callback_swi16 (void *pointer)
{
ulk_cpanel_printf ("SWI 0x16 Interrupt Triggered, Pointer is %lx\n", pointer);
}
ex_sw_interrupt.bin from the workspace in the Select File field. Enter
82000000 in the Load Address Field and Click on Load to load the software
interrupt application in the SD-RAM location 0x82000000.Since while creating the

(Confidential)
R 2.0

(Confidential)
R 2.0

OK to execute.

(Confidential)
R 2.0
6. Once the Application executes, the registered software ISR will be called. The print
inside the Software interrupt ISR will be displayed along with its argument(pointer) value
as shown in figure below.

(Confidential)
R 2.0

(Confidential)
R 2.0
5. Dip Switch Setting for different Boot Modes

This section describes the Dip Switch setting for different boot modes. After programming the
application in the Particular Boot Mode, User has to set the Dip Switch accordingly to Execute
the Programmed Application binary.
5.1.Boot Mode 2
To Launch the ARM/FPGA application from the Boot Mode 2, the Dip Switch setting in the target
board should be as shown in figure below.

(Confidential)
R 2.0
5.2.Boot Mode 3

(Confidential)
R 2.0
5.3.Boot Mode 4

(Confidential)
R 2.0
5.4.Boot Mode 5

(Confidential)
R 2.0
5.5.Boot Mode 6

(Confidential)
R 2.0

(Confidential)
R 2.0
6.Technical Support
# 7/B, 29th Main,
BTM Layout 2nd Stage,
Bangalore - 560 076
Phone : +91-80-26781643, 26786243, 45
Fax
: +91-80-26685200
Email : emdby@iwavesystems.com
Web : www.iwavesystems.com

(Confidential)

Iw EMDBY UM 01 R1.0 REL2.0 - Stub

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Iw EMDBY UM 01 R1.0 REL2.0 - Stub

Caricato da

Copyright:

Formati disponibili

Stub Control Panel user manual for Mission 10x-Unified Learning Kit

Stub Control Panel user manual for

Mr. Sebikumar Kuruvilla

Mr. Abdullah Khan

iWave Systems Tech. Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

Document Revision History

iWave Systems Technologies Pvt. Ltd.

PROCEDURE TO USE THE ULK CONTROL PANEL.................................................................................6

STUB CONTROL PANEL APIS...................................................................................................................110

iWave Systems Technologies Pvt. Ltd.

PROCEDURE TO CREATE AND COMPILE ECLIPSE APPLICATION..............................................113

DIP SWITCH SETTING FOR DIFFERENT BOOT MODES...................................................................180

PROCEDURE TO LAUNCH ECLIPSE TOOL....................................................................................................113

PROCEDURE TO EXECUTE AND TEST SAMPLE ULK APPLICATIONS.........................................143

BOOT MODE 2............................................................................................................................................180

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

User Manual for ULK Control Panel

iWave Systems Technologies Pvt. Ltd.

1. Procedure to use the ULK Control Panel

1.1. Launching ULK Control Panel

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

1.2. LIST ULK Button

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

3. Click on the List ULK Button as shown in figure below.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

List Down Menu

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

1.3. List UnNamed

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

1.4. ULK Naming

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

1.5. Find ULK

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

2. If the Connection is successful, the below Shown ULK information Connection

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.

1. Click on Load button as shown in figure below..

iWave Systems Technologies Pvt. Ltd.

1.8.1. ARM Binary Download

iWave Systems Technologies Pvt. Ltd.

iWave Systems Technologies Pvt. Ltd.