-
Notifications
You must be signed in to change notification settings - Fork 40
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
Unable to select suitable driver for this board #49
Comments
Hi. It's probably the library. When starting up, the library needs to select an appropriate driver for the board. Different boards support different hardware. There is a raspberry pi driver, but it looks in /proc/cpuinfo for the presence of BCM2708 or BCM2709. Chances are you've got a newer raspberry pi that uses a different chip set. Can you post the contents of /proc/cpuinfo from your raspberry pi? And what model of raspberry pi do you have? |
Raspberry Pi 3
|
I've added
And it seems to work, I'll test it a bit more to be sure and will provide updates. |
Ok sweet. I don't have a board to test it on. The Raspberry Pi driver firstly detects if it applies (the test you've amended), but it also contains a function createPinData() that selects configuration for boards, since the raspberry pis sometimes change their hardware with each revision. The default case in that function is for a rasppi B+. From what I can see online, the 3 model has the same pinouts as the B+, so the B+ config should work. Just be aware that there can be differences. Do you want to create a pull request for that change, or would you like me to apply that? M |
Ok, awesome, thanks. |
Hi, @mrmorphic Hardware : Generic AM33XX (Flattened Device Tree) |
More details here: http://forum.dexterindustries.com/t/grove-dht-and-golang-in-general/3187
i2cdetect
returns the expected result, but I still get the error.The text was updated successfully, but these errors were encountered: