Its very odd indeed that it locks completely. There are lot of hardware/software in the GPU to ensure that complete lockups cannot happen (you really don't want a mobile phone to lock up and require a battery removal to reset it!). So that makes me suspect the app itself, which does have a particular wait on semaphore which doesn't timeout (for some reason the timeout version of the semaphore wait was giving me inconsistent results, so I had to remove it)- it may be getting jammed there.rkinch wrote:Let me be clear that I'm not faulting the camera module here. By "touch" I mean actually making a lot of clumsy contact with the board conductors while awkwardly hand-holding it on a lab workbench instead of using a proper fixture. I would expect this to interfere with the signaling. One would not do this is a normal application. My points were (1) that this type of interference locks up the camera on the software level, so that something at some abstraction level(s) is not able to recover from noise or dropouts or interruptions in the signals, because only a reboot gets it running again, (2) dodgy cabling that is too long might exhibit the same instability, and (3) the signals are digital, so it is not like the analog pixels are being transmitted and digitized after traversing a long cable, so a longer cable is not going to degrade the images, if the digital signals get through, and if they don't, then one would expect to get lockup or other erratic response, not dropped pixels or other mild degradations.jamesh wrote:Don't know why your camera locks when you touch it - I've never had that problem.
There again, the app is only meant as demo code, and not for production, so some issues are to be expected.