Read and control sensors, displays, and other peripherals on Sipeed boards through I2C and SPI, two hardware communication interfaces. Find connected devices, prepare shared pins, and troubleshoot wiring, permissions, and communication settings.
Read and control I2C and SPI peripherals on Sipeed boards (LicheeRV Nano, MaixCAM, NanoKVM).
Review the instructions the agent will receive before you install.
Use the i2c and spi tools to interact with sensors, displays, and other peripherals connected to the board.
# 1. Find available buses
i2c detect
# 2. Scan for connected devices
i2c scan (bus: "1")
# 3. Read from a sensor (e.g. AHT20 temperature/humidity)
i2c read (bus: "1", address: 0x38, register: 0xAC, length: 6)
# 4. SPI devices
spi list
spi read (device: "2.0", length: 4)
Most I2C/SPI pins are shared with WiFi on Sipeed boards. You must configure pinmux before use.
See references/board-pinout.md for board-specific commands.
Common steps:
/etc/init.d/S30wifi stopmodprobe i2c-devdevmem (board-specific)i2c detect and i2c scanconfirm: true — always confirm with the user firstSee references/common-devices.md for register maps and usage of popular sensors:
AHT20, BME280, SSD1306 OLED, MPU6050 IMU, DS3231 RTC, INA219 power monitor, PCA9685 PWM, and more.
| Problem | Solution |
|---|---|
| No I2C buses found | modprobe i2c-dev and check device tree |
| Permission denied | Run as root or add user to i2c group |
| No devices on scan | Check wiring, pull-up resistors (4.7k typical), and pinmux |
| Bus number changed | I2C adapter numbers can shift between boots; use i2c detect to find current assignment |
| WiFi stopped working | I2C-1/SPI-2 share pins with WiFi SDIO; can't use both simultaneously |
devmem not found | Download separately or use busybox devmem |
| SPI transfer returns all zeros | Check MISO wiring and device power |
| SPI transfer returns all 0xFF | Device not responding; check CS pin and clock polarity (mode) |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automate website navigation, form entry, button clicks, and data extraction using the agent-browser command-line tool. Capture screenshots or PDFs, reuse login sessions, and inspect page elements while checking web application behavior.
Use the GitHub command-line tool to inspect issues, pull requests, and automated workflow runs. Check failed steps and logs, retrieve additional details through the API, and extract selected fields into structured results.
Set up, debug, and extend PicoClaw using its own commands and configuration structure. Get guidance on model authentication, external tool connections, scheduled tasks, and how conversations are routed and stored.
Turn repeated workflows into reusable Picoclaw skills, or update and review existing ones. Organize SKILL.md instructions, scripts, reference documents, and output assets, then check the structure and test representative tasks.
Summarize articles, local files, YouTube videos, and podcasts to review their main points. Adjust the summary length, or extract available text and transcripts from URLs when you need the source content.
Control interactive command-line programs through tmux by sending keystrokes, reading terminal output, and waiting for prompts. Use separate sessions to operate Python consoles or run multiple coding agents while checking their progress and results.