gpio_export: something went wrong: No such file or directory about chip_io HOT 5 CLOSED

Are you properly cleaning up the GPIO before exiting out of the interpreter?
What happens if you do: ls /sys/class/gpio

from chip_io.

I have the same error using python 2.7.9

root@chip:/home/chip# ls /sys/class/gpio
export gpiochip0 gpiochip1013 gpiochip1021 unexport

from chip_io.

I see the same error being displayed when debug mode is active. In my case, GPIO works even when these messages are being displayed.

I think this is caused by a small bug on function gpio_export on event_gpio.c:

    ssize_t s = write(fd, str_gpio, len);  e_no = errno;
    if (DEBUG)
        if (e_no)
            printf("gpio_export: something went wrong: %s\n", strerror(e_no));

I'm not an expert on C, but according to what I researched you should only check errno when you get an erroneous result. In this case, we should check the value returned by write first, and if it's different to the value of len, then we should check the error code the function set into errno (this check is done further in the gpio_export function and it passes in my tests). You should expect the stdlib functions to set errno only in case of error. In this case, a previous function call set the errno variable to "2" (no such file or directory), so when the code above checked errno, the error line was printed. I made a test change to print errno before and after the write call and confirmed the errno code of "2" was there before the call to write, so I think we can ignore these errors. I'll try to submit a patch for this, it's pretty simple.

from chip_io.

Nice work! I haven't used the GPIO pins on my CHIP for anything and with it being so long I can't remember if this issue is the reason I never fully utilized it. Either way nice contribution!

from chip_io.

Nice work! I haven't used the GPIO pins on my CHIP for anything and with it being so long I can't remember if this issue is the reason I never fully utilized it. Either way nice contribution!

Thanks for your kind words! And also thank you for opening this issue in the first place: it inspired me to search for an answer to this problem :)

Regards,
-G.

from chip_io.