Getting Started
1. Install the device description
Section titled “1. Install the device description”CODESYS identifies the board through its device description file (.devdesc.xml).
- Download
CODESYS_Control_Pico2.devdesc.xml. - In CODESYS: Tools → Device Repository → Install…
- Select the downloaded
.devdesc.xmlfile and confirm.
The device then appears in CODESYS Control devices as:
| Name | nXPico |
| Vendor | nexo S.r.l. |
| Device ID | 167e 2008 |
| Version | 3.5.20.100 |
2. Create a project and add the device
Section titled “2. Create a project and add the device”- File → New Project… → Standard project.
- As the device, pick nXPico.
- Under the device node, an IO module is added automatically (digital I/O, analog inputs, LED, temperature) — see IO Mapping.
3. Connect and log in
Section titled “3. Connect and log in”- Connect the board over micro-USB. The CODESYS gateway runs over USB (it is COM1 inside the runtime), so no network is involved.
- In the device editor’s Communication Settings, scan and select the device.
- Login and download your application.
At the first login CODESYS asks you to create the administrator user: the board has no default users or passwords. See Users and Passwords.
The application is written to flash and starts automatically on power-up. The code, up to 1 MB, is written to flash sector by sector during the download. If the download is interrupted (for example by unplugging the USB cable), no application starts at the next boot.
Runtime limits
Section titled “Runtime limits”The CODESYS runtime on nXPico has the following fixed limits:
| Setting | Value |
|---|---|
| Cyclic IEC tasks | 3 — a fourth one is refused with an error at download or at startup |
| Max task priority | 31 |
| Default cycle time | 100 ms (can be set both higher and lower) |
| Code + constants (flash) | 1 MB, executed in place (XIP) |
| Data (variables) | 20 KB |
| I/O image | 1280 bytes input, 1280 bytes output |
| Online change | Not supported — full download only |
| Applications | 1 (Application) |
| Force / write variables | Supported |
| Breakpoints | Not available — see below |
Breakpoints. The board is protected by secure boot, and the chip’s protection disables debugging: the red dot appears in the IDE, but execution does not stop. Monitoring, writing and forcing variables remain available.
Next: IO Mapping, Serial Ports and ST Examples.