Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

sdkconfig: set CONFIG_ESP32_DEEP_SLEEP_WAKEUP_DELAY=2000 by default

Browse source 
To increase the chances that the examples work out of the box, this
change is raising the default deep sleep wakeup delay to 1ms.
If GPIO15 is low at startup, ROM code takes less time to execute
(because no logging is performed), so more time may be needed to allow
flash chip to become ready.
This commit is contained in:
Ivan Grokhotkov 2017-05-15 10:32:35 +08:00
parent 9634f1815d
commit 3c583a7655
4 changed files with 6 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
components/esp32/Kconfig
View file

@ -548,18 +548,18 @@ config ESP32_RTC_CLK_CAL_CYCLES
config ESP32_DEEP_SLEEP_WAKEUP_DELAY config ESP32_DEEP_SLEEP_WAKEUP_DELAY
int "Extra delay in deep sleep wake stub (in us)" int "Extra delay in deep sleep wake stub (in us)"
default 0 default 2000
range 0 5000 range 0 5000
help help
When ESP32 exits deep sleep, the CPU and the flash chip are powered on When ESP32 exits deep sleep, the CPU and the flash chip are powered on
at the same time. CPU will run deep sleep stub first, and then at the same time. CPU will run deep sleep stub first, and then
proceed to load code from flash. Some flash chips need sufficient proceed to load code from flash. Some flash chips need sufficient
time to pass between power on and first read operation. By default, time to pass between power on and first read operation. By default,
without any extra delay, this time is approximately 900us. without any extra delay, this time is approximately 900us, although
some flash chip types need more than that.
If you are using a flash chip which needs more than 900us to become
ready after power on, set this parameter to add extra delay By default extra delay is set to 2000us. When optimizing startup time
to the default deep sleep stub. for applications which require it, this value may be reduced.
If you are seeing "flash read err, 1000" message printed to the If you are seeing "flash read err, 1000" message printed to the
console after deep sleep reset, try increasing this value. console after deep sleep reset, try increasing this value.

1
examples/system/deep_sleep/sdkconfig.defaults
View file

@ -4,4 +4,3 @@ CONFIG_ULP_COPROC_ENABLED=y
CONFIG_ULP_COPROC_RESERVE_MEM=512 CONFIG_ULP_COPROC_RESERVE_MEM=512
CONFIG_ESP32_TIME_SYSCALL_USE_RTC_FRC1=y CONFIG_ESP32_TIME_SYSCALL_USE_RTC_FRC1=y
CONFIG_ESP32_RTC_CLOCK_SOURCE_INTERNAL_RC=y CONFIG_ESP32_RTC_CLOCK_SOURCE_INTERNAL_RC=y
CONFIG_ESP32_DEEP_SLEEP_WAKEUP_DELAY=500

3
examples/system/ulp/sdkconfig.defaults
View file

@ -1,9 +1,6 @@
# Enable ULP # Enable ULP
CONFIG_ULP_COPROC_ENABLED=y CONFIG_ULP_COPROC_ENABLED=y
CONFIG_ULP_COPROC_RESERVE_MEM=1024 CONFIG_ULP_COPROC_RESERVE_MEM=1024
# Some flash chips need extra time to wake up
# Set this a bit higher to improve out-of-the-box experience
CONFIG_ESP32_DEEP_SLEEP_WAKEUP_DELAY=500
# Set log level to Warning to produce clean output # Set log level to Warning to produce clean output
CONFIG_LOG_BOOTLOADER_LEVEL_WARN=y CONFIG_LOG_BOOTLOADER_LEVEL_WARN=y
CONFIG_LOG_BOOTLOADER_LEVEL=2 CONFIG_LOG_BOOTLOADER_LEVEL=2

3
examples/system/ulp_adc/sdkconfig.defaults
View file

@ -1,9 +1,6 @@
# Enable ULP # Enable ULP
CONFIG_ULP_COPROC_ENABLED=y CONFIG_ULP_COPROC_ENABLED=y
CONFIG_ULP_COPROC_RESERVE_MEM=1024 CONFIG_ULP_COPROC_RESERVE_MEM=1024
# Some flash chips need extra time to wake up
# Set this a bit higher to improve out-of-the-box experience
CONFIG_ESP32_DEEP_SLEEP_WAKEUP_DELAY=1000
# Set log level to Warning to produce clean output # Set log level to Warning to produce clean output
CONFIG_LOG_BOOTLOADER_LEVEL_WARN=y CONFIG_LOG_BOOTLOADER_LEVEL_WARN=y
CONFIG_LOG_BOOTLOADER_LEVEL=2 CONFIG_LOG_BOOTLOADER_LEVEL=2