mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 00:04:28 +01:00
[GH-ISSUE #437] Yellow AP & Gicisky BLE TFT 2.13" Blank Screen #1918
Assignees
sascha_hemi
Clear assignees
sascha_hemi
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/OpenEPaperLink#1918
Reference in New Issue
Block a user
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?
Originally created by @connoreaton3 on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/437
I have built the yellow AP following the guide and it is working fine.
I have 3 Gicisky BLE TFT 2.13" flashed with the bin file and it shows No AP Found.
The tags appear in the AP and when I send data (e.g. current date) to them the screens go blank and nothing happens.
Not sure what is going on and I am pretty new to this so any help would be massively appreciated.
@gveloce commented on GitHub (May 9, 2025):
Guys, I thought that Gicisky BLE TFT 2.13" epaper tags are natively supported by OpenEpaperLink without flashing.
Can someone confirm this as I intend to buy a few for my HA projects. TIA
@atc1441 commented on GitHub (May 9, 2025):
Hey @gveloce the TFT Variant is not supported without flashing
@gveloce commented on GitHub (May 9, 2025):
thanks @atc1441 for the light speed response!
Good to know.
What flashing is then required for it ?
I saw there is a BIN file in tag binaries TLSR_Gicisky_TFT_213.bin.
Is this the one required to flash it in order to be supported?
TIA
@connoreaton3 commented on GitHub (May 9, 2025):
I managed to finally get this fixed.
You are correct with the .bin file (https://github.com/OpenEPaperLink/OpenEPaperLink/blob/master/binaries/Tag/TLSR_Gicisky_TFT_213.bin)
I used the ATC_TLSR BLE Flasher by ATC1441 (https://atc1441.github.io/ATC_TLSR_Paper_OTA_writing.html) at first and just used BLE to connect to the display and flash the .bin file to it.
Now, at first, as mentioned above, I did end up getting things connected, but the display just displayed "No AP Found," and as soon as I sent data to it, I accidentally soft bricked it and had to buy a UART-TTL USB Adapter and use the USB-COM Flasher (https://atc1441.github.io/ATC_TLSR_Paper_UART_Flasher.html) and remove the back from the display to connect to the pins on the baord.
After I flashed it with the USB-COM Flasher, it worked perfectly, and thankfully, I have had no issues since.
@gveloce commented on GitHub (May 9, 2025):
hi @connoreaton3
thanks for the detailed response. Glad you succeeded flashing it.
But looks quite an adventure to flash it risking rendering it a (e)paperweight (joke :D) ......
Thinking maybe is better avoid buying such tag model (unless there are any easier ways to make it work with OpenEpaperLink)
Any other Tag models verified to work w/o flashing?
Cheers,
GV,
@Misiu commented on GitHub (Jul 8, 2025):
@gveloce I have GICIsky 2.9 inch display - https://s.click.aliexpress.com/e/_onWdB1u
Works great without flashing.
P.S. I'm not sure whether I should or shouldn't change the firmware, as I'm unsure of its benefits. I'll probably order another display and test the firmware on it.
@gveloce commented on GitHub (Jul 8, 2025):
@Misiu i also have the 2.9 and works fine with stock fw As they say. If ain t broken don t fix it ;)
@dennyreiter commented on GitHub (Aug 12, 2025):
How did you hook up the flasher? I can't seem to find the proper pins for this device. When I open it up, I have a row of points as follows:
GND-RX-TX-3V3-3V3-RST-SWM-SWS-GND
And did you use any old adapter, like this one:
https://www.amazon.com/HiLetgo-CP2102-Converter-Adapter-Downloader/dp/B00LODGRV8
Thanks for your help. I'm trying to keep myself amused in a hotel room :)
@Misiu commented on GitHub (Aug 12, 2025):
@dennyreiter can't you use a web-based flasher? It should just work out of the box. All you need is Bluetooth on your pc/phone.
I found flashing by phone more reliable.
@dennyreiter commented on GitHub (Aug 12, 2025):
I did do the web flashing. And the first time I try and send something from
the AP to the tag, it bricks and the screen shuts off. This happened on two
different tags, just like @connoreaton3
https://github.com/connoreaton3 described
in the issue.
On Tue, Aug 12, 2025 at 4:42 AM Tomasz @.***> wrote:
@connoreaton3 commented on GitHub (Aug 12, 2025):
I used this UART USB Adapter (https://amzn.eu/d/8WMHXgM) and then the UART USB flasher (https://atc1441.github.io/ATC_TLSR_Paper_UART_Flasher.html) to flash the display.
I just used the pins from the jumper cables and put them in the holes on the back of the display to make a connection, and it worked.
@permissionBRICK commented on GitHub (Feb 7, 2026):
To save anyone the confusion I just went through in the future, let me be a bit more specific:
I faced the exact same issue:
Gicisky tft 2.13 tag, stock firmware shows a distorted image, found this thread https://github.com/OpenEPaperLink/OpenEPaperLink/issues/383#issuecomment-2531827911
Did as instructed, flashed the firmware via the ble flasher, it showed no ap found. Realized that it would no longer work with the BLE only ap. Then got a new Lilygo-Tpanel as OEPL host, which then discovered the tag, switching the display to AP found. As soon as I sent the first command to it via OEPL, it bricked the device, showing a blank screen, even if I disconnect the battery.
Found this thread and bought the exact UART flasher: https://www.amazon.de/dp/B0B7RHPMT7
Attempted to connected as instructed here: https://github.com/atc1441/ATC_TLSR_Paper/blob/main/USB_UART_Flashing_connection.jpg (from the link in the UART Flasher: https://atc1441.github.io/ATC_TLSR_Paper_UART_Flasher.html
The attempted to use the Flasher to flash the same firmware onto the device again: connected first RX to RX and TX to TX, first mistake, the TX on the flasher is supposed to go onto the RX on the board according to the picture (EXCEPT It's not, it's actually supposed to go onto the SWS port). Next: The jumper on the flasher with S1 needs to be in the default position bridging 5v to s1. I removed the other jumper from the output terminals, and it failed again. The final config that managed to get it working was as follows:
Jumper on S1 to 3.3v,
left = flasher, right = tag
Wire from GND to one of the GND ports
Wire from 3.3v to one of the 3.3v ports
Wire from TX to the SWS port (not RX)
Wire from RST (had to thread a pin through the hole to connect that one on this flasher) going to the RST port on the tag.
Then I ran the flasher here https://atc1441.github.io/ATC_TLSR_Paper_UART_Flasher.html
Unplug the battery from the tag.
First connect all wires, hold them down to ensure connection and only then plug in USB. Also make sure the RST wire has contact at the flasher side rst port.
then open the flasher, connect to the usb serial, leave default settings: 460800 baud, 3sec Atime, select the firmware from here:
https://github.com/OpenEPaperLink/OpenEPaperLink/blob/master/binaries/Tag/TLSR_Gicisky_TFT_213.bin
First hit Unlock Flash (no idea if that is necessary but i did it)
then hit upload firmware.
Once the process hits 100%, the display came alive again!
Now disconnect everything and put it back together, plug in battery and done!
Tried sending another command through OEPL, and this time it didn't brick the device.
That was way more complicated than it needed to be lol.
Would the universal BLE firmware now also work with this tag?
@permissionBRICK commented on GitHub (Feb 11, 2026):
Update: Turns out the tag works with the new Open BLE Universal firmware from here:
https://github.com/atc1441/atc1441.github.io/blob/master/ATC_BLE_OEPL.bin
using this flasher
https://atc1441.github.io/ATC_BLE_OEPL_Image_Upload.html
with the Device Type: 13: 213 Gici BW ST.
Even connects directly to Home Assistant with the OEPL Custom Integration.
It might be possible to directly flash that firmware via the original flasher too https://atc1441.github.io/BLE_EPaper_OTA.html
and then use the new flasher to set the device type via bluetooth. I don't know. I already had the non ble custom firmware on there, so I had to flash it via UART anyway.