eren-terzioglu opened a new pull request, #17399: URL: https://github.com/apache/nuttx/pull/17399
## Summary <!-- This field should contain a summary of the changes. It will be pre-filled with the commit's message and descriptions. Adjust it accordingly --> * Documentation/risc-v/esp32[-c3|-c6|-h2]: Add PM deep sleep docs Add PM deep sleep doc support for esp32[-c3|-c6|-h2] * boards/risc-v/esp32[-c3|-c6|-h2]: Add deep sleep board support Add deep sleep board support for risc-v based Espressif chips * arch/risc-v/esp32[-c3|-c6|-h2]: Add deep sleep support Add deep sleep support for risc-v based Espressif devices ## Impact <!-- Please fill the following sections with YES/NO and provide a brief explanation --> Impact on user: Yes, deep sleep support added for <!-- Does it impact user's applications? How? --> Impact on build: No <!-- Does it impact on building NuttX? How? (please describe the required changes on the build system) --> Impact on hardware: PM mode supported for esp32c3 esp32c6 and esp32h2 <!--Does it impact a specific hardware supported by NuttX?--> Impact on documentation: Yes, newly added config docs added <!--Does it impact the existing documentation? Please provide additional documentation to reflect that--> Impact on security: No <!--Does it impact NuttX's security?--> Impact on compatibility: No <!--Does it impact compatibility between previous and current versions? Is this a breaking change?--> ## Testing <!-- Please provide all the testing procedure. Consider that upstream reviewers should be able to reproduce the same testing performed internally --> Used configs: ``` esp32c3-generic:pm esp32c6-devkitc:pm esp32h2-devkit:pm ``` ### Building <!--Provide how to build the test for each SoC being tested--> Command to build: ``` make -j distclean && ./tools/configure.sh esp32c6-devkitc:pm && make -j && make download ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BAUD=921600 ESPTOOL_BINDIR=./ ``` ### Running <!--Provide how to run the test for each SoC being tested--> To let device into deep-sleep mode, these commands applied: ``` nsh> pmconfig relax standby nsh> pmconfig relax idle nsh> pmconfig relax normal nsh> pmconfig relax normal ``` ### Results <!--Provide tests' results and runtime logs--> After these commands applied, device will stop responding to `nsh` and after a while it will restart with `DSLEEP` or `SLEEP_WAKEUP` reset reason. Here is the log for esp32c6: ``` nsh> pmconfig relax standby nsh> pmconfig relax idle nsh> pmconfig relax normal nsh> pmconfig relax normal nsh> up_idlepm: newstate= 3 oldstate=0 ESP-ROM:esp32c6-20220919 Build:Sep 19 2022 rst:0x5 (SLEEP_WAKEUP),boot:0xc (SPI_FAST_FLASH_BOOT) SPIWP:0xee mode:DIO, clock div:2 load:0x40800000,len:0x96d4 load:0x408096e0,len:0x2c1c load:0x50000000,len:0x74 SHA-256 comparison failed: Calculated: cec7898d3414bfdcdfe71b8ca31fa38129f8eeecf92c569ea7c6f0c9a27633cb Expected: 00000000503c0000000000000000000000000000000000000000000000000000 Attempting to boot anyway... entry 0x4080936e *** Booting NuttX *** I (53) boot: chip revision: v0.1 I (54) boot: efuse block revision: v0.3 I (54) boot.esp32c6: SPI Speed : 80MHz I (54) boot.esp32c6: SPI Mode : DIO I (58) boot.esp32c6: SPI Flash Size : 4MB I (62) boot: Enabling RNG early entropy source... dram: lma 0x00000020 vma 0x40800000 len 0x96d4 (38612) dram: lma 0x000096fc vma 0x408096e0 len 0x2c1c (11292) rtc: lma 0x0000c320 vma 0x50000000 len 0x74 (116) padd: lma 0x0000c3a8 vma 0x00000000 len 0x3c50 (15440) imap: lma 0x00010000 vma 0x42030000 len 0x12080 (73856) padd: lma 0x00022088 vma 0x00000000 len 0xdf70 (57200) imap: lma 0x00030000 vma 0x42000000 len 0x25890 (153744) total segments stored 7 ABCDI (115) cpu_start: Pro cpu start user code I (115) cpu_start: cpu freq: 160000000 Hz I (115) spi_flash: detected chip: generic I (115) spi_flash: flash io: dio E NuttShell (NSH) NuttX-10.4.0 nsh> ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
