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 #291] Bricking 2.9bw with ota from nanoAp #3484

New Issue
Closed
opened 2026-03-20 23:06:02 +01:00 by sascha_hemi · 1 comment
sascha_hemi commented 2026-03-20 23:06:02 +01:00
Owner
Copy Link

Originally created by @Carlin75 on GitHub (Apr 9, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/291

Hi
I've heard that there's a big risk of bricking the 2.9bw display when you to update the firmware on the display. Is there a chance of fixing that issue on a upcoming firmware update on the nanoAp?

My displays are st-gm29xxf (fw36, needs to be fw39😁)

Or any tips and hits on to how to update firmware over ota😁

Originally created by @Carlin75 on GitHub (Apr 9, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/291 Hi I've heard that there's a big risk of bricking the 2.9bw display when you to update the firmware on the display. Is there a chance of fixing that issue on a upcoming firmware update on the nanoAp? My displays are st-gm29xxf (fw36, needs to be fw39😁) Or any tips and hits on to how to update firmware over ota😁
sascha_hemi commented 2026-03-20 23:06:02 +01:00
Author
Owner
Copy Link

@jjwbruijn commented on GitHub (Apr 10, 2024):

If you have a tag-based AP, there's a decent chance to brick a tag running on v0024
If your tag is already running on v0025 or higher, you're safe. Since this issue is caused by a firmware bug on the tag side, there is no way to fix this on the AP side
Just to be complete: This bug can manifest itself on C6-based AP's as well, the chance is a lot smaller though

<!-- gh-comment-id:2048422294 --> @jjwbruijn commented on GitHub (Apr 10, 2024): If you have a tag-based AP, there's a decent chance to brick a tag running on v0024 If your tag is already running on v0025 or higher, you're safe. Since this issue is caused by a firmware bug on the tag side, there is no way to fix this on the AP side Just to be complete: This bug can manifest itself on C6-based AP's as well, the chance is a lot smaller though
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
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#3484
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?