Projects by SEGGER
With more than 28 years of experience in embedded applications, SEGGER offers high quality middleware that significantly cuts down software development time. By following strict, yet efficient coding and documentation standards, SEGGER provides compact, flexible and easy-to-use software projects that allow end developers to fully concentrate on the development of their application.
Each software project shipped by SEGGER (including but not limited to SEGGER Eval software) is specifically created, optimized and verified to run on particular target hardware. These shipments include linker and setup files written in ANSI-'C' and Assembly when necessary, a workspace/project for the desired target tool-chain pre-configured to run out-of-the-box, and some or all of the following middleware components:
- embOS (Real Time Operating System)
- emNet (TCP/IP Stack)
- emFile (File System)
- emLib (Helper Libraries)
- emLoad (Bootloader)
- emModbus (Modbus Software)
- emUSB Device (USB Device Software)
- emUSB Host (USB Host Software)
- emWin (Graphic Software & GUI)
Pick Your Tool-Chain – SEGGER Offers Professional Porting Services
Due to numerous requests and SEGGER’s experience of working with multiple embedded development environments, SEGGER now offers a professional tool-chain porting service. This service enables the migration of a project from one tool-chain (IDE and Compiler) to another. The service includes every aspect of migration:
C and Assembly files are modified as necessary, linker and setup files are created, and a project is created specifically for the newly chosen target tool-chain which mirrors the configurations found in the original project. The end developer typically needs less than half a day to be up and running with his new tool-chain.
The porting service can pay for itself, especially when moving from an expensive proprietary commercial tool-chain to a GCC-based one.
There are multiple reasons to take advantage of this service which include:
- No dependency on a particular vendor
- Remove problems with license management
- Increase productivity
- Reduced cost
- Better editor/debugger
- More flexibility
Porting from one tool-chain to another is easiest and therefore least expensive, if the firmware is based on SEGGER middleware. “Due to years of experience with different tool-chains, it is easy for our engineers to migrate projects from one tool-chain to another. We do it all the time. And, with the obvious trend found in our industry, of companies moving to GCC-based tool-chains, a porting service to help facilitate this only makes sense. We find that companies are switching to all forms of GCC-based tool-chains, be they Visual-Studio-Style or Eclipse, commercial or free. Anybody who is interested in changing tool-chains is welcome to talk to us”, says Ivo Geilenbruegge, Managing Director of SEGGER.
Please contact SEGGER to learn more: info@segger.com.
Project Contents
SEGGER offers projects for various tool chains. The following examples demonstrate the contents of typical shipments for the IAR EWARM IDE as well as for emIDE.
Contents of an IAR EWARM Project
Typically, project shipments for the IAR EWARM IDE include:
| Folder or file | Description |
|---|---|
| "Doc" | Includes documentation on included middleware components |
| "Start" | Includes project, object and source files |
| Documentation on using SEGGER Eval Software with the chosen toolchain (optional) | |
| License.txt | Text file including license information |
The project itself then consists of:
| Folder or file | Description |
|---|---|
| "Application" | Includes source code for various sample applications for included middleware components |
| "Config" | Includes configuration source code and header files for included middleware components |
| "Inc" | Includes additional header files |
| "settings" | Preconfigured settings for the IAR EWARM IDE |
| "Setup" | Includes board support source code and header files, linker files, startup files, macros |
| "Util" | Includes source code files for various utilities required by the included middleware components (optional) |
| "Windows" | Includes source code and/or object and header files for various Windows applications, as well as required drivers |
| "FS", "GUI", "IP", "OS", "USB" and "USBH" | Include source code or object and header files for included middleware components |
| ReadMe.txt | Text file including information on the included middleware components, tested tool chain versions and project configurations |
| *.ewd, *.ewp, *.eww | The preconfigured project/workspace files for IAR EWARM |
| *.dsp, *.dsw | Project/workspace files for MS Visual Studio (for Windows applications) |
Upon opening the workspace/project, the IAR EWARM IDE will show the same structure as the folder above:
Contents of an emIDE Project
Typically, project shipments for emIDE include:
| Folder or file | Description |
|---|---|
| "Doc" | Includes documentation on included middleware components |
| "Start" | Includes project, object and source files |
| Documentation on using SEGGER Eval Software with the chosen toolchain (optional) | |
| License.txt | Text file including license information |
The project itself then consists of:
| Folder or file | Description |
|---|---|
| "Application" | Includes source code for various sample applications for included middleware components |
| "Config" | Includes configuration source code and header files for included middleware components |
| "Inc" | Includes additional header files |
| "Setup" | Includes board support source code and header files, linker files, startup files, macros |
| "Util" | Includes source code files for various utilities required by the included middleware components (optional) |
| "Windows" | Includes source code and/or object and header files for various Windows applications, as well as required drivers |
| "FS", "GUI", "IP", "OS" and "USB" | Include source code or object and header files for included middleware components |
| ReadMe.txt | Text file including information on the included middleware components, tested tool chain versions and project configurations |
| *.emP | The preconfigured project/workspace files for emIDE |
| *.dsp, *.dsw | Project/workspace files for MS Visual Studio (for Windows applications) |
Upon opening the workspace/project, emIDE will show the same structure as the folder above: