Scribd
Upload
112 views

Ride Intro

The document provides an introduction and overview of the RIDE integrated development environment (IDE) software. It describes that RIDE is designed for developing 8051 projects and includes tools like an assembler, compiler, linker, simulator, and debugger. It then outlines the basic process for building a new project in RIDE, including creating and adding source files. Debugging tools and features are also summarized, such as setting breakpoints, watchpoints, and using the peripheral status view.

Uploaded by

sakthikothandapani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
112 views

Ride Intro

The document provides an introduction and overview of the RIDE integrated development environment (IDE) software. It describes that RIDE is designed for developing 8051 projects and includes tools like an assembler, compiler, linker, simulator, and debugger. It then outlines the basic process for building a new project in RIDE, including creating and adding source files. Debugging tools and features are also summarized, such as setting breakpoints, watchpoints, and using the peripheral status view.

Uploaded by

sakthikothandapani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Introduction to RIDE

The Raisonance integrated development


environment (Ride7) is designed to
develop 80C51 projects.
It provides the tools necessary to build
8051-based projects:
Compile chain (Assembler, C compiler
and linker) for building applications.
Software simulator for validating
applications.
Hardware debugger for debugging with
the RLink USB dongle.
Tools overview

Build Process

Build a new project
Starting Ride7 Select Start | Programs | Raisonance
Tools | Ride7.
Click on the Project tab in the Ride7 menu.
In the drop down menu, click on New Project.
To create the settings:
1. Select application Type.
2. Select the type of Processor
3. Create a project Name
4. Select a directory Location
5. Select the radio button Create a new project.
6. Press Finish.
7. The Ride7 window appears.
Create and add a source file
To save the source file:
Choose File | Save. A standard Save As window
will open.
Enter <<filename>> into the Filename field.
Click on Save.
To add the file to the project:
Right click on test.prj in the Project window.
Select Add I Item
Select main.obj in the File Open window.
Click on Open.
Debugger
1. Make: Build the project (F9)
2. Cancel Make: Stop building the project
3. Start debug session (Ctrl D)
4. Stop debug session (Shift + Ctrl D)
5. Run debug (Ctrl F9)
6. Pause debug
7. Reset: Press this button to reset the application. (Ctrl F2)
8. Step into: On a function call in a line of the C source code, this
button steps into the called function. If it is not a function call, it
goes to the next line in the source code. (F7)
9. Step over: This button steps over a function call in a line of the C
source code. (F8)
10. Step out Exit functions (Shift + F7)
11. Run to (Cntrl Q)
12. Toggle breakpoint (F5)
13. Clear all breakpoints
Typical RIDE7 window
The Ride7 window looks like the following:
towers.c: The source file as edited in C language or in assembly language.
The Code window that shows you the instruction to be executed by the
simulator.
Disassembly View: This shows an image of the code in the Flash memory of
the target.
Debug peripheral tree.
Project options window: Application and Advanced Options.
Debug Output.
Toolbar which allows the user to control the simulation. (more information in
the next section)
The following columns are available in the Code window -(Disassembly
view):
Address: The address where the instruction is located.
Symbol: The name of the symbol, if a symbol is located at this address.
Code: The byte-code located at this address.
Mnemonic: The mnemonic corresponding to the byte-code.
Code Coverage: The number of times the byte-code at this address has been
executed.

Watchpoints
Watchpoints display variable values permanently on
the screen. To create one you must add the variable to
the Watch window.
1. Open the Watch window by choosing View | Watch.
2. With the pointer over the Watch window press the
right mouse button.
3. Choose Add from the menu that pops up.
4. Enter the variable into the expression field and click
on OK
The Watch window will now show the current value of
the variable in decimal, with the hexadecimal
equivalent in parentheses.
If you click on the GO button to run to the next
breakpoint, the value of variable turns red to indicate
that it has changed.
Peripheral status view
Example, to simulate Port A (PA),
double click on the PA icon in the
Debug peripherals tree.
A PORT A view appears which
shows the state of each pin of the
port and lets you modify the
registers:
Green indicates a value of one and
red a value of zero.
By clicking on the LED it is possible
to connect each pin of the port to
a Net, to VCC, the Ground or no
connection.
Break points
Code view
In the code view, first select the line on which you want
to stop. The line becomes grey:
Then click on the Toggle Breakpoint button and the
line becomes red:
This means that a breakpoint has been set on this line.
The application stops running when this line is reached
and the line turns pink.
Source view
You can use the same procedure to set a breakpoint on
a line of source code, or you can click on the
pink square in the margin next to the instruction.

You might also like