# Supporting for a board based on NXP i.MX 8M MINILPD4-EVK?

**URL:** <https://forums.balena.io/t/supporting-for-a-board-based-on-nxp-i-mx-8m-minilpd4-evk/5613>\
**Category:** Product support\
**Tags:** support\
**Created:** [March 13, 2019, 2:43pm UTC](https://forums.balena.io/t/supporting-for-a-board-based-on-nxp-i-mx-8m-minilpd4-evk/5613 "2019-03-13T14:43:52Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![TJvV](https://avatars.discourse-cdn.com/v4/letter/t/858c86/32.png) [@TJvV](https://forums.balena.io/u/TJvV)\
**Post date:** [September 26, 2023, 7:35am UTC](https://forums.balena.io/t/supporting-for-a-board-based-on-nxp-i-mx-8m-minilpd4-evk/5613/39 "2023-09-26T07:35:34Z")

</div>

Hi,

Your log ends with

```auto
systemd-journald.service: Got notification message from PID 753 (WATCHDOG=1)
systemd-udevd.service: Got notification message from PID 782 (WATCHDOG=1)

```

Could it be related to the watchdog?  
In a [different thread](https://forums.balena.io/t/watchdog-restarts-the-device-during-a-release-update/56834) there was a link to the [watchdog configuration](https://github.com/balena-os/meta-balena/blob/master/meta-balena-common/recipes-core/systemd/systemd/watchdog.conf); maybe increasing the timeout might help? Are you certain the hardware (not software) watchdog is properly cleared?  
The original thread was about a raspberry pi; you may need to look around and twiddle some things to handle the i.MX hardware watchdog.

---

_[View the full topic](https://forums.balena.io/t/supporting-for-a-board-based-on-nxp-i-mx-8m-minilpd4-evk/5613)._
