diff options
| author | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-09-07 00:59:02 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-09-07 00:59:02 +0300 |
| commit | 742d8bdbe46274401aa261881d14dee50a7618d5 (patch) | |
| tree | 6e3b64ac5865f92a1b23f1b4d4525184b5050cbd /esp8266/modmachine.c | |
| parent | b4be5a8f3499ca19bdc9ac3ef94625529141b0ff (diff) | |
| download | micropython-742d8bdbe46274401aa261881d14dee50a7618d5.tar.gz micropython-742d8bdbe46274401aa261881d14dee50a7618d5.zip | |
esp8266/modmachine: Map PWR_ON_RESET to vendor's REASON_DEFAULT_RST.
When dealing with a board which controls chip reset with UART's DTR/RTS,
we never see REASON_DEFAULT_RST (0), only REASON_EXT_SYS_RST (6). However,
trying a "raw" module with with just TXD/RXD UART connection, on power up
it has REASON_DEFAULT_RST as a reset reason.
Diffstat (limited to 'esp8266/modmachine.c')
| -rw-r--r-- | esp8266/modmachine.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/esp8266/modmachine.c b/esp8266/modmachine.c index df1ae0fcf6..a8d2de8bb8 100644 --- a/esp8266/modmachine.c +++ b/esp8266/modmachine.c @@ -260,7 +260,7 @@ STATIC const mp_rom_map_elem_t machine_module_globals_table[] = { { MP_ROM_QSTR(MP_QSTR_DEEPSLEEP), MP_ROM_INT(MACHINE_WAKE_DEEPSLEEP) }, // reset causes - { MP_ROM_QSTR(MP_QSTR_PWR_ON_RESET), MP_ROM_INT(REASON_EXT_SYS_RST) }, + { MP_ROM_QSTR(MP_QSTR_PWR_ON_RESET), MP_ROM_INT(REASON_DEFAULT_RST) }, { MP_ROM_QSTR(MP_QSTR_HARD_RESET), MP_ROM_INT(REASON_EXT_SYS_RST) }, { MP_ROM_QSTR(MP_QSTR_DEEPSLEEP_RESET), MP_ROM_INT(REASON_DEEP_SLEEP_AWAKE) }, { MP_ROM_QSTR(MP_QSTR_WDT_RESET), MP_ROM_INT(REASON_WDT_RST) }, |