-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add watchdog reset experiment #779
base: main
Are you sure you want to change the base?
Conversation
4471afb
to
e20dfd9
Compare
Should I add a P4 here as well? |
47aacaf
to
e3544c6
Compare
fn wdt_config1(&self) -> u32; | ||
} | ||
|
||
impl RtcWdtReset for crate::targets::esp32c3::Esp32c3 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would really like to avoid leaking chip-specific details like these into other modules, this all probably belongs in the targets
module.
|
||
#[cfg(feature = "serialport")] | ||
/// Check if the connection is USB OTG | ||
pub(crate) fn connection_is_usb_otg(&self, connection: &mut Connection) -> Result<bool, Error> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function feels like it belongs on the Connection
struct, so we should probably expose the necessary details from the targets
module which can then be referenced there.
This applies to the other functions in the targets
module below as well.
This is mostly experimental, so opening as a draft.
I've been playing with (cc cc #691) and I was able to reproduce the issue with espflash AND esptool as well, following the same steps as mentioned here
I looked into esptool and specifically to this commit.
esptool
not using this fix as default for SERIAL_JTAG, it can be used manually with:--after reset_watchdog
The reasons (from esptool perspective) it's not on by default are: