fdcavalcanti opened a new pull request, #17257: URL: https://github.com/apache/nuttx/pull/17257
## Summary - arch/xtensa: update SPI Flash driver for ESP32-S2|S3 Updates the SPI Flash driver used for user storage MTD. Moves ESP32 and ESP32S3 to use common driver. Updates KConfig options to keep backwards compatibility. - arch/risc-v: update SPI Flash driver for ESP32-C3|C6|H2 Updates the SPI Flash driver used for user storage MTD. Updates board linker script and bring up. ## Impact - Impact on user: No. - Impact on build: No. - Impact on hardware: This modifications affects ESP32-S2|S3|C3|C6|H2. - Impact on documentation: No. - Impact on security: No. - Impact on compatibility: Compatibility issues are mitigated in the following manner: Selecting ESP32_SPIFLASH automatically select ESPRESSIF_SPIFLASH and ESPRESSIF_MTD. Selecting ESP32S3_SPIFLASH automatically selects ESPRESSIF_SPIFLASH. Selecting ESP32S3_MTD automatically selects ESPRESSIF_MTD. SPIRAM and PARTITION_TABLE configs still make use of the now legacy SPI Flash driver on ESP32S3. ## Testing Tested extensively with fstest on all affected SoCs. ### Building This can be replicated to all SoCs: - ./tools/configure.sh esp32s3-devkit:spiflash - Enable CONFIG_TESTING_FSTEST - build and flash ### Running On first boot from a erased flash, an error should show up suggesting the partition is formatted: ``` EERROR: Failed to mount the FS volume: -19 Smartfs seems unformatted. Did you run 'mksmartfs /dev/smart0'? ERROR: Failed to setup smartfs ERROR: Failed to initialize SPI Flash ``` Do as instructed (mksmartfs /dev/smart0) and reboot. The /data directory should now be available. Run fstest. ### Results ``` nsh> fstest -n 30 -o 50 -m /data [...] Final memory usage: VARIABLE BEFORE AFTER DELTA ======== ======== ======== ======== arena 4e628 4e628 0 ordblks 2 2 0 mxordblk 2cf80 2cf80 0 uordblks 5ac8 5ac8 0 fordblks 48b60 48b60 0 File system tests done... OK: 60, FAILED: 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]
