Francesco Dolcini wrote:
On Fri, Mar 10, 2023 at 02:43:33PM +0100, Andreas Aegerter wrote:
This config is based on colibri_imx6_defconfig and enables additionally the watchdog. The intend of the new config is that distros can use this in the future and the behaviour will not be changed for
current users. IMO in general is a bad idea to duplicate a defconfig for the same board, you just duplicate the maintenance effort.
However I am not sure if it would be OK, to just enable the watchdog in the existing colibri_imx6_defconfig. Any suggestions?
I wonder what would be the implication of enabling it by default on the general defconfig.
One implication of this is that if the kernel does not support the watchdog and therefore does not reset it regularly, the system will reboot every 128 seconds. That's the main reason why I propose creating a new defconfig.
What about using a debugger or kgdb from Linux? What is the watchdog timeout once you enable it? Can we be sure that the OS will be able to start in time to refresh the watchdog?
Timeout is 128 seconds (default value if CONFIG_WATCHDOG_TIMEOUT_MSECS is not set). This should be enough to boot an embedded device. For debugger I recommend to use an u-boot image where the watchdog is not enabled.
Francesco
Andreas