How to prevent bootloop?

[Elleshar]

Good morning community,

as far as we can estimate it, there is a little confusion on our side.
https://media.video.bosch.com/media/%5BEN%5D+ctrlX+AUTOMATION+Application+Tutorial+%7C+SDK+%7C+3+Rea...
In the video the experts mentions a possible boot loop when creating your own realtime bundles.
Is there any new information about it?
In the documentation there is a guide to how to disable the hardware-watchdog.
But the phrase: "Disabling the monitoring can be persistent." is a bit confusing.
How can we disable it persistent?

Looking forward for an answer.
Sincerely Elleshar

[nickH · Accepted solution]

Hello Elleshar,

While developing your own realtime bundles, you should disable the hardware-watchdog like it is shown in the documentation. Otherwise you are not able to debug your code, because the hardware watchdog would trigger an error response (reboot) when reaching a breakpoint. Further running into an endless loop in your bundle-application would lead to a boot loop triggered by the hardware watchdog.

But if you are done with developing and your app is finished. You should be able to run your app on your CORE with a activated hardware watchdog.

The phrase: "Disabling the monitoring can be persistent." is a bit misleading. If you disabled your hardware watchdog it is persistent (still disabled after reboot). So the debug mode is active until you delete the created node. See here how to deactivate the debug mode again. 

Regards,

Nick

[Elleshar]

Thanks Nick

[Elleshar]

Hi again Nick, at the documentation there is an issue

POST https://192.168.1.1:443/automation/api/v1.0/scheduler/admin/controls

{
  "control_type": "debug",
  "control": {
    "machine": "123456789"
  }
}

the D of debug must written in uppercase. Otherwise it don't work.

Sincerely Elleshar 

[nickH]

Hi Elleshar,

thanks for reporting this issue. 

I passed on the issue and hope the docu gets adjusted soon.

Regards

Nick