Open plouflechien opened 1 year ago
Hello ! The chip is compatible with the custom firmware, but the screen driving part isn't working as it should. I've got a bunch of these, and have the same problem. The flashing works, for debug, you can use the TXD pin on the ESL to the RXD on the USB flasher. Tried changing model with e00X over BLE does work, but the screen doesn't update with any model number. I've tried to debug it a bit, but could not guess what was wrong with the SSD1680 / 1675 addresses. Or if it's the right place to look. Sadly i'm not good enough at coding to figure it out.
Some other models won't work either for the same reason, like the nebular. ATC1441 said he's too busy to work on it at the time, hopefully someone will make it work one day.
I Have a bunch of smaller Stellar Pro-154-NP (same series as the 213-N) that do work without issues !
And Thanks to ATC1441, and all the people who worked on this, i have a blast playing around with these ESL, i'm using them with an RPI to display a temperature probe on my beer tanks at my brewery !
Cheers !
Hello ! I got my hands of a bunch of Stellar Pros too. I managed to flash and use the BLE features. However the screen does not update as mentioned in OP. So I've been digging info and tinkering. Thanks to the work of all, here's what I managed to get :
So, before sharing this, I tried another approach : I extracted the original firmware, and try to reverse it, in the hope of getting some low level info on how the screen is driven. This task has also hurdles, but so far I managed to load the code in ghidra, disassemble it using https://github.com/trust1995/Ghidra_TELink_TC32/tree/master and start understanding the structure of the code (I think the same SDK is being used, I found similarities in the objects layout). However, there's still a lot to be done.
I just wanted to share this, just in case, and in the hope that someone will revive the subject with me, or get some advices on the best way to figure this out.
Cheers !
Hello, https://github.com/Reletiv/OpenEPaperLink_TLSR in folder [Stellar_2.13_BWR_PRO] are working files for Stellar Pro-213R-N
Hello, https://github.com/Reletiv/OpenEPaperLink_TLSR in folder [Stellar_2.13_BWR_PRO] are working files for Stellar Pro-213R-N
Hi!
Did you just flash the file from https://github.com/Reletiv/OpenEPaperLink_TLSR/blob/main/Stellar_2.13_BWR_PRO/STELLAR_PRO_2.13_BWR.bin and it worked with Stellar Pro-213R-N?
After flashing, I can't see the BLE device, the screen refreshes showing white letters on a black background (which is the opposite of everywhere I've seen) with the content AP Found...
Hi!
I did not use the binary directly. Instead I merged parts of the code (mainly the screen driver) with my own source.
Attached is my working version. It supports the web tool for OTA and sending images including in 3-color. The BLE device name should begin with THX_. This firmware IS NOT the OpenEPaper version compatible with AP, but the original one from atc1441 working only on Stellar Pro 213R,
I provide this with no further support as I stopped research on these devices.
Hi!
I did not use the binary directly. Instead I merged parts of the code (mainly the screen driver) with my own source.
Attached is my working version. It supports the web tool for OTA and sending images including in 3-color. The BLE device name should begin with THX_. This firmware IS NOT the OpenEPaper version compatible with AP, but the original one from atc1441 working only on Stellar Pro 213R,
I provide this with no further support as I stopped research on these devices.
Hi, sure! thanks a lot for the answer and the binary :)
@thxomas I have two more questions if I may:
EDIT : I really had this project out of my mind, sorry ! I forgot that I used this similar project and adapted it for 213-pro : https://github.com/reece15/stellar-L3N-etag Sorry for any time loss !
If you're interested I may share my codebase
Ok, that's what I thought, but I wasn't sure, because you mentioned old software for Stellar Pro 213R and it's not visible in the description of this repository and I thought that there was another repository :)
Sure! you can share it, maybe I will fix it for my tags, if not me then surely someone will find it useful!:)
@thxomas Hi, I was hoping you could help me a moment. I flashed the binary in ATC_Paper.zip in your comment of 23rd of August onto my Stellar Pro Epaper and it is working fine. I was hoping that the binary in "https://github.com/reece15/stellar-L3N-etag" would also work on my epaper but it doesn´t. Would it be possible to for you to share your codebase to create the ATC_Paper.bin from you comment of 23rd of August? You offered this to @belkone in your previous comment but it seems at the end you didn´t do it.
Hi ! You're right, I did not follow up my sharing proposal. Better late than never, here it is !
stellar3_etag_bwr_thxomas_src.zip
(the zip includes only the src folder, to be merged with your local repo of the @reece15 project).
FYI :
I'm happy that this work still generates interest and I may end up setting up a correctly forked repo on github.
Hello, I have some not well known "Stellar Pro-213R-N "
The chip TLSR8359 seems to be elligible to be hacked, but the screen is 250x122 and it has 3 colors (BW+red). Connecting to serial, seems to work (blue led is flashing while sending commands to it), but I can't say if it's working : any hint to read any output/debug from this ESL ?