Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR depends on meshtastic/Adafruit_nRF52_Arduino#2 but does not update the firmware dependency on that package since that PR isn't merged yet.
This is a draft/RFC PR. There are some parts of this PR i'm uncertain about and would especially like feedback/guidance on:
#include <nrfx_wdt.c>inmain-nrf52.c. Is there a better way to optionally compile/link C code from packages pulled in as dependencies, asframework-arduinoadafruitnrf52is?NRFX_*architecture configs should go somewhere else, not at the top ofmain-nrf52.c.src/platform/nrf52/architecture.hmaybe?nrfx_wdt_init()and beforenrfx_wdt_enable(). I'd like some day to have an architecture-agnostic way to let each thread have its own watchdog channel, which (on nrf52 at least) would require delaying enabling the wdt until all the thread setup is done. The split-setup convolution is in preparation for that future.🤝 Attestations