-> I updated my raspberry pi3 with runtime 4.22.0.0, and then no I2C device is running.
-> when i switch back to runtime 4.20.0.0 all I2C devices running.
what have i additionally to do, so that I2C Bus is although running in the newest Runtime Version 4.22.0.0 ?
I did read something about security changes on the new runtime Version, but i do not clear
understand, what i have do do, do bring the I2C Bus to live again ?
... there should be a Dialog in the Runtime Deploy tool, (see the link below) , but im my
Codesys Version 3.5.22.40 i could not find this "Change Service User button" ...
CODESYSControl_User.cfg [CmpCharDevice]
PermittedPath.0=/dev/i2c
PermittedPath.1=/dev/spidev
PermittedPath.2=/sys/class/gpio/
PermittedPath.3=/dev/gpiochipPerm
will be solved to 4.23.0.0 release
Last edit: eschwellinger 5 hours ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi together,
-> I updated my raspberry pi3 with runtime 4.22.0.0, and then no I2C device is running.
-> when i switch back to runtime 4.20.0.0 all I2C devices running.
what have i additionally to do, so that I2C Bus is although running in the newest Runtime Version 4.22.0.0 ?
I did read something about security changes on the new runtime Version, but i do not clear
understand, what i have do do, do bring the I2C Bus to live again ?
... there should be a Dialog in the Runtime Deploy tool, (see the link below) , but im my
Codesys Version 3.5.22.40 i could not find this "Change Service User button" ...
https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html
strange things happen, so what to do, any Ideas appreciated !
CODESYSControl_User.cfg
[CmpCharDevice]
PermittedPath.0=/dev/i2c
PermittedPath.1=/dev/spidev
PermittedPath.2=/sys/class/gpio/
PermittedPath.3=/dev/gpiochipPerm
will be solved to 4.23.0.0 release
Last edit: eschwellinger 5 hours ago
... the stars needed?