-
Notifications
You must be signed in to change notification settings - Fork 54
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
Error on RaspberryPi B+ #3
Comments
Commenting out
Seems to workaround this particular error, but then I get the following error
|
means, that the MCU did not reset or speaks at a wrong baud rate. A good indication for that is, if the returned error hex values are most of the time identical. Try |
Bingo! Works on the Raspberry Pi B. Will try B+ now.
|
Works on the B+ as well with the |
Can you confirm are you saying that even after selecting the correct baud you still had to comment out "GPIO.setmode(GPIO.BOARD)" for this to work on a B+ ? Paul |
Hi Paul, Yes that's correct. With the "GPIO.setmode(GPIO.BOARD)" as in the original code, but with this pull request modification (otherwise autoreset just runs in the background with no error message and I had to run strace manually to find out why), then that's the error:
|
Ok, the issue seems to be strictly "RFM2Pi" related and not something deanmao would be aware of. deanmao originally used GPIO.setmode(GPIO.BOARD) & .pin 11 for reset (P1-26 or BCM GPIO07) and when it was adapted by @mharizanov he changed it to use (GPIO.setmode(GPIO.BCM) pin 4 (P1-7) but left the previous setmode in place (it just gone unnoticed in the background until now). Since the mapping can change but the physical pin that aligns with the RFM2Pi cannot change. I think it would be wiser to revert back to the original GPIO.setmode(GPIO.BOARD), remove the (GPIO.setmode(GPIO.BCM) line and set the pin number to 7. This way it will always be right unless the rfm2pi is physically changed. Are you in a position to (easily) test that theory by any chance? and then we can get the repo's updated. |
Hi Paul, |
The text was updated successfully, but these errors were encountered: