|
Please note that in this page RIDE will reference to RIDE6 software which supports 8051, XA and other derivates.
For ARM, ST7 and STM8 family the software is RIDE7.
RIDE is a fully featured Integrated Development Environment (IDE) that provides
seamless integration and easy access to all the development tools.
From editing to compiling, linking, debugging and back to the start, with
a Simulator, ICE, Rom Monitor or other debugging tools, RIDE
conveniently manages all aspects of the Embedded Systems
development with a single user interface.
|
 |
Multi-file Editor
|
|
RIDE is based on a fast multi-document editor designed to meet
the specific needs of programming. The various methods,
menus, commands, and shortcuts are all fully compliant with the
Microsoft® specifications for Windows 2000, XP and NT. Classic
commands, such as string search and block action are integrated.
Advanced features such as Matching Delimiter (parenthesis, brackets), Grep
(multi-file search) and Indenter are integrated as well.
|
The customizable
color-highlighting feature is very useful to
indicate specific syntactic elements as they appear in the source
file: keywords, comments, identifiers, operators, and so on.
The color-highlighting feature is automatically keyed to the intrinsic file type (which
means, it works differently for C and assembler)
This permits the user to identify quickly and easily those parts
of the code responsible for syntax errors.
|
|
|
Project Manager
|
| The project manager creates
links between the various files that includes a project and the
tools necessary to create that project. A project is dedicated to
a particular target: 8051, XA, or other microcontrollers. |
The linker manages object
and library files, and output format conversion as necessary. |
|
|
Tree-structured projects
ease the management of the most complex applications (bank switching,
flash, multi-processor, multi-module...). The 'Project | Make'
command directs the integrated "make" utility to build
or rebuild the target programs for the current project.
To avoid wasting time, each source file will be translated by its
associated tool only if any of its dependencies are found to be
out of date. |
Dependency analysis, even
directly or indirectly included files, are automatic.
Options can be defined as global (for all the files) or as local
(for a specific node or file). Individual attributes can be set
for any file in the project. Similarities between the different
tools make migration from one processor family to another immediate
and easy, permitting multi-processor projects. |
|
|
The Message Window and the On-line Help
|
|
The message window displays all warning, error, and progress
messages generated during the processing of files associated with
each project.
Clicking on an error string in the message window automatically
positions the cursor at the point of that error in the source
code window.
|
The Online help system
is context-sensitive and provides information on nearly all aspects
of RIDE. A specific help file is supplied with each tool driven
by the IDE ('C' Compiler, Assembler, Linker, RTOS). Online menu hints appear
on the status line whenever you select a menu command.
|
|
|
|
|
The Script Language
|
| Most RIDE commands can be run from
a script file. Scripts are written in a C-like language, and are interpreted
at execution time. With the script language, most repetitive tasks can be done
automatically thus speeding up operations and reducing the probability of errors. |
Scripts are very useful for Hardware Testing
(board, emulator) and to initialize the system to a known status, but can also be
conveniently used for other tasks such as creating very complex breakpoints
or redirecting some output to a file to run a 'batch' debug session. |
|
|
Context Saving
|
| When a project is closed,
the whole associated context is saved (open file list, window size
and position etc..). |
Settings associated with
the debugger are also saves such as breakpoints, watches etc... |
|
|
Integrated High-level Debug
|
|
RIDE provides a fully integrated source-level debugging environment.
All information necessary is derived from the translators used
to accomplish each step of the process. This includes mundane
aspects such as "path names", and source code specific
information such as details of complex data types.
With the simple click of a mouse button, the user
can select among several powerful capabilities: simulate, monitor,
or emulate. The fast smooth integration
|
given by RIDE promotes
a feeling of familiarity and ease of use, while providing a level
of comfort and efficiency that reduces the most difficult and complex
applications to tasks that are easily managed. This seamless progression
of the "code-translate-link-debug-test" cycle is the result
of perfect communication between the programming tools and the debugger.
This is the heart of RIDE. |
|
|
|
|
|
| RIDE includes simulation
engines for most 8051, and XA derivatives. The simulator/debugger
is cleanly integrated into the presentation Windows. A wide range
of 'views' can be selected to provide flexible direct examination
of all memory spaces as well the all internal peripherals. |
The simulation engines
perform detailed and faithful simulations (including IDLE or Power
down modes), of all peripherals (including interrupt and watchdog
events) present on the selected component. |
Advanced Features
|
|
RIDE provides a rich variety of 'views' into an application.
These views or windows are associated with control commands like
complex breakpoints or high level trace recording.
|
 |
|
|
To get more information on RIDE please email you request to
support@raisonance.com
|
