Evaluation & licensing FAQ

Yes. Build the pinned v2.1.1 Linux host stack and run its tests. For v2.1.0, the host build and 36 CTest targets passed with GCC 13 on 2 October 2026.

STM32G0B1RE IAR project sources include source groups, C99 settings, startup references and a linker file. Set the CMSIS paths from the README. GCC firmware build: passed. IAR build: requires EWARM verification. Hardware and IDE details.

Firmware builds passed for STM32G0B1RE with Arm GCC and TIOL112; Nucleo-U575ZI-Q with Zephyr 3.7.2 and TIOL112; and ESP32-C3-DevKitM-1 with ESP-IDF 5.4.0 and STEVAL-IOD003V1/L6362A. Each includes source, build commands and wiring. Storage: RAM. Compare projects and build evidence.

The reference projects include TIOL112 and L6362A drivers with MCU UART, GPIO, wake-up and microsecond-timer adapters. Driver host tests and all three firmware builds passed. The ESP32-C3/L6362A example documents STEVAL-IOD003V1 headers, power settings and the IN1 modification. Manufacturer documentation.

The ESP32-C3 counter/button-and-LED reference includes an ESP-IDF application, L6362A adapter and STEVAL-IOD003V1 wiring. The thermal condition sensor provides native ESP-IDF MLX90640 classifier source; its source/build CI passed for commit f24680e.

Start with the shared reference application: its three input bytes carry a counter and button, and one output byte controls the LED. Change the payload sizes and application mapping together, then add parameters through the stack's ISDU/parameter APIs and replace the example product identity. Keep the IODD consistent with those definitions. The IODD generator produces draft XML. The IODD editor and MCP tools provide editable templates, XML/ZIP export and validation. Published examples passed the October 2025 official XSDs and the genuine legacy IODD Checker 1.1.4; see the Checker evidence. Physical IO-Link conformity and the current Checker release have not been established for the new reference.

Check the supply, common ground and C/Q wiring against the transceiver guide; UART 8E1 and the selected COM baud; WAKE, EN and diagnostic GPIO polarity; the microsecond hardware timer; driver release after transmit completion; echo suppression and RX overflow/error handling. Keep logging off the protocol UART. Use the porting guide and board-specific instructions, and include firmware, master model, logs and timing captures in a report.

Commercial-master bench validation is pending. Current measured evidence covers firmware builds, host tests and software master/device exchanges. See results and reproduction commands.

Certification status: not certified.

Public customer references are not currently listed. Published build and test evidence is available for evaluation.

One named commercial product range agreed in the quote, including its variants, successors and hardware revisions. Manufactured units, customers and variants within that range are unlimited and royalty-free. An unrelated product line needs a separate license. Enterprise scope for multiple families, subsidiaries or broader SDK redistribution is quoted separately. Existing or separately agreed rights keep their accepted scope.

The license remains valid when the MCU or PHY changes within the agreed product family. Porting and hardware validation are separately scoped and quoted.

Indie is issued to one named individual for their own independent product family, with perpetual royalty-free rights and unlimited manufactured units, customers and variants within that family. It includes source, documentation and the reference release, two onboarding hours for build/setup, MCU/PHY wiring and callback review, a written checklist, one year of updates and bug fixes and a 48-hour email response target. An employee’s Indie license does not grant rights to their employer or another company; company projects need a Company license held by that legal company.

Company is held by the named legal company for one agreed product family, with unlimited authorized employees and contractors working on that family. It provides the same source, documentation and reference release, perpetual royalty-free family rights and one year of updates and bug fixes. Eight total scoped integration hours include setup/build configuration review, MCU/PHY callback and wiring review, a written checklist and findings/report from the agreed build/test review. It also includes a 24-hour priority email response target and quarterly reviews during the included first year within the eight total hours. Agree target, compiler, PHY and tasks before booking.

Indie includes two onboarding hours for build/setup, MCU/PHY wiring and callback review, and a written bring-up checklist. Company includes eight total scoped engineering hours for agreed board, compiler, PHY and API tasks. Agree the tasks, deliverables and booking window before scheduling. Larger ports need a separate quote. Reproducible stack bug fixes do not consume custom engineering hours. Both packages receive the same source, documentation and reference release.

The current terms retain perpetual rights to use the version you licensed. The included update period is one year. Extended support is optional and currently listed at 20% of the original license fee per year; confirm the renewal coverage in your agreement.

Binary redistribution as part of your product, including a system-on-module, is compatible with the prior clarification from the licensor by email. Confirm this use and its scope in the signed agreement. Redistributing iolinki source to third parties is a separate matter and needs explicitly agreed terms; buying a product-family license does not by itself grant source-resale rights.

Both package quotes cover one agreed named product family, with unlimited manufactured units, customers, variants and hardware revisions within that commercial range, royalty-free. MCU/PHY changes within that family retain the license; porting and validation are separately quoted. Unrelated lines require a separate license. Enterprise multi-family, subsidiary and broader SDK redistribution scope is quoted. Already granted or separately agreed rights retain their accepted scope.

The public code is available under GPLv3-or-later. Evaluation, internal use, modifying code and conveying software have different implications under the license. When you distribute a covered work, obligations can include corresponding source, license notices and the applicable GPL terms. “Evaluation” is not a blanket exemption, and making source visible alone does not resolve every obligation. Read the license for your use and distribution model. Commercial terms provide the proprietary licensing path.

Start with the public GPL source and the STM32G0B1RE/TIOL112 reference project; adapt its documented MCU callbacks and wiring to your board. Evaluation follows the published GPL terms. Contact the licensor for a defined evaluation period or different terms.

Enterprise is quoted for multiple product families, subsidiaries, broader SDK redistribution and agreed business scope and engineering services. Send your product ranges, board, toolchain and integration requirements.

Release scheduling and support priorities are agreed in the quote. Release history, reported issues and CI results are public. Send the affected commit, target, toolchain, impact and reproduction when reporting a bug.

Supported versions, maintenance periods and security reporting requirements are agreed in the quote. The commercial tiers include one year of updates and bug fixes, with optional extended support.

Inspect releases, CI and issues. Include your release/commit, toolchain, target, reproduction commands and logs. Commercial support follows the accepted agreement.

Include the MCU/board and PHY, IDE or RTOS, COM mode and process-data sizes, ISDU/data-storage needs, master model, schedule, product-family range and whether customers receive binaries or source. Start with the host evaluation and hardware matrix to identify the remaining work.