gpiochi412 as example
- Dominant language
- Erlang
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
`root@OpenWrt:~# ls /sys/class/gpio/`
`export gpio432 gpiochip412 unexport`
how can i wrote the code
`(change_gw@OpenWrt)8> gpio:open_chip("/dev/gpiochip412").`
`{error,enoent}`
`gpio:open_chip("/dev/gpiochip0").`
`{ok,#Ref<0.172490437.1821769745.83712>}`
`gpio:open_lines(Chip, [1], [output], [0], "my-application").`
`{error,16}`
`gpio:open_lines(Chip, [1], [output], [0], "my-application").`
`{error,ebadf}`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the OpenWrt commands and the calls to gpio:open_chip/1 and gpio:open_lines/5 shown in the issue. Trace those entry points to determine why gpiochip412 returns enoent and the subsequent line operations return error 16 or ebadf. Done means identifying the cause and documenting a reproducible resolution for the reported device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100