-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simple rpio i2c example doesn't release the line #108
Comments
Thanks for the report. I only have a couple of i2c devices which appear to work ok, but will try to see if I can figure out if there are any issues with init/deinit. |
Thank you for the quick reply. |
same issue here ! $ i2cdetect -y 1 $ sudo node index.js (this is the LCD example) $ i2cdetect -y 1 i2cdetect sees something at address 0x03 , but after the next run no devices are detected |
Happen the same as PeterMaes , after rpio.i2cBegin(); |
I have the same problem.. no fix, no solution. |
Sensor: bmp180
Model: RPI 2B+
rpio: 1.3.0
Example is simple
i2c.js
:Steps:
$ sudo i2cdetect -y 1
$ sudo node i2c.js
After that the command
sudo i2cdetect -y 1
runs 10 times slower and shows no sensor:More over, I have another sensors which can be read with
rpio
without any issue, but after first read any other program can't get access to i2c bus.For example:
After reboot:
$ sudo node ~/api/i2c.js
bmp180.js:
PS:
dtoverlay=gpio-no-irq
$ cat >/etc/udev/rules.d/20-gpiomem.rules <<EOF SUBSYSTEM=="bcm2835-gpiomem", KERNEL=="gpiomem", GROUP="gpio", MODE="0660" EOF
with and without it story is the same
Please let me know what is wrong and how to fix it.
Thank you.
The text was updated successfully, but these errors were encountered: