At present, any SYSINIT_PANIC_ASSERT that fails in sysinit will cause the system to halt since it asserts, which might be confusing even when developing.
A custom sysinit panic assert handler should be added at the app level. I think this is the prototype, but check the Master branch which just had a bug fix for this: typedef void sysinit_panic_fn(const char *file, int line)
We can override the syscfg setting in the target or app and have it log something or send something to the console or do whatever.
See the TSL2561 driver for an example. If the driver isn't present or fails init, the system will halt.
At present, any
SYSINIT_PANIC_ASSERTthat fails in sysinit will cause the system to halt since itasserts, which might be confusing even when developing.A custom sysinit panic assert handler should be added at the app level. I think this is the prototype, but check the Master branch which just had a bug fix for this:
typedef void sysinit_panic_fn(const char *file, int line)We can override the syscfg setting in the target or app and have it log something or send something to the console or do whatever.
See the TSL2561 driver for an example. If the driver isn't present or fails init, the system will halt.