- Home
- Skills
- Agents & Orchestration
- i2c uart spi enum
Works with the AI Agents you already use
i2c uart spi enum
Cross-platform hardware bus discovery and diagnostic tool for I2C, UART, and SPI interfaces.
Free
i2c uart spi enum
Example session with this skill installed
Scan all I2C devices on /dev/i2c-1 and list all available UART ports with their VID and PID in JSON format.
- Read your context and instructions
- Compiled the i2c uart spi
I have scanned the system for I2C and UART peripherals. I found one I2C adapter with an active device at 0x48 and two UART ports, including an FTDI USB-to-Serial adapter.
Hardware Enumeration Results
{
"platform": "linux",
"python": "3.11.2",
"buses": ["i2c", "uart"],
"ok": true,
"warnings": [],
"i2c": {
"supported": true,
"adapters": [
{
"device": "/dev/i2c-1",
"bus": 1,
"adapter_name": "bcm2835 I2C adapter",
"readable": true,
"writable": true,
"probe": {
"addresses_scanned": 112,
"found": ["0x48"],
"detail": {"0x48": "ack"},
"warnings": {}
}
}
],
"clients": [{"bus": 1, "address": "0x68", "name": "rtc", "driver": "rtc-ds1307"}],
"notes": []
},
"uart": {
"supported": true,
"backend": "pyserial",
"ports": [
{
"device": "/dev/ttyUSB0",
"description": "USB Serial",
"hwid": "USB VID:PID=0403:6001",
"vid": "0x0403",
"pid": "0x6001",
"serial_number": "A1234567",
"manufacturer": "FTDI",
"product": "FT232R USB UART"
},
{
"device": "/dev/ttyS0",
"description": "ttyS0",
"hwid": "PNP0501",
"vid": null,
"pid": null
}
],
"notes": []
}
}
Next steps
- Check if the device at I2C address
0x48matches your expected peripheral (e.g., ADS1115 or TMP102). - If
0x68is busy (listed underclients), use thertc-ds1307driver to interact with it instead of raw I2C. - Use
/dev/ttyUSB0for your serial communication, as it is the identified FTDI hardware.
Connects securely to your tools. The creator never sees your data.
About this skill
Hardware developers and embedded engineers often struggle to identify which I2C, UART, or SPI devices are actually visible to the OS versus what is physically wired. This skill provides a cross-platform (Linux, macOS, Windows) enumeration tool that scans buses, identifies serial ports with full metadata, and performs safe address probing to verify hardware connectivity.
What it does
- Multi-bus enumeration discovers active I2C adapters, UART/COM ports, and SPI controllers across different operating systems.
- I2C address scanning performs safe probing via
i2c-devioctl to map out responding peripheral addresses. - Detailed serial metadata extracts VID/PID, serial numbers, and manufacturer strings using
pyserialwhen available. - SPI loopback testing validates SPI bus integrity by verifying TX/RX consistency (requires MOSI-MISO short).
- Permissions auditing checks read/write access for device nodes and identifies
i2cordialoutgroup membership issues. - JSON-first output generates machine-readable bus maps for downstream automation or integration with controller scripts.
How it works
- Passive Scan: Run
--bus all --jsonto list all exposed OS device nodes and system-level bus controllers. - Permission Check: Identify nodes with
readable=falseand follow provided instructions to fixudevrules or user groups. - Active Probing: Execute
--probefor I2C or--loopbackfor SPI to confirm physical hardware presence and wiring. - Environment Setup: Use the provided platform-specific commands to install optional dependencies like
smbus2orpyserialon the host.
Frameworks & tools
The tool runs on Python 3.8+ using standard library ioctl and sysfs calls. It integrates with pyserial for advanced UART discovery and smbus2 for SMBus-compliant probing.
Why this beats prompting it yourself
Generic AI prompts often output non-existent Linux commands or hallucinate bus structures. This skill uses a specialized Python bridge that handles platform-specific quirks, such as Windows COM port registry paths versus Linux by-id symlinks, while maintaining strict read-only safety by default.
Use cases
- Identify which
/dev/ttyUSBnode corresponds to a specific FTDI or CH341 chip via VID/PID. - Verify if a new I2C sensor is correctly wired and responding at its expected hex address.
- Debug missing SPI nodes in containerized environments by checking
node_visibilityflags.
Known limitations
Does not support I2C/SPI on macOS or Windows without dedicated vendor USB bridges. Cannot perform register-level read/write or driver installation. Requires host-side Python environment.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
No I2C/SPI support on macOS/Windows (platform restriction). Cannot load kernel modules or modify device trees. Probing I2C may interfere with active drivers.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 10 days ago
- Free with an Agensi account
- Software
Python