https://forge.codesys.com/forge/talk/Runtime/thread/e6aceff994/Recent posts to CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS imagesenMon, 10 Aug 2026 21:37:19 -0000https://forge.codesys.com/forge/talk/Runtime/thread/e6aceff994/?limit=25#04f7<div class="markdown_content"><p>when is the releaseof the 4.2.0.0</p></div>axberryMon, 10 Aug 2026 21:37:19 -0000https://forge.codesys.combe7e2e1035c63321f5877af5878890ec079172eehttps://forge.codesys.com/forge/talk/Runtime/thread/e6aceff994/?limit=25#370a<div class="markdown_content"><p>you need to wait fir 4.22.0.0 release which will fix this problem</p></div>eschwellingerMon, 10 Aug 2026 21:32:25 -0000https://forge.codesys.com778475f7e49d92c6f729bf9d37527945cd15123ahttps://forge.codesys.com/forge/talk/Runtime/thread/e6aceff994/?limit=25#f772<div class="markdown_content"><p>Hi,</p> <p>I'm trying to run CODESYS Control for Raspberry Pi SL on a Raspberry Pi 5, and the runtime consistently fails to start with the following error when launched manually:</p> <p>ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB)</p> <p>Hardware:</p> <p>Raspberry Pi 5 Model B Rev 1.1<br/> Revision code: d04171<br/> CPU: aarch64, BCM2712<br/> Serial number is correctly exposed via /proc/cpuinfo and /proc/device-tree/serial-number<br/> /proc/device-tree/model correctly reports "Raspberry Pi 5 Model B"</p> <p>What I've tried (all resulting in the same error):</p> <p>CODESYS Control for Raspberry Pi SL 4.11.0.0 (SDK 3.5.19.61) — the version that introduced Pi 5 support<br/> CODESYS Control for Raspberry Pi SL 4.21.0.0 (SDK 3.5.22.20) — latest available<br/> Raspberry Pi OS Bookworm (64-bit) with kernel 6.12.93+rpt-rpi-2712 (June 2026 build)<br/> Fresh install on Raspberry Pi OS Bookworm (64-bit) with an older image from November 24, 2025 — same error, ruling out a kernel-version regression<br/> Bootloader/EEPROM confirmed up to date (rpi-eeprom-update reports "up to date")<br/> Clean purge and reinstall of the codesyscontrol package each time (verified via dpkg -l, no leftover files)<br/> Verified /etc/codesyscontrol/3S.dat correctly symlinks to /etc/codesyscontrol/3S_aarch64.dat</p> <p>The service starts (systemctl status briefly shows active (running) with a real PID under /opt/codesys/bin/codesyscontrol.bin), but crashes shortly after and the process disappears — port 11740 never opens.</p> <p>Since this happens identically across two different runtime versions and two different OS images (5+ months apart), it doesn't seem to be a kernel/firmware timing issue. Could this be specific to the Rev 1.1 board revision, or is there a known issue with the hardware detection logic in the SL runtime that I should be aware of?</p> <p>Happy to provide full debug logs (-d flag output) or journalctl output if useful.</p> <p>Thanks in advance!</p></div>axberryMon, 10 Aug 2026 21:18:17 -0000https://forge.codesys.com2bdd0854195cdfbf934d9b1a0feee0fa1a4677b7