Hi,
I'm still trying to find reason for crashes of my Via Eden cpu, details in this thread:
https://forum.tinycorelinux.net/index.php?topic=28270.30During the investigation I found that setting a watchdog using wdt boot option does not work on TC17.1.
I have installed watchdog-6.18.35-tinycore.tcz
But wdt kernel option is not recognized:
Kernel command line: BOOT_IMAGE=/tce/boot/vmlinuz171R2 quiet host=huis cron consoleblank=0 wdt tz=CET-1CEST,M3.5.0,M10.5.0/3 waitusb=5:UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113" tce=UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113" reserve_mem=4M:4096:ramoops ramoops.mem_name=ramoops ramoops.record_size=1048576 ramoops.console_size=1048576 initrd=/tce/boot/rootfs171.gz,/tce/boot/modulesR2.gz,/tce/boot/8139report2.gz
Unknown kernel command line parameters "cron wdt host=huis tz=CET-1CEST,M3.5.0,M10.5.0/3 waitusb=5:UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113" tce=UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113"", will be passed to user space.I now have the hardware watchdog operational by using some commands in my bootlocal.sh:
# install watchdog and wait until device ready
sudo modprobe via_wdt; while [ ! -c /dev/watchdog1 ]; do sleep 1; done
# Keep the watchdog device open and service it every 10 seconds
( exec 3>/dev/watchdog1 || exit 1; while true; do printf 'K' >&3 || exit 1; sleep 10; done ) &This works. I have tested it by interrupting the printf-stream, system nicely reboots.
However....
This should have been operational by wdt boot option and it isn't
(or my understanding is too marginal)
Note, I'm using a custom kernel that has persistant ram active but I cannot imagine that is the reason.