-
Notifications
You must be signed in to change notification settings - Fork 24
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
question about command timeout #3
Comments
Thank you for your inquiry. Customers are encouraged to submit technical questions via our dedicated support portal at https://semtech.force.com/ldp/ldp_support. We invite all users to visit the LoRa Developer Portal Forum at https://forum.lora-developers.semtech.com and to join the thriving LoRa development community! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I meet a problem that the chip enter
COMMAND_TIMEOUT
state. This happens when I usellcc68_write_buffer
with data longer than 4 bytes, the datasheet said thatCOMMAND_TIMEOUT
is caused by an internal watchdog, and this watchdog can be disabled by the host, but I can't find any description about this watchdog and any opcode to disable it.Do you have any idea about how to debug this problem?
BTW, I've tried SPI frequency from 10M to 16MHz, and that didn't make any difference on this problem
The text was updated successfully, but these errors were encountered: