-
Notifications
You must be signed in to change notification settings - Fork 0
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
RS485 not working #1
Comments
as i can see the changes for digital input 4 are acitve:
but what else is now using gpio19? |
i had to comment this line out in the file /u-boot/config.txt than the /dev/ttySC0 and ttySC1 devices are created. `root@raspberrypi4:~# dmesg | grep spi [ 2.780497] spi-bcm2835aux fe215080.spi: cs2 >= max 1 |
Hi @wasn-eu , sorry for the long delay but I realized right now that there is an open issue. Did you find out where the problem results from (what overlay uses GPIO19)? I have no idea - my rpi 3 works without any problems. Regards, |
Ah, right now I saw the possible reason: Did you install https://github.com/kwindrem/RpiGpioSetup? This uses different GPIO pins (5 6 13 16 19 26) and MUST NOT be installed together with my addon! |
Hi
first thank you for your great work.
But i have a problem that i could not use the rs485 because of a gpio conflict:
`root@raspberrypi4:~# dmesg | grep -i '(can|spi)
[ 4.428624] pinctrl-bcm2835 fe200000.gpio: pin gpio19 already requested by fe200000.gpio; cannot claim for fe215080.spi
[ 4.443245] pinctrl-bcm2835 fe200000.gpio: error -EINVAL: pin-19 (fe215080.spi)
[ 4.463172] spi-bcm2835aux fe215080.spi: error -EINVAL: Error applying setting, reverse things back
[ 4.473534] spi-bcm2835aux: probe of fe215080.spi failed with error -22
[ 5.310065] CAN device driver interface
[ 5.355077] mcp251x spi0.0 can0: MCP2515 successfully initialized.
[ 20.178960] can: controller area network core
[ 20.407351] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 22.105419] can: raw protocol
`
I have the latest stable venus os large installation on a raspberry pi 4.
The text was updated successfully, but these errors were encountered: