[GH-ISSUE #367] Acces point says it's offline, then it says it's failed #215

Closed
opened 2026-03-20 17:27:53 +01:00 by sascha_hemi · 3 comments
Owner

Originally created by @Rajmi105 on GitHub (Sep 2, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/367

So when I flashed my ESP32-S2 with the Mini-AP v2, the installation went fine, I was able to connect it to my wifi, but then I see that it says that it is offline, than after some seconds it will say that it's failed.

I also looked at the terminal, and it said ping failed

I reflashed my ESP32-S2 multiple times, and I don't know how it works, please help

Originally created by @Rajmi105 on GitHub (Sep 2, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/367 So when I flashed my ESP32-S2 with the Mini-AP v2, the installation went fine, I was able to connect it to my wifi, but then I see that it says that it is offline, than after some seconds it will say that it's failed. I also looked at the terminal, and it said ping failed I reflashed my ESP32-S2 multiple times, and I don't know how it works, please help
Author
Owner

@nlimper commented on GitHub (Sep 4, 2024):

If it shows the 'failed' status, the esp32 cannot communicate with the radio module. I assume you connected a segmented tag or an esp32-C6, but in any case, check your wiring first. A segmented tag should be flashed automatically (at least, you will see attempts in the serial output), a esp32-c6, you have to flash yourself (using the 'update c6' button in the update screen).
It's not a bug, you just didn't connect the right stuff ;-)

<!-- gh-comment-id:2328168423 --> @nlimper commented on GitHub (Sep 4, 2024): If it shows the 'failed' status, the esp32 cannot communicate with the radio module. I assume you connected a segmented tag or an esp32-C6, but in any case, check your wiring first. A segmented tag should be flashed automatically (at least, you will see attempts in the serial output), a esp32-c6, you have to flash yourself (using the 'update c6' button in the update screen). It's not a bug, you just didn't connect the right stuff ;-)
Author
Owner

@Rajmi105 commented on GitHub (Sep 15, 2024):

I didn't connect a segmented tag to my ESP32 because I didn't think it was needed to make the access point usable, I just flashed my board with the software and tried to use it, because on paper the ESP32-S2 should have everything in itself that is needed for this to work.

Is it neccessary to use an e paper tag with it? If so than sorry, for not using one

And btw, no I did not connect an ESP32-C6, I am using the ESP32-S2 as written down in my issue

<!-- gh-comment-id:2351693253 --> @Rajmi105 commented on GitHub (Sep 15, 2024): I didn't connect a segmented tag to my ESP32 because I didn't think it was needed to make the access point usable, I just flashed my board with the software and tried to use it, because on paper the ESP32-S2 should have everything in itself that is needed for this to work. Is it neccessary to use an e paper tag with it? If so than sorry, for not using one And btw, no I did not connect an ESP32-C6, I am using the ESP32-S2 as written down in my issue
Author
Owner

@nlimper commented on GitHub (Sep 15, 2024):

An esp32-s2 cannot talk IEEE 802.15.4, so that's why you need two MCU's.
Also, esp32-s2 has barely enough memory, so it's advisable to use a esp32-s3 (16MB flash, 4MB psram) plus a esp32-c6.
You can find all info on how to build an access point the wiki: https://github.com/OpenEPaperLink/OpenEPaperLink/wiki

<!-- gh-comment-id:2351787273 --> @nlimper commented on GitHub (Sep 15, 2024): An esp32-s2 cannot talk IEEE 802.15.4, so that's why you need two MCU's. Also, esp32-s2 has barely enough memory, so it's advisable to use a esp32-s3 (16MB flash, 4MB psram) plus a esp32-c6. You can find all info on how to build an access point the wiki: https://github.com/OpenEPaperLink/OpenEPaperLink/wiki
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#215