ATC_BLE_OEPL Uploader

BLE Connection

E-Paper prefix filter(s): Remember last device

Debug CMD (Hex):

Set Device Type (Preset):

Select Firmware:

BLE ADV Interval:

Custom MAC (Hex, 8 Bytes):

NFC commands –

PIN Protection

PIN – lock –

PIN:

Locks BLE, not NFC. Kept in RAM, so a reboot clears it. An unlock lasts 60 s of silence and at most 600 s.

HW Config

Display Settings

Special Screen Type:

OEPL Type (Hex):

Controller:

Width: Height:

Width Offset: Height Offset:

Colors(Exc. White):

Invert W/H for BLE

Invert W/H Display

Invert Black Invert 2nd Color

GUI Rotation:

EPD Pinout

RESET:

DC:

BUSY:

BUSYs:

CS:

CSs:

CLK:

MOSI:

ENABLE:

ENABLE1:

FLASH_CS:

Invert ENABLE Pin

Pull CFG Sleep:

Pull ENABLE:

Pull ENABLE Sleep:

LED Pinout

NFC Pinout

External Flash Pinout

Other Pins

ADC Pin:

UART TX Pin:

LUT Playground

UC VCOM LUT Reg 0x20
UC W2W LUT Reg 0x21
UC B2W LUT Reg 0x22
UC W2B LUT Reg 0x23
UC B2B LUT Reg 0x24
UC Border LUT Reg 0x25

SSD LUT Reg 0x32

Raw LUT Data (Hex):

NFC

What a phone meets when it is held against the tag: the message it reads without any app, and the command channel an app uses to talk to the tag the way this page does over BLE.

chip – commands –

The message a tap reads

Kind:

Written to flash and kept across reboots. Clearing puts the tag's own default message back rather than leaving a phone with nothing to read.

Command channel

The same switch as under Protection, where it sits with the PIN – both decide who may command this tag, so changing one without seeing the other is how a tag ends up half shut. Kept here too because this is where someone working on NFC looks.

Diagnostics

Which NFC IC is fitted is detected at runtime, so the address and register layout below come from the tag, not from an assumption here. Recover clocks a jammed bus free and scans for the chip again – the device address of some NFC ICs lives in their own writable EEPROM, so a chip can legitimately move.

Tag Info

Readout

not read yet

One command and one answer: what firmware is running, what it is measuring, what panel, flash and NFC chip it has, and which modes are on. A plain command, not the debug channel – reading a tag's vital signs should not go through something that can also erase it.

Debug

Latest Reading

Battery Voltage: N/A

ADC RAW: N/A

ADC Temperature: N/A

EPD Temperature: N/A

Last Updated: N/A

Direct access to memory, peripheral and analog registers, flash, GPIO, I2C and the panel, through BLE_CMD_DEBUG (0x001B). There is no undo. The firmware area of the flash is write protected at every boot, so a stray write there does nothing until you lift the protection on purpose; everything else is yours to break. The same commands also work over NFC.

System

Memory and peripheral registers

Space Address Bytes Width

Jump to

Write

Fill elements of

Search bytes from the address for

Watch repeat every ms — shows only the bytes that changed

Analog registers

Address Bytes Write

Internal flash

Address Bytes

Write

Protection — unlocked, a wrong address bricks the tag until you reflash over SWS

GPIO

auto refresh — click a pin to toggle it

Pin Function output input Pull

Pulse ms (capped at 200)

I2C

Device (8 bit write addr) Reg bytes Register Bytes

Write

NFC

Moved to its own NFC tab, together with the message a tap reads and the command channel.

Panel

Command Data Read back

UART Flasher

1. USB-COM: Baud: Activation:

Set Device Type:

2. Firmware:

3. Actions: Open COM & Select file

Tag log (live) closed

Follow the end

Everything the tag would have printed on its UART. Opening this box tells the tag to send it as it is printed; closing it tells the tag to stop. Nothing is polled in between, so a quiet tag costs no traffic at all, and what it sends is dropped from its buffer on the way out, so nothing arrives twice. The tag switches it off by itself whenever the link drops, which is why it is always off after a reconnect until this box is opened again.