This guide explains how to create an ICS Configurator workspace, generate the host configuration files, and program the target firmware.
The workflow assumes that the target bootloader is already installed and that you completed the Quick Start (board setup, Config Mode, UART connection). It covers PC runtime installation, workspace configuration, code generation, and direct target programming with ICS Configurator.
The Configurator requires the Microsoft .NET 10.0 Desktop Runtime. If the runtime is missing, launching the Configurator displays an error dialog with a link to the Microsoft download page.
The runtime only needs to be installed once per computer.
Select Config Mode and connect the board before opening the Configurator connection.
.ics).
If the message is absent, check the selected COM port, close other serial sessions, confirm that the CN11 jumper is fitted, and press RESET again.
When the Configurator starts without a loaded workspace, it shows an empty workspace screen.
| Button | Action |
|---|---|
| Choose a save location, enter a workspace file name, and click Open. A workspace with default settings is created. | |
Select an existing .ics file and click Open. | |
| Save the current configuration. | |
| Show information about the application. |
Once a workspace is open, the Overview tab shows the configuration fields.
| Field | Description |
|---|---|
| Protocol Selection | Select EtherCAT for the example in this guide. Select PROFINET or EtherNet/IP for the corresponding application. |
| Fast Boot Enabled | Set to False for the EtherCAT workflow shown here. See the FastBoot note below. |
| Output Folder | Directory in which the generated files are stored. |
| Generate Firmware | Leave False for direct flashing from the Target view. Set True to also generate target_firmware.c for firmware provisioning from the host. |
| Firmware Download Retries | Number of retries for the firmware download. Default: 5. |
| Wait to write memory response | True or False. Default: False. |
The catalog fields contain the protocol descriptions used for code generation. Use the files supplied for the target application. These files are separate from the firmware selected in the Target view.
| Protocol | Catalog file |
|---|---|
| EtherCAT | ESI XML file |
| PROFINET | GSDML XML file |
| EtherNet/IP | EDS file in Catalog and its matching JSON description in JsonCatalog |
For EtherCAT:
TICS100MOD Simple.xml.
The EtherCAT tab lets you assign an index to each enum defined in the ESI file. The Enums list is populated automatically once an XML file is selected in the Overview tab.
Once the configuration is complete, click
Generate to create the source code.
A Generator Result dialog shows the generation output, including any warnings or errors. On success, the files are created in the Output Folder.
| Generated file | Content |
|---|---|
repository.c, repository.h | Repository of the selected protocol |
device_settings.c | Device configuration, including the protocol selection (ProtocolIndex) |
channel_settings.c | Channel settings of the selected protocol |
target_firmware.c | Firmware data for provisioning from the host. Generated only when Generate Firmware is True |
Add the generated files to your host application project. Build the host application with the files generated for the protocol that is flashed on the module. The examples describe where to copy them, see Examples.
The Protocol Selection of the workspace sets ProtocolIndex in the generated device_settings.c. The Linux host application user.c copies the corresponding deviceConfigObjects entry into its device configuration.
| ProtocolIndex | Protocol |
|---|---|
| 0 | EtherCAT |
| 1 | PROFINET |
| 2 | EtherNet/IP |
Select the intended protocol, regenerate the files, and use them in the matching host build. Keep the protocol selection in the workspace so that regenerated settings remain consistent.
FastBoot is set to False in this guide and in the provided example configuration. For PROFINET, FastBoot is typically set to True. Enabling FastBoot locks the selected protocol: it cannot be changed afterwards.
The Quick Start describes the same procedure in short form, see Quick Start. Use this section for the details of the Target view.
The decoded target log at the bottom of the Target view shows the startup mode and, during flashing, the programming activity.
Two controls manage the log:
The Firmware Update section lists each protocol and its firmware folder. Default folder paths are resolved relative to the saved .ics workspace location.
firmware/Ethercat, firmware/EthernetIp, or firmware/Profinet in the SDK. Confirm that the MCELF and XIP fields show the corresponding file names.
With the target connected in Config Mode and the firmware folders checked, click Flash. Progress is shown in the application.
After a successful firmware update:
The target boots in Run Mode and starts the programmed application.