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 #410] Tags not updating after ESP32_C6 re-flash with latest binary #3564

New Issue
Closed
opened 2026-03-20 23:06:42 +01:00 by sascha_hemi · 7 comments
sascha_hemi commented 2026-03-20 23:06:42 +01:00
Owner
Copy Link

Originally created by @Rudios81 on GitHub (Dec 11, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/410

Originally assigned to: @skiphansen on GitHub.

Describe the bug
After updating my AP to my own recompiled environment, I had issues with updating the C6 chip via OTA.
I finally managed to download the binary file from the master repository, and uploaded it onto my AP. From there I managed to update the C6 chip.
Unfortunately, none of my tags updated anymore after this update!
I have been trying to update the C6 chip many times, always got stuck at the download actions.

Finally I downloaded an older version of hte ESP32_C6 binary, the one from release 2.60 and uploaded this into my AP.
After updating the C6 chip with this binary file, some of my tags started to update immediately.

Originally created by @Rudios81 on GitHub (Dec 11, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/410 Originally assigned to: @skiphansen on GitHub. **Describe the bug** After updating my AP to my own recompiled environment, I had issues with updating the C6 chip via OTA. I finally managed to download the binary file from the master repository, and uploaded it onto my AP. From there I managed to update the C6 chip. Unfortunately, none of my tags updated anymore after this update! I have been trying to update the C6 chip many times, always got stuck at the download actions. Finally I downloaded an older version of hte ESP32_C6 binary, the one from release 2.60 and uploaded this into my AP. After updating the C6 chip with this binary file, some of my tags started to update immediately.
sascha_hemi added the bug label 2026-03-20 23:06:42 +01:00
sascha_hemi commented 2026-03-20 23:06:42 +01:00
Author
Owner
Copy Link

@collateral87 commented on GitHub (Dec 12, 2024):

I can confirm this issue. I flashed my C6 with the binary from version 2.7 and instantly the tags are working again.

<!-- gh-comment-id:2537454920 --> @collateral87 commented on GitHub (Dec 12, 2024): I can confirm this issue. I flashed my C6 with the binary from version 2.7 and instantly the tags are working again.
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@skiphansen commented on GitHub (Dec 14, 2024):

Thanks for the report! I've posted a new C6 image to the help_and_questions topic on Discord, please give it a try and let us know if it resolves the problem or not.

Thanks!

<!-- gh-comment-id:2543197218 --> @skiphansen commented on GitHub (Dec 14, 2024): Thanks for the report! I've posted a new C6 image to the help_and_questions topic on Discord, please give it a try and let us know if it resolves the problem or not. Thanks!
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@Boorte commented on GitHub (Dec 15, 2024):

I can also confirm the issue, however with some additional issues. I updated to latest FW (2.60b -> 2.75) on my yellow AP and all tags stopped working (was working fine before), however rolling back to previous FW did not make the tags work again. I've been trying to upgrade/downgrade, update filesystem and tag definitions/DB but nothing seems to help. The status of the AP says failed.

<!-- gh-comment-id:2543844116 --> @Boorte commented on GitHub (Dec 15, 2024): I can also confirm the issue, however with some additional issues. I updated to latest FW (2.60b -> 2.75) on my yellow AP and all tags stopped working (was working fine before), however rolling back to previous FW did not make the tags work again. I've been trying to upgrade/downgrade, update filesystem and tag definitions/DB but nothing seems to help. The status of the AP says failed.
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Dec 15, 2024):

If the status of the AP shows 'failed', don't mess with the ESP32-S3 firmware, filesystem, tag, or other things. In that case, focus on the ESP32-C6 firmware, because the 'failed' status indicates that's not working correctly.

<!-- gh-comment-id:2543845095 --> @nlimper commented on GitHub (Dec 15, 2024): If the status of the AP shows 'failed', don't mess with the ESP32-S3 firmware, filesystem, tag, or other things. In that case, focus on the ESP32-C6 firmware, because the 'failed' status indicates that's not working correctly.
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@Boorte commented on GitHub (Dec 15, 2024):

The ESP32-C6 update failes with the message "Packet could not be written!" and "Flashing failed. :-(".
I guess I have to find the old C6 firmware from 2.60b as well

<!-- gh-comment-id:2543846469 --> @Boorte commented on GitHub (Dec 15, 2024): The ESP32-C6 update failes with the message "Packet could not be written!" and "Flashing failed. :-(". I guess I have to find the old C6 firmware from 2.60b as well
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@Rudios81 commented on GitHub (Dec 16, 2024):

Thanks for the report! I've posted a new C6 image to the help_and_questions topic on Discord, please give it a try and let us know if it resolves the problem or not.

Thanks!

I can confirm that the version supplied on the discord discussion does solve the problem!

<!-- gh-comment-id:2545608127 --> @Rudios81 commented on GitHub (Dec 16, 2024): > Thanks for the report! I've posted a new C6 image to the help_and_questions topic on Discord, please give it a try and let us know if it resolves the problem or not. > > Thanks! I can confirm that the version supplied on the discord discussion does solve the problem!
sascha_hemi commented 2026-03-20 23:06:43 +01:00
Author
Owner
Copy Link

@skiphansen commented on GitHub (Dec 16, 2024):

Thanks for reporting the problem and testing the fix!

<!-- gh-comment-id:2545776258 --> @skiphansen commented on GitHub (Dec 16, 2024): Thanks for reporting the problem and testing the fix!
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#3564
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?