Hello Dirk,

I resolved the issue, I matched the /boot/config.txt contents as it was in stretch image and then copied the config.rsc to /etc/revpi. It is working now.

Hello Dirk, Thank you for the response. I double-checked the PiBridge connector and seems like the connection is fine. I can tell this because with stretch image, I have no problem in recognizing DIO module or even playing with the i/p o/p. Also, I did perform piTest -x and when that did not work, I...

I have a revolutionpi connect+ and I have built a custom image with yocto. I used the kernel from https://github.com/RevolutionPi/linux and have also installed picontrol and pitest. Uptill now, everything is working fine. When I enter the command > piTest -d Found 1 devices: Address: 0 module type: ...

I am bit late to reply, but I happened to make this work. The problem was with version of uboot 2019.07 which seems to be a common issue for raspberrypi compute modules. I used the older version of uboot 2018.11 and everything worked fine.

I am using Revpi Connect+, for this i have set: MACHINE = "raspberrypi-cm3". Also, again I would like to let you know without uboot, image successfully boots.

I have built a rpi-basic-image provided by the meta-raspberrypi layer for raspberrypi and and revolution pi. But now for my implementation I need to use uboot. With meta-raspberrypi this is also quite simple, just add RPI_USE_U_BOOT = "1" in local.conf. But with this configuration, the ima...