I noticed problems between the latest version of raspbian and codesys, after an update of raspbian.
no connection pc / pi.
no raspberry reboot
and freezes raspberry.
I think this stems from a conflict between the management of the codesys and rasbian I2C service.
I did the following tests:
"The reboot requests are all from the raspberry and not from the codesy interface on PC"
raspbian installed: reboot OK
then, raspbian update: reboot ok
then, raspbian upgrade: reboot ok
then, SSH, VNC, SPI, I2C services active: reboot ok.
then, installation of runtime codesys: reboot requested, the raspberry turns off but never turns on again.
raspbian installed, update, upgrade, no VNC, SPI, I2C.
the SSH service is active.
runtime installation codesys: reboot ok
installing the codesys license: reboot ok
start runtime on raspberry: reboot ok
loading a codesys program into the raspberry: reboot ok
running the codesys program in the raspberry: reboot ok
start SPI service in raspberry: reboot ok.
SPI and I2C active in the raspberry before the start of the codesys program in the raspberry:
-no connection between the PC and the raspberry,
-and reboot the raspberry asked, the raspberry turns off but never turns on again.
SPI and I2C active in the raspberry after running the codesys program in the raspberry: reboot ok
Starting the raspberry with SPI and I2C services enabled before reboot:
running request of the codesys program on the raspberry:
no pc / raspberry connection.
and after that, it freezes raspberry.
runtime codeys installation
when the services: SSH, SPI and I2C are active on the raspberry, it is almost impossible to install the codesys runtime.
and when it's possible after several minutes of waiting,
the reboots are degraded, as before.
by enabling only SSH installation is possible.
that's what I see, I'm not a pro of lines of codes, far from it ....
if you have some ideas to follow, I'm interested.