Both cases indicate that the Pi can't communicate with the image sensor over I2C - the firmware hasn't found it for auto-detect, and the kernel can't find it when told explicitly to look for it.
You could try "pinctrl set 44 op dh" to force the regulator on, and then try "sudo i2cdetect -y 10". If address 0x1a responds then that implies a device tree error that we can investigate. (Note that the 44 there is platform specific, so only applies to a Pi0W).
The fact that address 0x64 is responding means that the PCB that carries the image sensor is connected correctly, so that only leaves the small connector that connects the sensor to the sensor module to that PCB. If that really is clicked fully home, then the sensor is dead somehow. It's rare as all modules are tested on the assembly line at the factory, but it can happen.
You could try "pinctrl set 44 op dh" to force the regulator on, and then try "sudo i2cdetect -y 10". If address 0x1a responds then that implies a device tree error that we can investigate. (Note that the 44 there is platform specific, so only applies to a Pi0W).
The fact that address 0x64 is responding means that the PCB that carries the image sensor is connected correctly, so that only leaves the small connector that connects the sensor to the sensor module to that PCB. If that really is clicked fully home, then the sensor is dead somehow. It's rare as all modules are tested on the assembly line at the factory, but it can happen.
Statistics: Posted by 6by9 — Mon Jul 08, 2024 11:39 am
