When I use a CM5 SoC on a third party CM4 board that has USB-C and pull down resistors directly on the CC pins, I can use a USB-C cable on both the host and device end and the CM5 SoC always properly receives device status. When I take the same SoC and move it to the CM5 IO board with no devices plugged into USB-C or other additional devices to draw more power, I am unable to have any of my host devices recognize the CM5 / IO board as a device without a USB-C to A to C adapter (USB A female device facing to define the host/device relationship). This results in USB-A voltage limitations. With USB-C to USB-C the IO board is properly powered but with no data connection as a device.
When designing your board, did you run into similar issues with the CM5 IO board with the CM5 SoC? Is there a documented issue or jumper that I may need to use to correct this problem? I have also seen reports of people running into the same problem with the Pi 5 and solving it with a USB-A adapter as well. Apologies if I am missing something that’s already been well documented or discussed, but since your board is trying to deal with some of these issues, I’m curious what you’ve learned.
When designing your board, did you run into similar issues with the CM5 IO board with the CM5 SoC? Is there a documented issue or jumper that I may need to use to correct this problem? I have also seen reports of people running into the same problem with the Pi 5 and solving it with a USB-A adapter as well. Apologies if I am missing something that’s already been well documented or discussed, but since your board is trying to deal with some of these issues, I’m curious what you’ve learned.
Statistics: Posted by ChipChop — Sat Feb 01, 2025 10:57 pm