Loading applications with CyanIDE

CyanIDE is an Integrated Development Environment for the Cyan Technology eCOG1k and eCOG1X microcontrollers. It provides a suite of integrated tools to:

• Organise project and source files.
• Edit source files.
• Build the project.
• Run and debug the project.
• Automate tasks and extend CyanIDE functionality.

CyanIDE supports the whole family of Cyan microcontrollers from a common core application. Specific support for individual microcontrollers is provided by extension modules.

The CyanIDE workspace is divided into a number of windows.

The Navigator window is used for browsing files. When CyanIDE is first started, the Navigator window contains a single tab (the Help tab) for navigating the online help documents. When a project is opened, a second tab (the Files tab) is displayed for browsing and organising the files in the current project.

The Editor workspace is the main area within the CyanIDE application window. It displays documents and files open for editing.

The Output window contains four tabs displaying program output:

• Build - displays output from the build process.
• Debug - displays error messages and program output.
• Find in Files - displays output from a Find in Files text search.
• Command - the built-in Python command line interface.

Debug windows are available during debugging and allow the program state to be viewed and modified. The following windows are available:

• Registers - display and modify processor registers.
• Watch - display and modify variables or individual memory addresses.
• Memory - display and modify memory.

The working environment within CyanIDE is organised into projects.
A typical project includes:

• Source code files
• Configuration file
• Project properties controlling compilation, linking and debugging

A project also defines a target processor or simulator. Appropriate debugging support for the target processor or simulator is initialised when a project is loaded.

Organising source files

Source files are organised in the Navigator pane into logical folders and subfolders within a project. Folders may be created and files grouped as required. Note that the logical folder structure of the project files as displayed in the Navigator pane is independent of the physical location of the files on disk.

Source file in the project can be opened for editing in the text editor.

Building the project

Building the project produces an executable program that can be run on the target processor or simulator. The build steps performed include compilation of the source files followed by linking. The exact build sequence is determined by the project type and target processor or simulator.

CyanIDE attempts to build only the files that have been modified since the last build, unless a complete rebuild of the project is forced by selecting the Rebuild All menu item. File dependencies are maintained automatically.

Project properties

Project properties controlling compilation, linking, and debugging are grouped into project configurations. New configurations can be created to build different versions of the project. For example, separate configurations can be set up for a Release version and a Debug version of the project.

Project workspace

The project workspace including open files, window positions, watched variables, and breakpoints is saved as a file in the main project directory. These properties are saved in the workspace file when the project is saved or closed, and are restored when the project is reopened.