I’m experiencing a problem trying to bind GPIO7. I can bind other GPIO fine, such as GPIO2, but things do not seem to work when I bind the former. I’m not doing anything with the GPIO yet, just attempting to bind it. But, when trying to bind GPIO7, my app refuses to start.
If I start it with
"app start", it’ll simply hang on
If I start it with
"app runProc myProg --exe=myProg", it’ll hit
COMPONENT_INIT, but then it’ll output:
Jul 6 13:13:30 swi-mdm9x15 user.emerg Legato: EMR | myProg/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (myProg.mainComponent.le_gpioPin7:eb4b6dc575d64f27484e7657275f11fd).
Jul 6 13:13:31 swi-mdm9x15 user.info Legato: INFO | supervisor/supervisor T=main | proc.c proc_SigChildHandler() 2035 | Process ‘myProg’ (PID: 394) has exited with exit code 1.
Jul 6 13:13:31 swi-mdm9x15 user.warn Legato: -WRN- | supervisor/supervisor T=main | app.c app_SigChildHandler() 3457 | Process ‘myProg’ in app ‘myProg’ faulted: Ignored.
Jul 6 13:26:12 swi-mdm9x15 user.info Legato: INFO | supervisor/supervisor T=main | apps.c DeactivateAppContainer() 374 | Application ‘myProg’ has stopped.
I’m binding in my .adef like so:
myProg.mainComponent.le_gpioPin7 -> gpioService.le_gpioPin7
…and requiring in my .cdef:
le_gpioPin7 = le_gpio.api
I’ve checked the pin status in microcom via
AT+WIOCFG? as well. I’ve tried having it set to both 4 & 16, but it doesn’t seem to make a difference.
Is there something different about GPIO7? I looked around the forum a bit and saw some discusion regarding gpioExpanderService and conflicts, but I wasn’t sure if any of that applied to this scenario or not (gpioExpanderService is not installed on my device). Thank you very much in advance.
Board: mangOH Red
Firmware: SWI9X15Y_07.12.14.00 r34472 CARMD-EV-FRMWR1 2017/11/29 18:24:42