-
Notifications
You must be signed in to change notification settings - Fork 2k
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
driver xbee and uart #4731
Comments
Created PR #4734. |
Following commits add extra debug outputs. Yonezawa-T2@0b437f4 Set You may also be interested in #4445 if you have other problems. |
I've tried the driver with the arduino-due and it still fails, but I think is a problem of uart.
At last, not log the debug info |
Created PR #4749. |
Good, i've tested the new driver and it works as wanted.
Last question: destination long address how is obtained? because with my xbee it not matches. |
I don't sure that I understand your question correctly. XBee use short address as its source address unless its short address is configured to |
This issue can be closed, as #4445 has been merged. |
xbee: add timeout for AT command response (fixes #4731)
xbee: add timeout for AT command response (fixes #4731) (backport)
Hi, i'm testing the xbee driver with an arduino-due board.
The current driver for xbee not work with the board, the driver stop run at line 126 of xbee.c:
while (dev->resp_limit != dev->resp_count) { mutex_lock(&(dev->resp_lock)); }
The same configuration and board work with riot release 2015.09.
Maybe the problem is into uart driver, but I think the xbee driver need to have a timeout. Because now riot is locked and it not log any info to detect the problem.
The text was updated successfully, but these errors were encountered: