GPIO scan use instructions? #76
Description
Trying to configure GPIOs on "BLK18E-0012-38X38_S 50H10PE-S" board. It flashed without any issues (other than Ethernet needed some IOs enabled I guess, but that information was found.
I can do registry GPIO dump and there is no IR cut. Web interface has night mode disabled and no pins assigned.
So GPIO scan appeared to be the right tool. I can scan and see the report, but there is no explanation how it works and what to expect. There is a message: "waiting to toggle some IOs". I did toggle inputs to the IR Cut driver chip, expecting they are inputs on 3518 when unconfigured and I should see the change, but nothing happens.
I'm also concerned tat if IO is already output - it can be blown by external stimulus. Most IOs on HiSi chips are only 4 or 8mA.
Would be nice to have a bit more explanation about GPIO scan:
- Does GPIO scan put all pins in HiZ? Maybe only unassigned/undeclared in registry?
-how long pin have to be stimulated to be registered as changed? is it instantaneous or slow and require full scan cycle? How long is it?
-as I have not seeing report of changed pins - some screen grabs would help. Unless it is so obvious. - web interface IO number format? Scan reports dual numbers separated by underscore. Is web interface takes the same format or it is remapped as linear numbers?
- A little walk through use and operation of GPIO scan tool would be nice.
- Best practice to scan and identify pins for IRcut, IRlight and SDC input?
- How is "ipc tool/gpio scan"related to "gpio" app that I assume is independent app in default firmware. That one offered to scan toggle all pins or a (linear) range, so I assume it is not reading but driving, which is also can potentially blow some IOs.
I think whole community will benefit from these clarifications.
Cheers y'all!