-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stellar Pro-213R-N - firmware flashing failed #40
Comments
Hello ! 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 !
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, |
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, |
@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 ! 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. |
For me the flashing works with Baud 115200. I set the Atime to 8 secs to give me more time. After hitting "unlock flash" I quickly (within the 8 secs of Atime) connect Rst to ground for a moment. Then I hit "flash firmware" and quickly connect the Rst to ground again for a moment. This way it is working for me. It is important to use the src folder from thxomas to replace the src folder in https://github.com/reece15/stellar-L3N-etag. Otherwise the Pro version of the epaper was not working for me. |
If I replace the src folder from thxomas in atc1441’s code, make.exe stops right after this line. |
Hi, https://github.com/pvvx/TlsrComSwireWriter The cabling is slighlty different and it makes use of the RTS pin to reset the chip and flash before it boots the firmware (RTS is not available on all USB-to-UART adapters). I remember having to enable the RTS/CTS feature on the Pi too. it requires some hardware you may not have at your disposal but I remember being stuck like you with an ESP board (worked only once). Hope this helps |
I actually have a Raspberry Pi 4 Model B. Unfortunately, I can’t access the link you attached. Thanks a lot! |
Edit : corrected the link in my previous post |
Hi, if you want to use with Open Epaperlink then below fork works well with Stellar Pro 213R-N: https://github.com/Reletiv/OpenEPaperLink_TLSR/tree/main/Stellar_2.13_BWR_PRO |
Hello! I finally managed to do it. I think the problem was with the browser I was using. Chrome is the right one. However, I still have issues with the colors, but I think it’s good enough for me. I believe the issues are already known. I noticed there’s also an offset on the left side. However, I’m attaching some pictures. Thank you very much for your help. |
Hi there, |
Hello everyone ! |
OpenEpaperLink doesn’t work with the tool you want to use. Read the comments above. thxomas explained it very well, and it worked for me. |
Thank you so much for your fast answer ! I merged the firmware from https://github.com/reece15/stellar-L3N-etag with the code provided by thxomas and it worked like a charm with Reece15 tools. The only issue that I have is that my image is shifted to the right and the colors are inverted (only black and white, red is fine) I'll look at it but if you have an idea on how to solve this issue I will be pleased ! |
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 ?
The text was updated successfully, but these errors were encountered: