[GH-ISSUE #316] Feature request: Support for ESP32-S3 N32R8V #2944

Closed
opened 2026-03-20 22:06:00 +01:00 by sascha_hemi · 9 comments
Owner

Originally created by @rogerjak on GitHub (May 11, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/316

I got the ESP32-S3-DevKitC-1-N32R8V and tried to flash it with the Mini-AP-v4 on https://install.openepaperlink.de but it didn't work.
Then tried compiling from source, copying the V4 and changing these to all kinds of versions, but it doesn't work.

board_build.flash_mode=dout
board_build.arduino.memory_type = opi_opi
board_build.psram_type=qspi_opi
board_upload.maximum_size = 16777216
board_upload.maximum_ram_size = 327680
board_upload.flash_size = 16MB

At first I got CRC errors, but after some tweaking I got it "working", i.e. it showed up as a Wifi AP.
But in the logs I get littlefs-errors like this:

[ 650][E][esp32-hal-spi.c:215] spiAttachMISO(): HSPI Does not have default pins on ESP32S3!
[ 1812][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation
[ 1982][E][Preferences.cpp:483] getString(): nvs_get_str len fail: ssid NOT_FOUND
[ 1983][E][Preferences.cpp:483] getString(): nvs_get_str len fail: pw NOT_FOUND
[ 2638][E][vfs_api.cpp:105] open(): /littlefs/parsers.json does not exist, no permits for creation

Any suggestions?

Originally created by @rogerjak on GitHub (May 11, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/316 I got the [ESP32-S3-DevKitC-1-N32R8V](https://eu.mouser.com/ProductDetail/Espressif-Systems/ESP32-S3-DevKitC-1-N32R8V) and tried to flash it with the Mini-AP-v4 on https://install.openepaperlink.de but it didn't work. Then tried compiling from source, copying the V4 and changing these to all kinds of versions, but it doesn't work. `board_build.flash_mode=dout` `board_build.arduino.memory_type = opi_opi` `board_build.psram_type=qspi_opi` `board_upload.maximum_size = 16777216` `board_upload.maximum_ram_size = 327680` `board_upload.flash_size = 16MB` At first I got CRC errors, but after some tweaking I got it "working", i.e. it showed up as a Wifi AP. But in the logs I get littlefs-errors like this: `[ 650][E][esp32-hal-spi.c:215] spiAttachMISO(): HSPI Does not have default pins on ESP32S3!` `[ 1812][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation` `[ 1982][E][Preferences.cpp:483] getString(): nvs_get_str len fail: ssid NOT_FOUND` `[ 1983][E][Preferences.cpp:483] getString(): nvs_get_str len fail: pw NOT_FOUND` `[ 2638][E][vfs_api.cpp:105] open(): /littlefs/parsers.json does not exist, no permits for creation` Any suggestions?
Author
Owner

@nlimper commented on GitHub (May 11, 2024):

If I remember it right, the 32MB version that you use, uses a different flash mode. The install.openepaperlink.de binaries are meant for use with the 16MB versions. But compiling it yourself should work. If you got yourself a WiFi AP, you were successfull in flashing! :-)
The errors you pasted, are to be expected with a fresh AP, and are not alarming. And sadly, vfs_api.cpp generates the 'does not exist' error already on a if fs.exists(filename) statement. So, you can safely ignore all those.

<!-- gh-comment-id:2105955412 --> @nlimper commented on GitHub (May 11, 2024): If I remember it right, the 32MB version that you use, uses a different flash mode. The install.openepaperlink.de binaries are meant for use with the 16MB versions. But compiling it yourself should work. If you got yourself a WiFi AP, you were successfull in flashing! :-) The errors you pasted, are to be expected with a fresh AP, and are not alarming. And sadly, `vfs_api.cpp` generates the 'does not exist' error already on a `if fs.exists(filename)` statement. So, you can safely ignore all those.
Author
Owner

@rogerjak commented on GitHub (May 11, 2024):

I can connect to the Wifi AP in my phone, but http://192.168.4.2/ isn't working.
And nothing more in the log than what I wrote above.

<!-- gh-comment-id:2105956544 --> @rogerjak commented on GitHub (May 11, 2024): I can connect to the Wifi AP in my phone, but http://192.168.4.2/ isn't working. And nothing more in the log than what I wrote above.
Author
Owner

@nlimper commented on GitHub (May 11, 2024):

You have to connect to the AP address, which is http://192.168.4.1

<!-- gh-comment-id:2105956828 --> @nlimper commented on GitHub (May 11, 2024): You have to connect to the AP address, which is http://192.168.4.1
Author
Owner

@rogerjak commented on GitHub (May 11, 2024):

Ah! Stupid me, tried to connect to my phone :(
Working now, thank you!

Edit: Didn't realize it had DHCP server enabled...

<!-- gh-comment-id:2105957156 --> @rogerjak commented on GitHub (May 11, 2024): Ah! Stupid me, tried to connect to my phone :( Working now, thank you! Edit: Didn't realize it had DHCP server enabled...
Author
Owner

@rogerjak commented on GitHub (May 11, 2024):

But after connecting to it and changing Wifi to my own network (working, can browse from my computer) I still get these in the log:
[ 653][E][esp32-hal-spi.c:215] spiAttachMISO(): HSPI Does not have default pins on ESP32S3! [ 1832][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 4001][E][vfs_api.cpp:105] open(): /littlefs/parsers.json does not exist, no permits for creation [ 35268][E][vfs_api.cpp:105] open(): /littlefs/www/index.html does not exist, no permits for creation [ 36193][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 69780][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 97412][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [118510][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [121070][E][vfs_api.cpp:105] open(): /littlefs/Tag_FW_Pack.bin does not exist, no permits for creation [135046][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [139689][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation

<!-- gh-comment-id:2105960672 --> @rogerjak commented on GitHub (May 11, 2024): But after connecting to it and changing Wifi to my own network (working, can browse from my computer) I still get these in the log: `[ 653][E][esp32-hal-spi.c:215] spiAttachMISO(): HSPI Does not have default pins on ESP32S3! [ 1832][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 4001][E][vfs_api.cpp:105] open(): /littlefs/parsers.json does not exist, no permits for creation [ 35268][E][vfs_api.cpp:105] open(): /littlefs/www/index.html does not exist, no permits for creation [ 36193][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 69780][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [ 97412][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [118510][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [121070][E][vfs_api.cpp:105] open(): /littlefs/Tag_FW_Pack.bin does not exist, no permits for creation [135046][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation [139689][E][vfs_api.cpp:105] open(): /littlefs/current/apconfig.json does not exist, no permits for creation`
Author
Owner

@nlimper commented on GitHub (May 11, 2024):

Read my first comment...
vfs_api.cpp generates the 'does not exist' error already on a if fs.exists(filename) statement. So, you can safely ignore all those.

<!-- gh-comment-id:2105967223 --> @nlimper commented on GitHub (May 11, 2024): Read my first comment... vfs_api.cpp generates the 'does not exist' error already on a if fs.exists(filename) statement. So, you can safely ignore all those.
Author
Owner

@rogerjak commented on GitHub (May 11, 2024):

Now I can't get the C6 radio part working.
Shouldn't it be enough with the one UART (17-2, 18-3), the debug UART isn't really needed?
I get debug prints from the C6 that it receives msgs from the tags, but the AP shows nothing :(

<!-- gh-comment-id:2106000038 --> @rogerjak commented on GitHub (May 11, 2024): Now I can't get the C6 radio part working. Shouldn't it be enough with the one UART (17-2, 18-3), the debug UART isn't really needed? I get debug prints from the C6 that it receives msgs from the tags, but the AP shows nothing :(
Author
Owner

@nlimper commented on GitHub (May 11, 2024):

All pins are needed.
And please, with all respect, don't make this github issue a personal help channel. Please try to find the problem yourself first, read and try to interpret the serial output, and see the Wiki for documentation. The connection with the C6 is straightforward, if all pins are connected to the right pins that are mentioned in the Mini-AP-v4 build platformio.ini (and also in the wiki), it works. :-) If you finally don't get it to work, provide all relevant info for us to help you.

<!-- gh-comment-id:2106006524 --> @nlimper commented on GitHub (May 11, 2024): All pins are needed. And please, with all respect, don't make this github issue a personal help channel. Please try to find the problem yourself first, read and try to interpret the serial output, and see the Wiki for documentation. The connection with the C6 is straightforward, if all pins are connected to the right pins that are mentioned in the Mini-AP-v4 build platformio.ini (and also in the wiki), it works. :-) If you finally don't get it to work, provide all relevant info for us to help you.
Author
Owner

@rogerjak commented on GitHub (May 11, 2024):

Sorry, it started out as a request to officially support the S3 N32R8V (and I still see that as legit).
But the wiki is not clear, why name some pins debug and then you tell me they're mandatory?
Will order a C6 with all pins needes, so hopefully it'll work then.
Again, sorry, won't write here no more.

<!-- gh-comment-id:2106011423 --> @rogerjak commented on GitHub (May 11, 2024): Sorry, it started out as a request to officially support the S3 N32R8V (and I still see that as legit). But the wiki is not clear, why name some pins debug and then you tell me they're mandatory? Will order a C6 with all pins needes, so hopefully it'll work then. Again, sorry, won't write here no more.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2944