-
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
Recieving Garbage without anything Sending #10
Comments
Can you try the DumpRegister Example? It reads all the registers in the module and prints them. That can help you make sure that you can communicate with the module correctly. You should be able to read the Version register at 0x42. If you don't see the correct output, the link is not correctly setup and we can debug from there. |
Well, interestingly, every single register is coming back as 0xC8. Of course, I had to disable the version check to get the dump to run correctly
Sorry accidentally closed issue |
Can you use this code to test the SPI communication? This is a simple code that sets up SPI and reads the Version Register and prints it. There might be errors as I couldn't, but they should be minor. If you don't see the correct output I'll suggest to debug the SPI communication between the module and the pi pico.
|
Sorrry for the delayed response! Running your code above the output is I've also tested the register dump with a new Pico and a new LoRa chip to the same results. |
Can you comment out lines 120 to 123 and try to use the library, as you are using a different chip, it might not be working for you.
|
I have already commented out the version check as I had to in order to run the dumpregisters code You said you've used this chip before right? I'm worried that all of the opcodes are different otherwise |
Hey, I know I'm quite late, but I think that the issue is in printing the output. Try replacing char* (pointer) to normal char. |
Upon flashing LoRaReceiver.cpp onto my Pico, the device immediately begins recieving garbage, regardless if there's another device sending or not. A sending device does not create a different output. Perhaps this suggests the nature of the issue?
And so on forever.
The text was updated successfully, but these errors were encountered: