Post your output here and say when you got the board. We are seeing two different ID's on the ribbbon cable. The TEST3 TEST4 one seems to be newer.
#MagTag 2025 read.py output
royal imp
Program to run:
My output, with a board I just got, with markings like the second picture:
0x1B (temperature) ['0x7f', '0xf0']
display option reg 0x2d ['0x0', '0x28', '0x80', '0x40', '0x0', '0x0', '0x40', '0x0', '0x0', '0x0', '0x0']
user id 0x2e ['0x44', '0x0', '0x4', '0x0', '0x25', '0x0', '0x1', '0x78', '0x2b', '0xe']```I expect the temperature values to vary. But the 0x2d and 0x2e values might be the same or different. Thanks.
crimson dew
I purchased my Magtag 2025 in November 2025 and it has the ribbon cable marking on the first picture (i.e. FPC-A005 and no TestN).
Adafruit CircuitPython 10.0.3 on 2025-10-17; Adafruit MagTag with ESP32S2
>>>
soft reboot
Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
0x1B (temperature) ['0x7f', '0xf0']
display option reg 0x2d ['0x0', '0x28', '0x40', '0x20', '0x10', '0x0', '0x40', '0x1', '0x0', '0x0', '0x0']
user id 0x2e ['0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0']
Code done running.
Let me know if you want me to do any additional testing.
And, of course, it does not exhibit the bottom row of noise pixels.
royal imp
@neat jay could you try this on the one you just got as well, to see if it's the same as mine?
neat jay
@royal imp
Adafruit CircuitPython 10.1.1-1-ge43c59c9d6 on 2026-02-18; Adafruit MagTag with ESP32S2
>>> import read
0x1B (temperature) ['0x7f', '0xf0']
display option reg 0x2d ['0x0', '0x28', '0x80', '0x40', '0x0', '0x0', '0x40', '0x0', '0x0', '0x0', '0x0']
user id 0x2e ['0x44', '0x0', '0x4', '0x0', '0x25', '0x0', '0x1', '0x78', '0x2b', '0xe']
>>>
so same as mine, good sign, thanks, we could use some testing of older 2025 generation ones now
neat jay
older old original magtag:
Adafruit CircuitPython 10.0.3 on 2025-10-17; Adafruit MagTag with ESP32S2
>>> import read
0x1B (temperature) ['0x0', '0x0']
display option reg 0x2d ['0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff']
user id 0x2e ['0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff', '0xff']
>>>
that is the non-SSD1680, so those non-existent values make sense
we could change the current register test to try reading 0x2e instead of 0x71 and get the same info
stuck dawn
I get this output:
code.py output:
0x1B (temperature) ['0x7f', '0xf0']
display option reg 0x2d ['0x0', '0x28', '0x40', '0x20', '0x10', '0x0', '0x40', '0x1', '0x0', '0x0', '0x0']
user id 0x2e ['0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0', '0x0']
MagTag purchased July 2025.
Ribbon cable says FPC-A005 20.06.15 TRX
crimson dew
I get this output:
```
code.py output:
0x1B (temperature) ['0x7f', '0xf0']
displ...
Same as mine purchased November 2025 so we have a rough set of dates for the 'original' 2025 SSD1680.
royal imp
Based on this data, I've made a PR:
Here is a build to test: https://github.com/adafruit/circuitpython/actions/runs/22164035178/artifacts/5565641843. I've tested on original MagTag (non-SSD1680), and the recent MagTag (needs colstart-8). If someone with a November 2025 purchase could test and see that there is no junk at the bottom of the screen, thank you.
See https://github.com/adafruit/circuitpython/issues/10835 for details and pictures. PR is https://github.com/adafruit/circuitpython/pull/10836
crimson dew
All pixels display correctly with build CircuitPython 10.2.0-alpha.1-1-g31dd19b058 on my November 2025 purchased MagTag.