starred/OpenEPaperLink
1
0
Fork 0
mirror of https://github.com/OpenEPaperLink/OpenEPaperLink.git synced 2026-03-21 00:04:28 +01:00
Code Issues 472 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #310] Support for Solum M3 2.7" Newton BWR - EL027H3BRA #179

New Issue
Closed
opened 2026-03-20 17:27:34 +01:00 by sascha_hemi · 5 comments
sascha_hemi commented 2026-03-20 17:27:34 +01:00
Owner
Copy Link

Originally created by @olanwe on GitHub (May 5, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/310

Is your feature request related to a problem? Please describe.
I have a new M3 2.7" tag here (EL027H3BRA) and flashed SOL_M3_Uni_full_0027 on it. The device is booting up (green LED flashing, Display is refreshing), but nothing (apart from a thin colored "garbage" line on the far right of the display) is being displayed. However, the tag is polling regularly, so the firmware seems to be running normal.

EL027H3BRA_1
EL027H3BRA_2

Information as seen by the AP:

0000051D098E0006
M2 1.54"
152x152 fw:39 0x27
CH 26, RSSI -37, LQI 255, 3.163V

So both the tags MAC-address is inccorrect (original address is 051D098EB490) and both type and resolution are wrong.
Dump of UICR:
m3_27_i_051d098eb490.bin.log

Originally created by @olanwe on GitHub (May 5, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/310 **Is your feature request related to a problem? Please describe.** I have a new M3 2.7" tag here (EL027H3BRA) and flashed SOL_M3_Uni_full_0027 on it. The device is booting up (green LED flashing, Display is refreshing), but nothing (apart from a thin colored "garbage" line on the far right of the display) is being displayed. However, the tag is polling regularly, so the firmware seems to be running normal. ![EL027H3BRA_1](https://github.com/jjwbruijn/OpenEPaperLink/assets/7893408/20e46fd9-91ec-4769-921f-bb10624e073f) ![EL027H3BRA_2](https://github.com/jjwbruijn/OpenEPaperLink/assets/7893408/2c408555-77ef-4f73-b471-25311f202565) Information as seen by the AP: ``` 0000051D098E0006 M2 1.54" 152x152 fw:39 0x27 CH 26, RSSI -37, LQI 255, 3.163V ``` So both the tags MAC-address is inccorrect (original address is 051D098E**B490**) and both type and resolution are wrong. Dump of UICR: [m3_27_i_051d098eb490.bin.log](https://github.com/jjwbruijn/OpenEPaperLink/files/15212815/m3_27_i_051d098eb490.bin.log)
sascha_hemi added the enhancement label 2026-03-20 17:27:34 +01:00
sascha_hemi commented 2026-03-20 17:27:35 +01:00
Author
Owner
Copy Link

@krikkirk commented on GitHub (Aug 12, 2024):

Hi there, I dont have the same tag. You can try modifying this line and the line below to 300 and 200. It will manually tell OEPL that this tag has the correct resolution.
And modify this line to STYPE_SIZE_026 so it will show solum 2.6 in your AP. See if the splash screen works as expected.

<!-- gh-comment-id:2284562837 --> @krikkirk commented on GitHub (Aug 12, 2024): Hi there, I dont have the same tag. You can try modifying[ this line ](https://github.com/OpenEPaperLink/Tag_FW_nRF52811/blob/main/tag_fw/hal/Newton_M3_nRF52811/tagtype_db.cpp#L113C17-L113C24)and the line below to 300 and 200. It will manually tell OEPL that this tag has the correct resolution. And modify this [line](https://github.com/OpenEPaperLink/Tag_FW_nRF52811/blob/main/tag_fw/hal/Newton_M3_nRF52811/tagtype_db.cpp#L80) to STYPE_SIZE_026 so it will show solum 2.6 in your AP. See if the splash screen works as expected.
sascha_hemi commented 2026-03-20 17:27:35 +01:00
Author
Owner
Copy Link

@olanwe commented on GitHub (May 1, 2025):

I just noticed that the tag is supported by the latest M3 firmware now, so this issue can be closed.

<!-- gh-comment-id:2845015708 --> @olanwe commented on GitHub (May 1, 2025): I just noticed that the tag is supported by the latest M3 firmware now, so this issue can be closed.
sascha_hemi commented 2026-03-20 17:27:35 +01:00
Author
Owner
Copy Link

@michilehr commented on GitHub (May 25, 2025):

@olanwe which firmware did you flash to get it working? Did you also flash the UICR
I have the samel problem and alrady flashed 0029 - but does not work.

<!-- gh-comment-id:2908028185 --> @michilehr commented on GitHub (May 25, 2025): @olanwe which firmware did you flash to get it working? Did you also flash the UICR I have the samel problem and alrady flashed 0029 - but does not work.
sascha_hemi commented 2026-03-20 17:27:35 +01:00
Author
Owner
Copy Link

@olanwe commented on GitHub (May 25, 2025):

@olanwe which firmware did you flash to get it working? Did you also flash the UICR I have the samel problem and alrady flashed 0029 - but does not work.

Hi @michilehr, I flashed the one available here: https://github.com/OpenEPaperLink/Tag_FW_nRF52811/tree/main/tag_fw

I made a backup of the infopage first but I did not have to use it. As the tag was already running with the old firmware (i.e. logging into the AP but only displaying a thin noise line) it was even sufficient to do an over-the-air update using the OTA-version (Newton_M3_Universal-ota.bin) to get it working.

<!-- gh-comment-id:2908062429 --> @olanwe commented on GitHub (May 25, 2025): > [@olanwe](https://github.com/olanwe) which firmware did you flash to get it working? Did you also flash the UICR I have the samel problem and alrady flashed 0029 - but does not work. Hi @michilehr, I flashed the one available here: https://github.com/OpenEPaperLink/Tag_FW_nRF52811/tree/main/tag_fw I made a backup of the infopage first but I did not have to use it. As the tag was already running with the old firmware (i.e. logging into the AP but only displaying a thin noise line) it was even sufficient to do an over-the-air update using the OTA-version ([Newton_M3_Universal-ota.bin](https://github.com/OpenEPaperLink/Tag_FW_nRF52811/blob/main/tag_fw/Newton_M3_Universal-ota.bin)) to get it working.
sascha_hemi commented 2026-03-20 17:27:36 +01:00
Author
Owner
Copy Link

@michilehr commented on GitHub (May 26, 2025):

@olanwe which firmware did you flash to get it working? Did you also flash the UICR I have the samel problem and alrady flashed 0029 - but does not work.

Hi @michilehr, I flashed the one available here: https://github.com/OpenEPaperLink/Tag_FW_nRF52811/tree/main/tag_fw

I made a backup of the infopage first but I did not have to use it. As the tag was already running with the old firmware (i.e. logging into the AP but only displaying a thin noise line) it was even sufficient to do an over-the-air update using the OTA-version (Newton_M3_Universal-ota.bin) to get it working.

Nice. I have just used your Dump of the UICR and it works. Thanks for sharing!

<!-- gh-comment-id:2908781734 --> @michilehr commented on GitHub (May 26, 2025): > > [@olanwe](https://github.com/olanwe) which firmware did you flash to get it working? Did you also flash the UICR I have the samel problem and alrady flashed 0029 - but does not work. > > Hi [@michilehr](https://github.com/michilehr), I flashed the one available here: https://github.com/OpenEPaperLink/Tag_FW_nRF52811/tree/main/tag_fw > > I made a backup of the infopage first but I did not have to use it. As the tag was already running with the old firmware (i.e. logging into the AP but only displaying a thin noise line) it was even sufficient to do an over-the-air update using the OTA-version ([Newton_M3_Universal-ota.bin](https://github.com/OpenEPaperLink/Tag_FW_nRF52811/blob/main/tag_fw/Newton_M3_Universal-ota.bin)) to get it working. Nice. I have just used your Dump of the UICR and it works. Thanks for sharing!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
88MZ100 FW
ARM Tag FW
ap fw
bug
documentation
enhancement
good first issue
nRF FW
pull-request
Mirrored from GitHub Pull Request
 question
tag fw
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sascha_hemi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#179
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?