Fully agree that, a 8 or 16 M psram will significantly enhance the experience of Cardputer ADV, but shortage of GPIO could be a major problem. Maybe we could a version of ADV with S31 in the future.

Привет, разобрался? такая же тема после прошивки

@lishi 我CoreS3+GPSv2.1，一样的，只要loop里更新label就会闪退重启。不止是GPS，用LoRaWAN-EU868也会这样。老哥有找到原因吗？

Your RFID 2 module is likely not broken. The "Failed authenticating" error is the key clue here. Mifare 1KB cards use sector-based authentication with crypto keys. Bruce (and most generic RFID readers) will attempt the default keys (e.g. FF FF FF FF FF FF or A0 A1 A2 A3 A4 A5) to authenticate, but if FlipperZero or NFC Tools wrote data using custom or non-default keys, authentication will fail even though the UID and card type are read correctly. Things to try: Test with a blank/factory card. If it reads fine, your module is working. Check what keys were used when writing via FlipperZero or NFC Tools and make sure Bruce is configured to use those same keys. If the card was written with default keys, try a different card; it may have been locked or write-protected. The fact that UID, ATQA, and SAK are being detected correctly strongly suggests the module is functional.

Additional finding: Secondary firmware bug — boot sequence crash on cold boot (MEPC: 0x00000006) While investigating the sta.scan() crash, I discovered a second distinct firmware bug affecting the Tab5 in UIFlow2 v2.4.4. Description: On every cold boot, the device crashes during UIFlow2's initialization sequence before any user code runs. The device automatically reboots and boots successfully on the second attempt. Crash signature: Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled. MEPC : 0x00000006 MCAUSE : 0x00000001 MTVAL : 0x00000006 Key observation: The stack contains 0x7474696c (ASCII: "litt") pointing to a crash inside UIFlow2's LittlevGL/LVGL initialization sequence — not in user code. Reproducibility: 100% reproducible on cold boot Device always self-recovers on automatic reboot Completely independent of user code — happens before any user application starts This is a separate bug from issue #94 (sta.scan() at MEPC: 0x4ff13582). Both bugs share the same root environment (UIFlow2 v2.4.4 on Tab5) but occur at different stages and involve different subsystems.

@Aleximdh same settings on mine, have you tried it on diff wifi?

Hi, this would do the work https://github.com/ThatsLucas/M5Unit-ACMeasure-Internal-FW You need to reflash it though

@johnericsutton Hello, i had the same issue and fixed it on my github, you can use it : https://github.com/ThatsLucas/M5Unit-ACMeasure-Internal-FW

UIFlow2.4.4でも挙動が変わっていないのですが、ご参考として情報共有します。 Write characterの表示位置はそれぞれ下記のようになっているようです。 0：一番左の桁 1：一番左の桁の小数点 2：左から二番目の桁 3：左から二番目の桁の小数点 4：コロン したがって、下記のように書いた場合、LEDの表示は"0.1.:"となります。 [image: 1778318692419-d24bad0f-0fc2-402c-8409-b966be4aa725-image.jpeg] ドキュメントにはDigiClockUnit.set_charのindex（表示位置）は0~4までとなっていますが、上記の挙動からすると本来は0~8まで必要と思われます。 （強制的に5~8を指定しても0~3の扱いになってしまい、左側2桁しか表示されません） 以上、特に新しいネタは無いのですがご参考でした。