search

OpenIPC / ipctool

Simple tool (and library) for checking IP camera hardware
https://openipc.org
MIT License
152 stars 33 forks source link

gpio scan issue #103

Closed bedenko closed 4 months ago

bedenko commented 7 months ago

I have module IMA20S07 with SSC335 and IMX307. I've flashed module with latest image 2.3.12.07-lite. IRCUT is not working, so i ran command ipctool gpio scan, but i got empty return with exit code 1.

I tried ipctool trace /tmp/ipctool gpio scan, but ipctool creates child process and trace tool does not support tracing of child processes.

Is there any other way of debugging this? Besides setting up complete SDK and compiling new ipctool with additional outputs.

widgetii commented 7 months ago

Besides setting up complete SDK and compiling new ipctool with additional outputs.

That's the only way to debug it properly

flyrouter commented 7 months ago

One simple and dirty way is to try to control different GPIOs by brute force in scanning mode and changing values. The last two numbers indicate from which GPIO you need to scan. Break it up into small sections and keep an eye on the camera. Quite often, an IR filter is attached to 78 and 79 GPIOs, but this is only one of the options.

curl -s https://raw.githubusercontent.com/OpenIPC/sandbox/main/scripts/search-gpio/search-gpio | sh -s -- 0 100
bedenko commented 7 months ago

@FlyRouter that script worked like a charm! Indeed there are pins 78 (on) and 79 (off) responsible for IRCUT. Now i only need to find pin for IR sensor. I assumed it was pin 81, since it is set as input in /sys/class/gpio/, but it does not change value in day/night ambient.

flyrouter commented 7 months ago

Good Don’t forget to then indicate the data for your device in the GPIO table in our Wiki.