-
Notifications
You must be signed in to change notification settings - Fork 398
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
RADIOLIB_DEBUG_PROTOCOL on ST nucleo-WL55JC1 explodes in cascades of garbled output #1327
Comments
There is a reasonable chance that the garbled mess is in fact information, so before we disappear down too many rabbit holes, can you post some of the output. You didn't say if it still worked even if the output looks wrong. The latest version has passed all the pre-compliance checks for LoRa so if you could tell us which LNS's are causing issue & what those issues are that would be useful - it is tested against TTS by default and then Chirpstack occasionally. |
Hmm, I got it wrong, it actually do get a few lines of normal output before it turns crazy. I test against a completely default configured chirpstack. I dont see any traffic from the device if I enable the flag. The output looks like: (and it runs really fast, what you see below is approx 0.5 second)
|
I have now tried the program on a ATSAMD21+RFM95 combo. Changed a few lines for the new radio:
and removed the Prints the debug just perfect, and connect to my LNS too. Some time ago I did the same with an ESP, no problems with the |
Couple of things to check would be whether the other debug flags also cause this problem, and how much the compiled binary size changes when you enable them. Which version of the library are you running? Garbled UART output is usually one of the following:
|
The 3 other debug options works as expected. Code sizes as reported by the tool chain:
The protocol one is definitely much bigger. |
I assume you're using STM32duino, just to be clear? Haven't had any issues with it through the Arduino IDE, didn't test PIO. |
This is my
Hope it answers your question. Dunno if there are multiple ways to do arduino programming on the STM32 |
Are you using the actual Nucleo-WL55JC1 board - if so, I can give it a try and then we can debug from there. |
correct, a Nucleo-WL55CJ1 |
And I can add that I have just repeated the test, this time building on a windows machine. Same result. The previous tests as all been built on Linux |
Not sure that this is 100% good hint for you Try to set
in your sketch build environment ( Read this wiki page for details: |
I might need a little help on this. I added the two compile flags to build_flags in my I even went to the extreme and put this in the file while moving it around:
rationale would be that if the compiler actually pick up the file and tries to use the crazy value I would at least get a build error. But that never happened.... |
https://github.com/stm32duino/Arduino_Core_STM32/wiki/Customize-build-options-using-build_opt.h |
@MortenGuldager could you please try the fix proposed by @lyusupov? Please note that the referenced |
@StevenCellist |
Trying to use
RADIOLIB_DEBUG_PROTOCOL
to get a understanding of why my device works better with some LNS than others.When I enable
RADIOLIB_DEBUG_PROTOCOL
inBuildOptUser.h
the console just print a garbled mess. Seems to begin imediatly the moment where the first debug is to be printed.RADIOLIB_DEBUG_BASIC
is working as expected.The program is as simple as I can make it.
The text was updated successfully, but these errors were encountered: