This guide takes you from unpacking the boards to a TICS100MOD module with flashed firmware, ready to be connected to a host. It applies to ICS Development Board revision V2 and Carrier Board revision 3.0.0.
After completing this guide, build and run a host application from the Examples. The Configurator guide describes the flashing procedure used here in more detail.
| Item | Details |
|---|---|
| Hardware | 1 × Carrier Board, 1 × ICS Development Board |
| Power | 5 V supply |
| Cable | Micro-USB cable (UART access) |
| Software | TICS100MOD-SDK installed |
In this guide, {SDK_DIRECTORY} is the folder in which the TICS100MOD-SDK is installed.
Carrier Board
| No. | Item | Function |
|---|---|---|
| 1 | Mating connector | Connection to the ICS Development Board |
| 4 | USB-C connector | 5 V input |
| 5 | Micro-USB connector | UART access |
| 6 | LEDs | Status indication (see Step 5) |
ICS Development Board
| No. | Item | Function |
|---|---|---|
| 1 | Mating connector | Connection to the Carrier Board |
| 2 | CN5 header | Boot mode selection (see Step 2) |
| 3 | CN11 header | Configuration mode selection (see Step 3) |
| 6 | LEDs | Status indication (see Step 5) |
The CN5 header on the ICS Development Board selects the boot mode of the module. Boot mode pins provide information to the ROM code for boot and must be set before the power ramp.
| Header Pin | Pin description | Header Pin | Pin description |
|---|---|---|---|
| CN5_1 | +3V3 | CN5_2 | SOP0 |
| CN5_3 | +3V3 | CN5_4 | SOP1 |
| CN5_5 | +3V3 | CN5_6 | SOP2 |
| CN5_7 | +3V3 | CN5_8 | SOP3 |
| Boot Mode | SOP3 | SOP2 | SOP1 | SOP0 |
|---|---|---|---|---|
| OSPI (4s) | 0 | 0 | 0 | 0 |
| UART | 0 | 0 | 0 | 1 |
| OSPI (1s) | 0 | 0 | 1 | 0 |
| OSPI (8s) | 0 | 0 | 1 | 1 |
| DevBoot | 1 | 0 | 1 | 1 |
| xSPI 8D | 1 | 1 | 0 | 0 |
| USB DFU | 1 | 1 | 1 | 0 |
| Unsupported Boot Mode | All other combinations are not defined |
Use OSPI (4s) mode. In this mode no jumpers are fitted: leave all pins of CN5 open.
The CN11 header on the ICS Development Board selects the operating mode of the module. The mode is read at startup.
| CN11 jumper | Module mode |
|---|---|
| Fitted (pins connected) | Config Mode |
| Not fitted | Run Mode |
To flash the firmware in this guide, fit the CN11 jumper now, with the boards unpowered. Config Mode allows ICS Configurator to write the module firmware. If you change CN11 later, power-cycle the boards to apply the new mode.
{SDK_DIRECTORY}\tools\ics-configurator\ics-configurator.exe..ics workspace file.
If the UART COM port is not listed, install the FTDI Virtual COM Port (VCP) driver, reconnect the micro-USB cable, and refresh the COM port list in ICS Configurator. On Windows, the assigned COM port number is shown in the Device Manager under Ports (COM & LPT).
The boards were powered before ICS Configurator connected, so the startup messages were not captured. Press the RESET button on the ICS Development Board. The Target tab of ICS Configurator must now show the following startup message:
If the message does not appear, check the selected COM port, close any other application using the COM port, confirm that the CN11 jumper is fitted, and press RESET again.
Compare the LEDs with the tables below.
Carrier Board
| LED | Expected state at power-on | Meaning |
|---|---|---|
| D2 | ON | Reset status: the MCU is released from reset |
| D6 | ON | +3V3 is present on the Carrier Board |
| D10 | ON | +3V3 is present on the Module |
ICS Development Board
| LED | Expected state at power-on | Meaning |
|---|---|---|
| D4 | ON | WARMRSTN status: warm reset is deasserted |
| D7 | ON | PORZ status: power-on reset is deasserted |
| D8 | OFF | User LED |
| D9 | ON | Power Good: the input supply and the +3V3 output rail are valid |
| D14 | ON | +3V3 is present on the Module |
| D10 | OFF | UART COM |
D2, D4, and D7 indicate reset status on different signals. When they are ON, the MCU is not held in reset. These indicators apply in both Config Mode and Run Mode.
The SDK provides pre-built firmware for each protocol:
| Protocol | Firmware folder |
|---|---|
| EtherCAT | {SDK_DIRECTORY}\firmware\Ethercat |
| EtherNet/IP | {SDK_DIRECTORY}\firmware\EthernetIp |
| PROFINET | {SDK_DIRECTORY}\firmware\Profinet |
.mcelf and .mcelf_xip images. ICS Configurator fills in the image file names automatically. Repeat for every protocol you want to flash.
The ICS Configurator Target view shows the following message in Run Mode:
This is the expected output at this stage. The module is now ready to be connected to a host application.
Build and run a host application, see the Examples. Make sure the firmware you flashed matches the protocol of the example build configuration.