Protocol
Bulk Private-Protocol Control
Expose direct I2C / SPI / OTA control paths for custom host software and deeper integration.
I2C / SPI Bridge
UTools-SI104
4 independent I2C channels and 1 SPI interface, with host-side tooling, a Linux driver prototype, and a dedicated OTA channel for hardware debug, register validation, and automated testing.
UTools-SI104 is built for multi-channel I2C / SPI peripheral debugging, register validation, automated testing, and custom host-tool development.
SI104
Software Value
How companion software and release assets speed up validation
Script
Python CLI Validation
Run register read/write, link checks, and batch validation from the command line.
Driver
Linux I2C Driver Prototype
Map multi-channel Bulk I2C access to standard i2c_adapter instances for system-side validation.
Highlights
UTools-SI104 at a glance
4 independent I2C + 1 SPI multi-channel access
4 Bulk I2C interfaces and 1 Bulk SPI interface over the private protocol
USB access with WinUSB auto-binding
Dedicated Bulk OTA upgrade channel
Linux driver prototype and dedicated OTA channel
Linux private Bulk I2C driver mapped as standard i2c_adapter instances
Interfaces & Status
Key access information
Multi-Bus Bridge
One USB entry fans out to I2C, SPI, and OTA workflows
Register debug, script validation, and driver integration share one reusable control path.
Host Side
USB Host WinUSB / Bulk
Python Script Register IO
Outputs
4x I2C Multi-channel debug
1x SPI Fast register access
OTA Dedicated upgrade path
USB EnumerationVID 0x34B7 / PID 0xE481WinUSBBoundBulk I2C / SPIReadyPhysical Channel UseConflict Risk
Delivery
Release assets and typical scenarios
Hardware Connection
The device enumerates as 4 Bulk I2C interfaces, 1 Bulk SPI interface, and 1 Bulk OTA interface.
Register Debug
The current default path is the USB Vendor Bulk private protocol; on Windows, confirm WinUSB binding first.
Validation Advice
Choose the path for the task: WinUSB private protocol for Windows debugging, kernel driver for Linux integration validation.
Typical Scenarios
Hardware Debug
Use 4 I2C channels and 1 SPI channel to quickly read/write peripheral registers and validate links.
Private Protocol Development
Build custom host software and automated validation tools over Bulk I2C / SPI / OTA interfaces.
Linux System Integration
Map the private Bulk I2C kernel-driver prototype as standard i2c_adapter instances for integration validation.
Technical Documents
Product manuals, protocol references, and other PDF-format technical resources.
PDF / EN
PDF / EN
UTools-SI104 Technical Manual V1.1
English offline guide for interface, protocol, and integration workflow.
Released: 2026-06-03
Checksum: SHA256 59026e17...52dc148c
Download PDF / EN
UTools-SI104 Product Overview V1.0
English product overview for quick product positioning.
Released: 2026-06-03
Checksum: SHA256 a566c446...389880b9
DownloadFAQ
Check these points before setup and integration.
What is the default access method today?
The default firmware uses a USB Vendor Bulk private protocol for I2C / SPI / OTA debugging, Linux driver integration, and custom host-software development.
Why should I avoid two paths on the same physical I2C channel?
When host software, Linux drivers, or test scripts access the same physical channel at the same time, state conflicts can occur. Keep one controller path active at a time.
Does SI104 support only I2C and not SPI?
No. The default firmware provides 4 I2C channels and 1 SPI channel. SPI is currently mainly used in host mode.