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 #218] Tags stuck on 'Updating' when going from 36 (0x24) to 38 (0x26) #3435

New Issue
Closed
opened 2026-03-20 23:05:30 +01:00 by sascha_hemi · 2 comments
sascha_hemi commented 2026-03-20 23:05:30 +01:00
Owner
Copy Link

Originally created by @ThinkPadNL on GitHub (Feb 4, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/218

Describe the bug
M2 tags are stuck on black screen 'Updating!' and do not come back online when updating from 0x24 to 0x26

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'advanced settings'
  2. Click on 'auto update'
  3. Tag changes to 'updating!'
  4. Tag is not coming back online again, bricked?

Expected behavior
Update succeeding and tag coming back online

Additional context
Looks same issue as #184 but my tags were already on v24

Guess i'm up to reflashing them in flashing jig?

Originally created by @ThinkPadNL on GitHub (Feb 4, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/218 **Describe the bug** M2 tags are stuck on black screen 'Updating!' and do not come back online when updating from 0x24 to 0x26 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'advanced settings' 2. Click on 'auto update' 3. Tag changes to 'updating!' 4. Tag is not coming back online again, bricked? **Expected behavior** Update succeeding and tag coming back online **Additional context** Looks same issue as #184 but my tags were already on v24 Guess i'm up to reflashing them in flashing jig?
sascha_hemi added the bug label 2026-03-20 23:05:30 +01:00
sascha_hemi commented 2026-03-20 23:05:31 +01:00
Author
Owner
Copy Link

@jonasniesner commented on GitHub (Feb 5, 2024):

Hi, yea, you will most likely have to reflash with a jig. The bricking protection is only active starting with the firmware you where trying to update to. Try removing the batteries and inserting them back after shorting the pins first.

<!-- gh-comment-id:1926325280 --> @jonasniesner commented on GitHub (Feb 5, 2024): Hi, yea, you will most likely have to reflash with a jig. The bricking protection is only active starting with the firmware you where trying to update to. Try removing the batteries and inserting them back after shorting the pins first.
sascha_hemi commented 2026-03-20 23:05:31 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Feb 8, 2024):

The bug that would cause corrupted transfers is fixed in version 0x25, so in 0x24 it still could go wrong.
If they are stuck on 'Updating', using a jig to reflash will be the only option sadly.

<!-- gh-comment-id:1934472925 --> @nlimper commented on GitHub (Feb 8, 2024): The bug that would cause corrupted transfers is fixed in version 0x25, so in 0x24 it still could go wrong. If they are stuck on 'Updating', using a jig to reflash will be the only option sadly.
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 bug
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#3435
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?