From 476fc04d5b073427f1e9a64e016c7d6c781b059f Mon Sep 17 00:00:00 2001 From: Jelmer Date: Thu, 25 Jan 2024 20:26:50 +0100 Subject: [PATCH] Updated M3 Tag Firmware changelog (markdown) --- M3-Tag-Firmware-changelog.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/M3-Tag-Firmware-changelog.md b/M3-Tag-Firmware-changelog.md index a836a7e..de08dd0 100644 --- a/M3-Tag-Firmware-changelog.md +++ b/M3-Tag-Firmware-changelog.md @@ -1,11 +1,12 @@ ## 0026 - Universal FW -Incorporates Jonas' changes for LED control -Fixed 4.3" shutdown routine -All M3 tags should now be able to use the same binary file -Tag type, EPD type is determined in the 'customer' UICR data as set in factory +- Incorporates Jonas' changes for LED control +- Fixed 4.3" shutdown routine +- All M3 tags should now be able to use the same binary file +- Tag type, EPD type is determined in the 'customer' UICR data as set in factory HOWEVER: We haven't checked all types! I have been trying to determine how the tag finds out what kind of controller the EPD uses, and I may have gotten it all wrong! I -highly- suggest only updating tags one-at-a-time, and only if you want to try the new features. + If you want to help, dump the UICR from a tag, and let me know what type of tag is is/controller it uses. ## 0024 - Feature parity ##