Go to file

Sebastian Hugentobler 75544904a5 i2c addresses go only up to 127		2024-05-22 08:51:18 +02:00
.cargo	initial commit	2024-05-20 15:32:00 +02:00
src	i2c addresses go only up to 127	2024-05-22 08:51:18 +02:00
.gitignore	initial commit	2024-05-20 15:32:00 +02:00
build.rs	initial commit	2024-05-20 15:32:00 +02:00
Cargo.lock	initial commit	2024-05-20 15:32:00 +02:00
Cargo.toml	initial commit	2024-05-20 15:32:00 +02:00
deny.toml	initial commit	2024-05-20 15:32:00 +02:00
flake.lock	initial commit	2024-05-20 15:32:00 +02:00
flake.nix	initial commit	2024-05-20 15:32:00 +02:00
LICENSE	0BSDS license, basically PD	2024-05-20 15:34:16 +02:00
memory.x	initial commit	2024-05-20 15:32:00 +02:00
README.md	typo in readme	2024-05-20 15:35:59 +02:00
rust-toolchain.toml	initial commit	2024-05-20 15:32:00 +02:00

nRF52840 DK I²C Scanner

Quick and simple program to scan for used I²C addresses on an nRF52840 DK.

Setup

Connect I²C as follows:

GND -> GND
VCC -> VDD
SDA -> P0.03
SCL -> P0.04

Either use nix and enter the dev shell with nix develop or ensure that at least the following is installed:

Attach the dev-kit with USB, turn it on and run probe-rs list to verify the connection. It should show something akin to the following:

The following debug probes were found:
[0]: J-Link (J-Link) (VID: 1366, PID: 1051, Serial: 001050288663, JLink)

Run cargo run to compile the software and flash it. The resulting output will tell you at which addresses I²C devices were found.

Example output with a device at 0x27

0.014221 INFO  i2c device at 0x27