Menu
Read and control I2C and SPI peripherals on Sipeed boards (LicheeRV Nano, MaixCAM, NanoKVM).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | hardware |
| description | Read and control I2C and SPI peripherals on Sipeed boards (LicheeRV Nano, MaixCAM, NanoKVM). |
| homepage | https://wiki.sipeed.com/hardware/en/lichee/RV_Nano/1_intro.html |
| metadata | {"nanobot":{"emoji":"🔧","requires":{"tools":["i2c","spi"]}}} |
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) |
Submit development specs, approve execution plans, monitor workers, retry failed tasks, check job status, and manage orchestration jobs. Use when asked to start a development job, check worker progress, approve a plan, retry something, or list orchestrator jobs.
Generate synthetic training data, manage seeds, preview synthesis jobs, and work with the data factory. Use when asked to generate synthetic data, create training examples, augment a dataset, manage seeds, or check factory job status.
Browse, compare, evaluate, and manage trained models. View leaderboard, trends, lineage, and artifacts. Deploy models to Ollama. Use when asked about models, model comparison, which model is best, model evaluation, deploying a model, or downloading a model.
Check BashGym system status, GPU utilization, hardware info, and aggregate statistics. Use when asked about system health, what's running, GPU usage, memory, disk space, or general system stats.
Browse, promote, demote, classify, and generate training examples from Claude Code execution traces. Use when asked about traces, gold traces, trace counts, promoting or demoting traces, generating examples, exporting training data, or syncing traces.
Start, stop, pause, resume, and monitor model training runs. Check training progress, view metrics, and get GPU utilization during training. Use when asked to train a model, check training status, view loss curves, stop a run, or see training logs.