boards: stm32h7: nucleo-h743zi2: add watchdog

[ghost]

Summary

Add a config to test the stm32h7 watchdog

Impact

None

Testing

Builds and run

[xiaoxiang781216]

@slorquet you can try the built-in watchdog monitor instead:
https://github.com/apache/nuttx/blob/master/drivers/timers/Kconfig#L395-L464

[ghost]

Why do so? I need to control which task resets the watchdog.

[ghost]

Followup: I did that and it works.

However, it ENTIRELY masks why I got stack corruption at context switch when trying to create a kthread like I wanted to contribute. This is still worrying.

[jerpelea]

please add a proper commit title and commit message
ex
"boards: stm32h7: nucleo: add watchdog

commit message describing the change "

[ghost]

Contributing to nuttx is painful, specifically because of all these board tests that test canned config and miss new features.

[patacongo]

Contributing to nuttx is painful, specifically because of all these board tests that test canned config and miss new features.

I tend to agree. Things are not as much fun as the old days. But with so many committers and personal with absolute authority, I think we as a group of 50 or contributors need the discipline of strict process to keep things from degenerating into chaos.

[ghost]

Surely there are reasonable reasons for this.

It will limit me to critical contributions I can't avoid. Because I dont have spoons to spend beautifying pull requests when a workaround has been found.