How can I ensure the host Raspberry Pi 5 can safely and effectively supply power to the CM5 IO Board over USB-C?
https://github.com/raspberrypi/rpi-sb-provisioner
This diagram is a bit misleading or **maybe simplified for clarity** — it’s based on the **CM4 IO Board**, which actually had **separate** USB-C ports for power and device mode.
I am aiming for a real OTP fuse burn using `rpi-sb-provisioner`, with the Raspberry Pi 5 as the host and the Compute Module 5 (CM5) + CM5 IO Board as the target.
The **Compute Module 5 IO Board** (CM5 IO Board) only has **one USB-C port**. That USB-C port is **dual-purpose**, and its function depends on the *USB boot jumper (nRPIBOOT → GND)* and **how the USB connection is made**.
https://github.com/raspberrypi/rpi-sb-provisioner
For the **CM5 IO Board**, here's what really happens:
| Function | USB-C Port on CM5 IO Board | Notes |
| ------------------------------------------| ---------------------------------------| ---------------------------------------------------------------------------------- |
| **Power supply** | Same USB-C port | You connect 5V/3A power here |
| **Device mode (to host)** | Same USB-C port | Connect USB-A to USB-C from Pi5 or PC |
| **Jumper required** | Yes | Connect nRPIBOOT → GND to force USB boot mode |
---
### How to make it work (correct CM5-only wiring):
* **Use a single USB-C port on the CM5 IO Board**.
* Use a **USB-A to USB-C data cable** from **your host Pi 5** to **the CM5 IO Board**.
* Ensure **5V power** reaches the board **either through that cable** or how??
* Use the **nRPIBOOT jumper** to force the CM5 into device mode.
* Then run `rpiboot` on your host Pi 5.
---
If I am using the USB-C port for both power and data:
* Be sure the host (Pi 5) can supply **sufficient power**
* Or power the CM5 IO Board through the **barrel jack** and use USB-C **only for data** ??? How??
https://github.com/raspberrypi/rpi-sb-provisioner
This diagram is a bit misleading or **maybe simplified for clarity** — it’s based on the **CM4 IO Board**, which actually had **separate** USB-C ports for power and device mode.
I am aiming for a real OTP fuse burn using `rpi-sb-provisioner`, with the Raspberry Pi 5 as the host and the Compute Module 5 (CM5) + CM5 IO Board as the target.
The **Compute Module 5 IO Board** (CM5 IO Board) only has **one USB-C port**. That USB-C port is **dual-purpose**, and its function depends on the *USB boot jumper (nRPIBOOT → GND)* and **how the USB connection is made**.
https://github.com/raspberrypi/rpi-sb-provisioner
For the **CM5 IO Board**, here's what really happens:
| Function | USB-C Port on CM5 IO Board | Notes |
| ------------------------------------------| ---------------------------------------| ---------------------------------------------------------------------------------- |
| **Power supply** | Same USB-C port | You connect 5V/3A power here |
| **Device mode (to host)** | Same USB-C port | Connect USB-A to USB-C from Pi5 or PC |
| **Jumper required** | Yes | Connect nRPIBOOT → GND to force USB boot mode |
---
### How to make it work (correct CM5-only wiring):
* **Use a single USB-C port on the CM5 IO Board**.
* Use a **USB-A to USB-C data cable** from **your host Pi 5** to **the CM5 IO Board**.
* Ensure **5V power** reaches the board **either through that cable** or how??
* Use the **nRPIBOOT jumper** to force the CM5 into device mode.
* Then run `rpiboot` on your host Pi 5.
---
If I am using the USB-C port for both power and data:
* Be sure the host (Pi 5) can supply **sufficient power**
* Or power the CM5 IO Board through the **barrel jack** and use USB-C **only for data** ??? How??
Statistics: Posted by ayushpandey104 — Mon May 12, 2025 7:55 pm