The eCos Tests Prentice.Hall – Embedded.Software.Development.with.eCos
12.7 Simulators
The eCos framework provides simulators for several different processor architectures, including the Hitachi H8300, MIPS, Matsushita AM3x, PowerPC, and SPARClite. A simulator can be useful when a development board is not available, or possibly too costly, and the hardware has not been developed. In these cases, the software can be developed for the target processor and run on a simulator target. The simulators are run from the GNU debugger GDB, either using the Insight GUI or from the GDB command line. To invoke the PowerPC-based GNU debugger you run the executable powerpc-eabi-gdb.exe. Figure 12.14 Configuration Tool Run Tests dialog box. 312 Chapter 12 • An Example Application Using eCos First, let’s see how to run code on the simulator using Insight. When running Insight GDB, select File – Target Settings to bring up the dialog box for connecting to a target, as shown in Figure 12.16. Under the Target drop-down list, select Simulator. Any target-specific options can be entered in the Options edit field within this dialog box. Figure 12.15 Configuration Tool Connection Settings dialog box for running tests on a target system. N O T E The pre-built PowerPC GNU cross-development tools are also included on the CD-ROM in the file ppcgnu- tools.tar.bz2 under the gnu\ppctools directory. You can add the PowerPC GNU cross-development tools by unzipping the file under the root D:\cygwin directory. The files are extracted under the D:\cygwin\toolsppc directory. The command to extract the PowerPC GNU cross-development tools is: tar xjvf cygdriveegnuppctoolsppcgnutools.tar.bz2 You would then need to add the D:\cygwin\toolsppc directory to your path, as shown in Chapter 10 in Section 10.2.2, Installing the Platform-Specific Cross-Development Tools, in STEP 4. The PowerPC GNU cross-development tools are used in Chapter 13.Parts
» Prentice.Hall – Embedded.Software.Development.with.eCos
» Where It All Started—Cygnus Solutions
» The eCos Configuration Method
» eCos Core Components The Origins of eCos
» Processor and Evaluation Platform Support
» eCos Support The Origins of eCos
» Component Framework eCos Terminology
» Component Repository eCos Terminology
» Configuration Options eCos Terminology
» Components and Packages Targets
» Summary Prentice.Hall – Embedded.Software.Development.with.eCos
» The Example HAL Function Call Trace
» Next, the Example HAL Function Call Trace
» Finally, the platform reset routine uses the architecture macros defined in
» HAL Macro Definitions Overview
» Common Configuration Components HAL Configuration
» Architecture-Specific Configuration Components HAL Configuration
» HAL and Kernel Exception Handling
» Application Exception Handling Exceptions
» Interrupt and Scheduler Synchronization
» Interrupt Service Routine Management
» Interrupt State Management Interrupt Control
» Interrupt Controller Management Interrupt Control
» Summary Summary Prentice.Hall – Embedded.Software.Development.with.eCos
» Virtual Vector Configuration Virtual Vectors
» Communication Channels Virtual Vector Table Initialization
» Kernel Directory Structure The Kernel
» Multilevel Queue Scheduler The Scheduler
» Bitmap Scheduler Priority Levels
» Scheduler Configuration The Scheduler
» Thread Stacks and Stack Sizes
» Condition Variables Synchronization Mechanisms
» Message Boxes Synchronization Mechanisms
» Counters Counters, Clocks, Alarms, and Timers
» Clocks Alarms Counters, Clocks, Alarms, and Timers
» Timers Counters, Clocks, Alarms, and Timers
» Asserts and Tracing Prentice.Hall – Embedded.Software.Development.with.eCos
» IO Sub-System IO Control System
» Device Drivers IO Control System
» ROM File System File Systems
» RAM File System File Systems
» USB Support Prentice.Hall – Embedded.Software.Development.with.eCos
» OpenBSD FreeBSD Networking Support
» Networking Threads Networking Support
» Networking Configuration Networking Support
» Networking Tests Networking Support
» DNS Support Networking Support
» SNMP Support Prentice.Hall – Embedded.Software.Development.with.eCos
» The GoAhead Embedded WebServer
» Symmetric Multi-Processing Support Prentice.Hall – Embedded.Software.Development.with.eCos
» Additional Features Prentice.Hall – Embedded.Software.Development.with.eCos
» Overview Prentice.Hall – Embedded.Software.Development.with.eCos
» RedBoot Directory Structure Prentice.Hall – Embedded.Software.Development.with.eCos
» RedBoot Configuration Installation and Configuration
» Boot Scripting RedBoot Commands
» Cygwin Tools Directory Structure
» Installing the Platform-Specific Cross-Development Tools
» Installing WinCVS Accessing the Online eCos Source Code Repository
» Setting WinCVS Preferences Accessing the Online eCos Source Code Repository
» WinCVS Update Commands Accessing the Online eCos Source Code Repository
» Package Directory Structure Packages
» CDL Script Files The Component Definition Language Overview
» Saving Configurations Screen Layout
» Importing and Exporting Configurations
» Configuration Window Screen Layout
» Conflicts Window Screen Layout
» Properties Window Screen Layout
» Short Description Window Screen Layout
» Memory Layout Window Screen Layout
» Memory Layout Manipulation Screen Layout
» eCos Repository Database The Configuration Tool
» Graphical Representation of CDL Script Files
» Conflicts and Resolutions Using Templates
» The Package Administration Tool
» The Command-Line Configuration Tool
» Source-Navigator Additional Open-Source Tools
» Splint Additional Open-Source Tools
» A Closer Look The eCos Build Process
» Development Hardware Setup Examples Overview
» Building the Application Application
» Loading the Application Application
» Using the GDB Command-Line Interface
» The eCos Tests Prentice.Hall – Embedded.Software.Development.with.eCos
» Simulators Prentice.Hall – Embedded.Software.Development.with.eCos
» Overview of Porting Prentice.Hall – Embedded.Software.Development.with.eCos
Show more