-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use cyw43 macros for bluetooth logging #2490
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
base: develop
Are you sure you want to change the base?
Use cyw43 macros for bluetooth logging #2490
Conversation
not yet convinced as CYW43_PRINTF seems to be on by default (?) which means we're now getting a bunch more logging |
I've replaced calls to cybt_printf with calls to CYW43_PRINTF. So as far as I can see this should NOT produce more logging. I don't see extra logging when I test bluetooth. |
I'm confused (from cyw43_config.h)
Which is why i thought CYW43_PRINTF is supposed to print, and you should use the other macros to route to it. I don't see anything in pico-sdk at least that disables CYW43_PRINTF by default |
Note also that the cyw43_driver only uses it directly in a |
You're saying that my change enables more logging. I'm just telling you that it behaves the same. |
I'm saying you are compiling more printf strings into the binary, not necessarily that they are being printed the driver itself seems to use CYW43_WARN for such error strings (which seems to be where we're mostly using them)
so i think these are wrong too - i just hadn't noticed before ;-) |
ok, you're right cybt_printf was off in release. |
c88ae46
to
33efceb
Compare
Second attempt... |
33efceb
to
03ec34e
Compare
CYW43_PRINTF is used for errors
CYW43_DEBUG is for messages in debug builds only
CYW43_VDEBUG is disabled by default
Fixes #2253