Hey everyone,
I recently designed the following pretty simple CM4 carrier board and now trying to re-flash the CM4 via that device. Unfortunately it's not working. When running sudo ./rpiboot on my machine I'm just getting the message "Waiting for BCM2835/6/7/2711/2712...". Looks like it cannot connect to the CM4 chip. I am using a CP2102N chip for UART to USB communication and also implemented a jumper to ground the nRPIBOOT pin. I can also see via LED that the board is running in boot mode with that jumper set but my host computer cannot connect to the CM4. I think the reason is the CP2102N chip instead like what the original carrier board is using (FSUSB42MUX + USB2514B). I did hope that I can skip those two chips because I din't understand their usage in a flashing process. But looks like it is needed. If anyone can explain me what I'm doing wrong and why the CP2102N is the wrong choice here that would be amazing. Thanks a lot in advance!
I recently designed the following pretty simple CM4 carrier board and now trying to re-flash the CM4 via that device. Unfortunately it's not working. When running sudo ./rpiboot on my machine I'm just getting the message "Waiting for BCM2835/6/7/2711/2712...". Looks like it cannot connect to the CM4 chip. I am using a CP2102N chip for UART to USB communication and also implemented a jumper to ground the nRPIBOOT pin. I can also see via LED that the board is running in boot mode with that jumper set but my host computer cannot connect to the CM4. I think the reason is the CP2102N chip instead like what the original carrier board is using (FSUSB42MUX + USB2514B). I did hope that I can skip those two chips because I din't understand their usage in a flashing process. But looks like it is needed. If anyone can explain me what I'm doing wrong and why the CP2102N is the wrong choice here that would be amazing. Thanks a lot in advance!
Statistics: Posted by hibart — Tue Jan 07, 2025 10:27 pm