https://forge.codesys.com/u/nixola/2026-07-21T12:32:28ZRecent posts by nixola2026-07-21T12:32:28Z2026-07-21T12:32:28Znixolahttps://forge.codesys.com/u/nixola/https://forge.codesys.coma86e0ad4b59e27a73da4a43a8802a6539c1ca2ec

<div class="markdown_content"><p>Hi, I added the following lines to <code>/etc/codesyscontrol/CODESYSControl_User.cfg</code>:</p> <p><code>[CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev* PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip*</code></p> <p>However, I'm still unable to read or control GPIO pins from any CODESYS application. Specifically, setting the pin direction (and, thus, the IoDrvGpioSysfs driver configuration) fails, with a rather non-descript error in the logs:</p> <table> <thead> <tr> <th>Description</th> <th>Component</th> </tr> </thead> <tbody> <tr> <td><code>Setting direction failed for GPIO pin 586</code></td> <td><code>IEC</code></td> </tr> <tr> <td><code>Update configuration failed from driver IoDrvGPIOSysfs</code></td> <td><code>CmpIoMgr</code></td> </tr> </tbody> </table> <p>I'm running CODESYS Control for Linux ARM64 SL version 4.21.0.0; it's running in rootless mode, as the <code>codesyscontrol</code> user, but said user is in the <code>gpio</code> group and can otherwise normally interact with GPIO, both via <code>gpioset</code>/<code>gpioget</code> and via the sysfs driver in <code>/sys/class/gpio/</code>.<br/> The system is a custom 64-bit Raspberry OS based distro, running on a Raspberry Pi CM5 on kernel 6.18.34 with PREEMPT_RT scheduling.</p></div>