stm32mp1 watchdog command line test

[Ara.1]

Hi All,

i am getting watchdog Device or resource busy in stm32mp1

root@mp1som:~# dmesg | grep watchdog

[   2.108020] iwdg 5a002000.watchdog: unable to set timeout value, using default

[   3.642347] iwdg 5a002000.watchdog: timeout skrinked to 1

[   3.647585] systemd[1]: Hardware watchdog 'STM32 Independent Watchdog', version 0

[   3.654887] systemd[1]: Set hardware watchdog to 30s.

root@mp1som:~# echo V > /dev/watchdog

-sh: can't create /dev/watchdog: Device or resource busy

root@mp1som:~#

[KnarfB]

How did you build your image? What version? Changes / additions? What mp1som?

[Ara.1]

Its customized image built using yocto, following distro is the details

NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION          = "1.42.0"

BUILD_SYS           = "x86_64-linux"

NATIVELSBSTRING     = "universal"

TARGET_SYS          = "arm-openstlinux_weston-linux-gnueabi"

MACHINE             = "stm32mp1som"

DISTRO              = "openstlinux-weston"

DISTRO_VERSION      = "2.7-snapshot-20210104"

TUNE_FEATURES       = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"

TARGET_FPU          = "hard"

DISTRO_CODENAME     = "warrior"

GCCVERSION          = "8.%"

PREFERRED_PROVIDER_virtual/kernel = "linux-mp1som"

[Olivier GALLIEN]

Hi @Ara.1​ ,

Looks like you are using a custom environment ( warrior + basic boot chain from V1.2 ecosystem) on a custom design based on SOM.

I'm afraid this is too much custom to be efficiently supported in this community.

I you confirm you are using a part from SOM maker integrating STM32MP1, please be aware that the SOM maker supposed to be your favorite support contact.

If not please give more details in order we can provide relevant support.

Olivier

[Ara.1]

its working used following command

wdctl