starred/OpenEPaperLink
1
0
Fork 0
mirror of https://github.com/OpenEPaperLink/OpenEPaperLink.git synced 2026-03-21 00:04:28 +01:00
Code Issues 472 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #214] Problems with MiniAP and SD-Card #2326

New Issue
Closed
opened 2026-03-20 21:05:33 +01:00 by sascha_hemi · 4 comments
sascha_hemi commented 2026-03-20 21:05:33 +01:00
Owner
Copy Link

Originally created by @seeers on GitHub (Feb 1, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/214

I soldered an SD card slot to the MiniAP and adapted the Platformio.ini accordingly:

board_build.partitions = esp32_sdcard.csv
and added the following buildflags:
-D HAS_SDCARD
-D USE_SOFTSPI
-D SD_CARD_SS=38
-D SD_CARD_CLK=40
-D SD_CARD_MISO=37
-D SD_CARD_MOSI=39

Changed 'VSPI' to 'HSPI' in storage.cpp, erased the Flash, build and uploaded the compiled FW.

I can connect to the APs wifi, unfortunately the status is initializing...
Sometimes the AP reboots / crashes when I refresh the page http://192.168.0.4 with F5 (Windows sound for new hardware / COM port found)
The segmented display shows IP addr., then nothing follows.

Access to the SD card works via http://192.168.4.1/edit

Have I made a fundamental mistake or could it be a bug?
Does anyone else use an ESP32-S2 with Segmented Display as a radio and an SD card?

init
Serial output:

| AP Info - type F0       |
| Ch   |             0x0B |
| Power|               0A |
| MAC  | 840B2D9150650131 |
| Ver  |           0x0017 |
[WiFi-event 12]
[WiFi-event 14]
>AP Segmented Data 840B2D9150650131
queue item added, first in line, total 1 elements
ACK>
XFC>Waiting for valid time from NTP-server
[WiFi-event 14] 
>AP Segmented Data 840B2D9150650131
queue item added, total 2 elements
>AP Segmented Data 840B2D9150650131
queue item added, total 3 elements
>SDA 840B2D9150650131
queue item added, total 4 elements
AP FW version 0017 - AP_FW_Segmented_UK.bin found in FW pack
Waiting for valid time from NTP-server
Waiting for valid time from NTP-server
Waiting for valid time from NTP-server
Waiting for valid time from NTP-server
pingACK> ok, 4ms
ADR>pingACK> ok, 4ms

Log.txt:

           00:00:03 No connection information saved
           00:00:03 Starting configuration AP, ssid OpenEPaperLink
           00:00:03 Reboot. Reason: Power-on
           00:00:03 No connection information saved
           00:00:03 Starting configuration AP, ssid OpenEPaperLink
           00:00:03 Reboot. Reason: Power-on
           00:00:03 No connection information saved
           00:00:03 Starting configuration AP, ssid OpenEPaperLink
           00:00:03 Reboot. Reason: Power-on
           00:02:00 No connection information saved
           00:02:00 Starting configuration AP, ssid OpenEPaperLink
           00:02:00 Reboot. Reason: Task Watchdog
           00:07:17 No connection information saved
           00:07:17 Starting configuration AP, ssid OpenEPaperLink
           00:07:17 Reboot. Reason: Panic
           00:00:03 No connection information saved
           00:00:03 Starting configuration AP, ssid OpenEPaperLink
           00:00:03 Reboot. Reason: Power-on
Originally created by @seeers on GitHub (Feb 1, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/214 I soldered an SD card slot to the MiniAP and adapted the Platformio.ini accordingly: board_build.partitions = esp32_sdcard.csv and added the following buildflags: -D HAS_SDCARD -D USE_SOFTSPI -D SD_CARD_SS=38 -D SD_CARD_CLK=40 -D SD_CARD_MISO=37 -D SD_CARD_MOSI=39 Changed 'VSPI' to 'HSPI' in storage.cpp, erased the Flash, build and uploaded the compiled FW. I can connect to the APs wifi, unfortunately the status is initializing... Sometimes the AP reboots / crashes when I refresh the page http://192.168.0.4 with F5 (Windows sound for new hardware / COM port found) The segmented display shows IP addr., then nothing follows. Access to the SD card works via http://192.168.4.1/edit Have I made a fundamental mistake or could it be a bug? Does anyone else use an ESP32-S2 with Segmented Display as a radio and an SD card? ![init](https://github.com/jjwbruijn/OpenEPaperLink/assets/16150580/e2262168-f7b1-49e3-966d-f96773933b03) Serial output: ``` | AP Info - type F0 | | Ch | 0x0B | | Power| 0A | | MAC | 840B2D9150650131 | | Ver | 0x0017 | [WiFi-event 12] [WiFi-event 14] >AP Segmented Data 840B2D9150650131 queue item added, first in line, total 1 elements ACK> XFC>Waiting for valid time from NTP-server [WiFi-event 14] >AP Segmented Data 840B2D9150650131 queue item added, total 2 elements >AP Segmented Data 840B2D9150650131 queue item added, total 3 elements >SDA 840B2D9150650131 queue item added, total 4 elements AP FW version 0017 - AP_FW_Segmented_UK.bin found in FW pack Waiting for valid time from NTP-server Waiting for valid time from NTP-server Waiting for valid time from NTP-server Waiting for valid time from NTP-server pingACK> ok, 4ms ADR>pingACK> ok, 4ms ``` Log.txt: ``` 00:00:03 No connection information saved 00:00:03 Starting configuration AP, ssid OpenEPaperLink 00:00:03 Reboot. Reason: Power-on 00:00:03 No connection information saved 00:00:03 Starting configuration AP, ssid OpenEPaperLink 00:00:03 Reboot. Reason: Power-on 00:00:03 No connection information saved 00:00:03 Starting configuration AP, ssid OpenEPaperLink 00:00:03 Reboot. Reason: Power-on 00:02:00 No connection information saved 00:02:00 Starting configuration AP, ssid OpenEPaperLink 00:02:00 Reboot. Reason: Task Watchdog 00:07:17 No connection information saved 00:07:17 Starting configuration AP, ssid OpenEPaperLink 00:07:17 Reboot. Reason: Panic 00:00:03 No connection information saved 00:00:03 Starting configuration AP, ssid OpenEPaperLink 00:00:03 Reboot. Reason: Power-on ```
sascha_hemi added the bug label 2026-03-20 21:05:33 +01:00
sascha_hemi commented 2026-03-20 21:05:33 +01:00
Author
Owner
Copy Link

@titijack commented on GitHub (Feb 9, 2024):

I faced exactly the same issue with a 1.54" ESL. It was 3 weeks ago, so I don't remember well. I tried to debug but didn't find the issue. It seems the first init steps ran (files are copied on the SDCard) but with kernel panics and reboot loops.
I wanted to extend this nanoAP storage for my daughter to avoid to upload images to HA and use the api etc... and I find the UI of the AP easy to use and user friendly enough to manage custom drawings, embedded features (like calendars) and image upload / applied as static images.

<!-- gh-comment-id:1935886848 --> @titijack commented on GitHub (Feb 9, 2024): I faced exactly the same issue with a 1.54" ESL. It was 3 weeks ago, so I don't remember well. I tried to debug but didn't find the issue. It seems the first init steps ran (files are copied on the SDCard) but with kernel panics and reboot loops. I wanted to extend this nanoAP storage for my daughter to avoid to upload images to HA and use the api etc... and I find the UI of the AP easy to use and user friendly enough to manage custom drawings, embedded features (like calendars) and image upload / applied as static images.
sascha_hemi commented 2026-03-20 21:05:34 +01:00
Author
Owner
Copy Link

@jonasniesner commented on GitHub (Feb 17, 2024):

To be honest the SD card code is not really tested because no currently supported APs support it. Why do you need an SD card?

<!-- gh-comment-id:1950304472 --> @jonasniesner commented on GitHub (Feb 17, 2024): To be honest the SD card code is not really tested because no currently supported APs support it. Why do you need an SD card?
sascha_hemi commented 2026-03-20 21:05:34 +01:00
Author
Owner
Copy Link

@seeers commented on GitHub (Feb 18, 2024):

I use relatively large vlw fonts with icons, so I didn't have much space left on the filesystem. I also suspected that the memory area had been corrupted. (little space and many updates)
So I wanted to try out the option with the SD card.
In the meantime I have changed to a ttf font, now there is more space on a new esp32-s2.

Nevertheless I find the SD option interesting to save write cycles of the internal flash.

<!-- gh-comment-id:1950992266 --> @seeers commented on GitHub (Feb 18, 2024): I use relatively large vlw fonts with icons, so I didn't have much space left on the filesystem. I also suspected that the memory area had been corrupted. (little space and many updates) So I wanted to try out the option with the SD card. In the meantime I have changed to a ttf font, now there is more space on a new esp32-s2. Nevertheless I find the SD option interesting to save write cycles of the internal flash.
sascha_hemi commented 2026-03-20 21:05:34 +01:00
Author
Owner
Copy Link

@jonasniesner commented on GitHub (Mar 2, 2024):

I am closing this for now since we have no capacity to work on this at the moment and no "official" AP uses it at the moment. Feel free to work on it yourself though.

<!-- gh-comment-id:1974862690 --> @jonasniesner commented on GitHub (Mar 2, 2024): I am closing this for now since we have no capacity to work on this at the moment and no "official" AP uses it at the moment. Feel free to work on it yourself though.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
88MZ100 FW
ARM Tag FW
ap fw
bug
documentation
enhancement
good first issue
nRF FW
pull-request
Mirrored from GitHub Pull Request
 question
tag fw
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sascha_hemi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2326
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?