BLE I²C + UART Console.
Send bytes. Read registers. See every bit.
Discover I²C devices
Scan addresses 0x08–0x77, then select a responding address.
Uses one-byte reads. Probing may consume data or change state on some devices. Scan only when appropriate for your target.
Transaction
Packet & connection details +
One request at a time. Reads follow writes with a repeated START. Leave write data empty for a read-only transaction, or set read count to 0 for write-only.
Reads up to 2047 bytes use one continuous I²C transaction. Larger responses arrive in 20-byte Bluetooth packets and are checked and reassembled before display. Updated firmware is required above 18 bytes.
NUS service
6e400001-b5a3-f393-e0a9-e50e24dcca9e
Open this page directly in Chrome or Edge. Disconnect the phone’s nRF Connect session first. All transactions stay in this browser tab; nothing is sent to a server.
Response
Bytes will land here
Connect and send a transaction.
Click any returned byte to inspect its bits.
Bit inspector
A closer look, one bit at a time.
I²C script & binary file
Use await i2c.write(address, bytes), i2c.read(address, count), or i2c.writeRead(address, bytes, count). Up to 32768 write bytes and 2047 read bytes per transaction. Buffer a file with await i2c.stage(file); transmit it locally with await i2c.writeStaged(address). Helpers: file, fileName, sleep(ms), log(...), progress(sent, total), ascii(text), text(bytes), hex(bytes). Run only scripts you trust.
Ready. Select a Low Region Binary for the TPS25751 example.
Activity
0UART terminal
Connect to check UART availability.
Live RX shows hex and decoded text. Keep the connection open to receive data. A send confirmation means bytes were queued; it does not confirm a reply from the target.