How to override the default post_init function?

[konsulten]

Currently it seems the watchdogs are disabled by default in the __post_init function. Is there a possibility to override or modify this behaviour?

#763

[Dominaezzz]

I'm pretty sure you can just re-enable the watchdog in your main function. There should be an example as well.

[konsulten]

Won’t there be some time where its disabled then? I would prefer never to disable it ons 19 juni 2024 kl. 22:26 skrev Dominic Fischer ***@***.***>:

…

I'm pretty sure you can just re-enable the watchdog in your main function. There should be an example as well. — Reply to this email directly, view it on GitHub <#1698 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3FNEO5JLHYR35BEL6BIRTZIHSOPAVCNFSM6AAAAABJSP5EAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGQYTOMRYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MabezDev]

We'd probably add this behind a configuration option. We don't have a complete story for this yet see #1111.

[Dominaezzz]

For this sort of thing, rather than a config option, which can only be specified once per crate. This should probably be part of the entry macro, which can be specified once per application/binary (of which there could be multiple in a crate).

#[entry(watchdog, psram(80))]
fn main() {
    // stuff
}

I would prefer never to disable it

Not that I think this is bad to want or something, I'm just curious what you're worried about happening between the disable and re-enable? Or is this a matter of principal?

[konsulten]

Im worried that I have made a bad OTA image and get stuck in it :/ ons 19 juni 2024 kl. 22:53 skrev Dominic Fischer ***@***.***>:

…

For this sort of thing, rather than a config option, which can only be specified once per crate. This should probably be part of the entry macro, which can be specified once per application/binary (of which there could be multiple in a crate). #[entry(watchdog, psram(80))]fn main() { // stuff} I would prefer never to disable it Not that I think this is bad to want or something, I'm just curious what you're worried about happening between the disable and re-enable? Or is this a matter of principal? — Reply to this email directly, view it on GitHub <#1698 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3FNELZDHY6L4GCLARGULTZIHVVJAVCNFSM6AAAAABJSP5EAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGQ2DGOBYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MabezDev]

With the changes to how we initialize the hal, we can now make this a global configuration option. (Bear in mind this issue on the esp32 when implementing: #2105)