Wind River Workbench; Wind River GNU Compiler; Wind River Titanium Cloud; Simics; Wind River Helix Cockpit 1. Software Downloads; Other Downloads; Board Support Packages; Current Publication. Device Cloud Agent 1.2 for Intelligent Device Platform XT 3.1. Device Cloud Agent 2.0. Device Cloud Agent 2.1. Trusted Windows (PC) download Wind River Workbench 3.3.1. Virus-free and 100% clean download. Get Wind River Workbench alternative downloads. Wind River Workbench 3.3 Bosch Rexroth is a collection of tools based on the Eclipse framework to develop control based applications and functions in C/C. Workbench offers an end-to-end, open standards-based suite for device software design, development, debugging, test, and management. 3 1 Overview 1.1 Introduction 3 1.2 How This Guide is Organized 3 1.3 Related Documentation 4 1.1 Introduction Welcome to Wind River Workbench By Example for the VxWorks target operating system. The purpose of this guide is to provide real-world examples of accomplishing tasks and solving problems that can occur during daily development.
Contents
- 2 New Project
- 3 Build and Run
To start Wind River Workbench IDE (Integrated DevelopmentEnvironment) select from menu Applications menu → Development → WindRiver Workbench. The following figure will show up asking us tochoose the workspace.
The workspace is the place, where your projects will be stored. It isrecommended to place workspace under your home directory (/home/<login>under Linux).
Then the main IDE window is opened:
To create a new project right-click in the Project Explorer andchoose New→VxWorks Downloadable Kernel Module Project. (Later, youwill also work with Real-Time Process Projects.) A dialog windowopens, where you can specify the location and name of the project.Continue with the Next button.
In the next dialog window do not make any changes unless you want tocreate your own Makefile. This is not needed right now. Continue withthe Next button.
In the following dialog you can choose the architecture (x86, ARM, …)and the compiler (Diab, GNU). For the first time set Active buildspec to SIMLINUXgnu. It means that we will use a simulatorrunning on Linux with the GNU compiler as a target platform. Click onthe Next button again.
Click Next and then Finish button.
Now you can see the newly created project in the Project Explorertab.
The project does not contain any source files. To create a new Csource file choose from menu File→New→File and enter its nameinto the dialog window that opens.
An empty new C file is created. Now copy the following code to it.
As with most modern IDEs it is possible to build and run anapplication with a single click. It is, however, quite useful tounderstand what happens behind the scene. We will first look at theindividual steps that are needed to run a VxWorks application and thenwe will show how to do it with one click.
3.1 Manual, step by step procedure
To build the project choose Project→Build All or Project→BuildProject. First invocation of building the project asks for extensionof search path. In here, you can procced with Continue.
The build log can be watched in the Build console tab that opensduring the build process.
The built application needs to be executed on a target machine. Wewill start with using VxWorks simulator (vxsim) as the target'machine'. The simulator should be already preconfigured in the IDE soyou can launch and connect it by clicking the Connect vxsim0button in the Remote Systems tab.
If you do not see vxsim0 in the Remote Systems tab, create theconnection by right-clicking there and selecting New→Connection→WindRiver VxWorks 6.x Simulator Connection, then Next andFinish.
Then, you will see the simulator console in the Target Consolestab that opens up during connecting to the simulator.
The Remote Systems tab will show the information about the runningsimulator.
To load the built application into the simulator chooseDownload→VxWorks Kernel Task… option from the target's contextmenu (see below). Download Configurations dialog appears. You canleave everything in default values. In case that you work with multiplebinaries, you should check that the correct application is selectedin Downloads tab. Finish the operation by pressing the Downloadbutton.
To run the application in the simulator, type sp CreateTasks onthe target console (command line). Command sp creates a new taskwith CreateTasks function as the entry point. The command ilists all running tasks.
Our application prints messages to the simulator console, which makesit hard to enter other commands. Fortunately, it is possible to startanother console as follows: Right click on the vxsim0 item in theRemote Systems tab and choose Host Shell from the opened menu.Now, you can type any commands easily, e.g. the td Task1 commanddeletes one of the tasks that we have run previously.
3.2 One click alternative
While developing your application you will typically need to run yourprogram repeatedly. For example, you run your program, realize that ithas a bug, fix the bug in the source code and run the program again.It is annoying to repeat the steps described in the previous sectionover and over again. Fortunately, Workbench IDE can automate all ofthis. When you click the 'play' icon for the first time, a dialogwindow will show up to let you setup basic parameters.
First time you try this an error is reported. It is not a severe problemas it only reports that the configuration is not complete.
Basically the only information missing for running the configuration isan entry point. You can select an entry point by clicking the Browse...button.
Opened up window Entry Points might be empty when the project is not yetbuilt.
From now on, you can press Ctrl-F11 to relaunch the lastconfigured application.
To debug your program launch it either directly in the debugger(Run→Debug As→VxWorks Kernel Task) or attach the debugger to an alreadyrunning task – in the Remote Systems tab select the task you wantto attach to, right-click it and choose Debug→Attach to TaskX from the contextmenu (right click).
First, the attached task needs to be stopped.
The Debug window shows the 'backtrace' (the sequence offunction calls) of the stopped task. The stopped task can be furtherinspected (e.g. see Variables window) or traced using buttons inthe Debug window.
Wind River Workbench IDE provides the complete documentation to theVxWorks OS and the IDE itself.
If you want to read the documentation as book (not just a APIreference) select Help→Help Contents or just Contents in theHelp window. Then, you can browse all available documentation.Typically, you will navigate to the following chapters:
- If you develop a Downloadable Kernel Module:
- Wind River Documentation→VxWorks→VxWorks Kernel Programmer's Guide
- Wind River Documentation→VxWorks→VxWorks Kernel API Reference
- If you develop a Real-Time Process:
- Wind River Documentation→VxWorks→VxWorks Application Programmer's Guide
- Wind River Documentation→VxWorks→VxWorks Application API Reference
When you choose tab Related Topics in the Help tab, it will offer(after a longer delay caused by creation of the index) a list of related topicsto the keyword at current cursor position.
The System viewer is a tool for monitoring activities inside a runningsystem. It facilitates logging of various events (task statetransition, context switch, IPC events, etc.) and shows themoff-line in graphs. To launch the System viewer right click on thevxsim0 item in the Remote Systems tab and choose LaunchSystem Viewer.
In the configuration dialog choose the events you want to log. You canselect either the context switch or task state transitions or specificones like events related to semaphores, message queues, etc.
After finishing the configuration, start event logging by clicking theStart System Viewer logging button (the green 'play' button underthe menu; see the figure above). Let System Viewer run for sufficienttime (10–20 seconds) and then stop the logging by Stop SystemViewer logging button.
You can hide/filter out the tasks from the time diagram that are notinteresting for you.
Clicking the =? icon gives you the description of marks and linetypes used in the diagram.
Use the System Viewer tool to compare the behavior of your programwhen
kernelTimeSlice(1)
is commented out and when it is not.Look up kernelTimeSlice
documentation and compare thedocumentation with the observed behavior. Explain the teacher what thekernelTimeSlice
function does and show him the system viewertraces (both with and without kernelTimeSlice
).DISCUSSION
Overview
Workbench 3.1 was the last Amiga OS version released by Commodore/Amiga, and the release by Cloanto aims to celebrate this version trying to be as true to the original as possible without compromising functionality. This is unlike the Workbench 3.X environment, which intentionally added several recognizable post-Commodore/Amiga features.
By popular demand, and consistent with our original goal of preserving the Classic Amiga heritage, the Amiga Forever series always included ROMs, floppy disk images and system updates also taking into account 'Classic Support' scenarios (for use outside of emulated Amiga systems).
Thus, Workbench 3.1 became available as sets of physical floppy disks (e.g. for customers who purchased a used Amiga computer, but were missing the disks), preinstalled on CompactFlash and SD cards, and in other formats. A license key is always included, to make it possible to additionally download a copy to update or restore the original.
System Requirements
Workbench 3.1 requires a 3.0 or 3.1 Amiga ROM ('Kickstart') version, and is additionally compatible with 3.X ROMs as used in Amiga Forever.
Shared Improvements
In a careful balance of preservation, restoration and innovation, features of all Amiga Forever Classic Support editions of Workbench 3.1 include:
- Dates were preserved, while file attributes and comments were restored (relative to the distribution by ESCOM and Village Tronic)
- Updated C/Version command (Y2K patch)
- Addition of Libs/workbench.library (for A-4000T 3.1 ROMs and 3.X ROMs)
- Updated S/Startup-Sequence (conditional SetPatch, for 3.X ROMs)
- Increased MultiView stack to 32768
- Installer script improvements
- Updated Installer (43.3 or 44.10, depending on CPU) and FastFileSystem 45.9 (to support larger disks)
- Installer itself is now part of the system installation (inside the Utilities directory)
Floppy Disk Set
The Amiga Forever Classic Support floppy disk (image) set consists of six disks, and features the same improvements of the hard disk version. Additionally, the installer script was modified to support the changes, and with some other enhancements (e.g. to avoid 'disk full' errors on large disks and to fix some typos). All disks were carefully tuned and defragmented for maximum performance.
The floppy disk set can be used alone (to boot and use the system), or to create a new hard disk installation, equivalent to the Amiga Forever Classic Support hard disk image. Enhancements include the installation of workbench.library, Installer 43.3 (on 68000 or 68010 CPUs) or 44.10 (on 68020+ CPUs), and FastFileSystem 45.9.
Hard Disk Image
The Amiga Forever Classic Support hard disk image is the result of a full installation from the floppy disk set.
As part of this, the appropriate Installer program is copied to the Utilities directory, which is part of the system search paths and which was also the location chosen by Commodore/Amiga in many of its own installations.
Depending on the desired video modes, one or more monitor files may need to be copied manually from 'Storage/Monitors' to 'Devs/Monitors'.
Support for Disks Larger than 4 GB
The installer script included on Amiga Forever Classic Support media was improved to support installation to hard disks larger than 4 GB regardless of the Installer, FastFileSystem and ROM version.
Full runtime support for disks larger than 4 GB requires several elements, of which FastFileSystem 45.9 and Installer 44.10 are included in the Workbench 3.1 distribution, whereas lower-level components such as scsi.device come from a ROM update, such as the 3.X ROM (supported, but not included).
For maximum compatibility, the Amiga boot partition should be the first partition of a disk, and it should not be larger than 4 GB. In order to remain compatible with older software that uses 32-bit values to measure disk capacity, a maximum partition size of 2 GB is recommended.
The FastFileSystem component itself may be included in different locations: the Amiga system ROM, the Amiga disk RDB, and as a file (FastFileSystem, inside the 'L' directory of the system disk). Based on the available versions, the system determines which version to load.
For large disk support, confirm that the destination disk RDB has an official NSD-compatible FastFileSystem 43.20 or 45.9 or higher (e.g. use 'Version DH0: FULL').
To update the FastFileSystem stored in the disk RDB, run Tools/HDToolBox, select Partition Drive with [x] Advanced Options, then Add/Update..., select FastFileSystem, then Update using the FastFileSystem as provided in the Amiga Classic Support Workbench 3.1 distribution (use 'Version l:FastFileSystem' to check that version).
Emulation-Specific Changes
Workbench 3.1 versions that are included in the emulation environment of Amiga Forever include the above modifications which are shared with the Classic Support series, plus some emulation-specific changes which are not part of the Classic Support series:
- Added C/Shutdown command (for shutting down the session)
- Added C/GetHostVar command (for passing data from host to guest)
- Restored licensed speech-synthesis files to Devs, L, Libs, Utilities
- Added Devs/DOSDrivers/Speak
- Added UAE RTG files to Libs, Storage
- Set default printer to EpsonQ (emulation has emulated EpsonQ printer)
- Updated S/Startup-Sequence to bind in several utilities (NewIcons, FullPalette, LhA, etc.) from Amiga Forever Work partition, if present
- Updated S/Startup-Sequence to support Cloanto S/AFShared-Startup
- Updated S/Shell-Startup to support Cloanto UXCLI
- Edited SCSI_DEVICE_NAME in Tools/HDToolBox.info ('scsi.device' replaced with 'uaehf.device')
Slightly different hard disk image file names are used to differentiate between the Classic Support ('workbench-310.hdf') and the emulation-enhanced ('workbench-311.hdf') versions.
For space reasons, because the 3.1 floppy disk images contain additional emulation support files, they do not contain a copy of Libs/workbench.library. The file is however included in both the the 3.1 hard disk image and in the preinstalled Workbench 3.X environment.
For more details on 'uaehf.device' vs. 'uaescsi.device' and other emulation-specific changes see:
Wind River Workbench 3.3 Download
Online Support
Each Classic Support set comes with a license key that can be used to download the same set again for recovery or update purposes. To register for support, please refer to cloanto.com/genuine.
Additional Enhancements
Workbench 3.1 remains true to the look and feel and the feature set of the last Workbench by Commodore/Amiga, including support for 3.0 ROMs and the ability to boot from floppy disks. For maximum compatibility, no new ROM functionality is provided in the disk set.
For additional enhancements, Amiga Forever includes a 3.X ROM and an environment named Workbench 3.X. Workbench 3.1 as discussed here is compatible with 3.X ROMs.