fdcavalcanti opened a new issue, #17384: URL: https://github.com/apache/nuttx/issues/17384
### Description / Steps to reproduce the issue Hi folks, Seems the change on #17381 is causing the ESP32 to not boot anymore. Issue can be easily seem on target and on QEMU: ``` $ qemurun esp32 Running QEMU for esp32... Adding SPI flash device ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3ffb2080,len:7616 load:0x40080000,len:33660 entry 0x40082b58 *** Booting NuttX *** I (713) boot: chip revision: v3.0 I (716) boot.esp32: SPI Speed : 40MHz I (716) boot.esp32: SPI Mode : DIO I (716) boot.esp32: SPI Flash Size : 4MB I (723) boot: Enabling RNG early entropy source... dram: lma 0x00001020 vma 0x3ffb2080 len 0x1dc0 (7616) iram: lma 0x00002de8 vma 0x40080000 len 0x837c (33660) padd: lma 0x0000b178 vma 0x00000000 len 0x4e80 (20096) imap: lma 0x00010000 vma 0x400e0000 len 0x15aa8 (88744) padd: lma 0x00025ab0 vma 0x00000000 len 0xa548 (42312) dmap: lma 0x00030000 vma 0x3f410000 len 0x76e4 (30436) total segments stored 6 ABI (613) cpu_start: Pro cpu start user code I (614) cpu_start: cpu freq: 240000000 Hz I (632) spi_flash: detected chip: gd I (635) spi_flash: flash io: dio D ``` Steps to replicate: - Checkout `nuttx`: 8f91054b1d3f88d528c5327340de41d4f63c4262 - ./tools/configure.sh esp32-devkitc:nsh - make and flash Can we take a look at this or revert the PR? Thanks in advance! ### On which OS does this issue occur? [OS: Linux] ### What is the version of your OS? Mint 22 ### NuttX Version master ### Issue Architecture [Arch: xtensa] ### Issue Area [Area: Kernel] ### Host information _No response_ ### Verification - [x] I have verified before submitting the report. -- 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]
