mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 00:04:28 +01:00
[GH-ISSUE #536] Solum GR42003N black = grey and red = missing #3102
Assignees
sascha_hemi
Clear assignees
sascha_hemi
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/OpenEPaperLink#3102
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 @Markusenz on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/536
TAG is a Solum GR42003N with ZBS soc.
Firmware flashed is M2_ZBS_42_SSDVAR_BWR.bin version 42
When the Tag boots or receives content, during the update I can see strong black color for some moment, but when update is finished it is faded to grey. The red parts of the image are not visible at all.
Also tried "full update" setting but same result. see photo .
Voltage is stable 3.3V.
Is there a LUT setting somewhere to change, in order to get that running?
in case LUT changes between Tag versions, it would be cool to put that in the infopage?
thank you!
@atc1441 commented on GitHub (Dec 28, 2025):
Hey, that is a (most likely)broken display which can unfortunately not be fixed.
Does the original boot refresh to a nice image?
@Markusenz commented on GitHub (Dec 28, 2025):
Yes, when reverting to the original firmware, it shows all colors nicely, so the display has no hardware issue
With custom firmware, at the OEPL boot screen and the "waiting for data..." screen sometimes black looks good, but red is always missing. sometimes black is grey as in picture above. After receiving an image, it is always grey and red is also missing.
@atc1441 commented on GitHub (Dec 28, 2025):
Ok, sorry then the display does need a different initialization.
So a new firmware needs to be compiled. I remember there was a 2.9" variant with the same issue. The display is currently configured as a BW variant while being BWR
Should be somewhere here https://github.com/OpenEPaperLink/Tag_FW_ZBS243/blob/main/zbs243_shared/board/ssd-var.c#L195
Best is to sniff an original firmware refresh and compare the values to the OEPL Firmware init
@Markusenz commented on GitHub (Dec 28, 2025):
Where can I sniff (which pin and which protocol/baudrate and trigger), I can do it when I have the info.
The filename says ...BWR so I thought it would be for black white red
@atc1441 commented on GitHub (Dec 29, 2025):
Here is a sniffing how to https://youtu.be/gGNzAxeF2o4
The display you got is slightly different thats why the firmware does not fully work and needs a new one