Skip to content
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

Why is DEBUG_VERBOSE commented out in AIoTC_Config.h #521

Closed
kensheldon opened this issue Jan 2, 2025 · 1 comment
Closed

Why is DEBUG_VERBOSE commented out in AIoTC_Config.h #521

kensheldon opened this issue Jan 2, 2025 · 1 comment
Labels
topic: code Related to content of the project itself

Comments

@kensheldon
Copy link

AIoTC_Config.h contains macros to simplify the syntax of calls to Debug.print(DBG_blah, ...) The file defines helper macros for diagnostic levels ERROR, WARNING, INFO, DEBUG, and VERBOSE. This seems like a nice feature, but for one detail: One of the macros swallows its arguments. The body is commented out.

#define DEBUG_VERBOSE(fmt, ...) //Debug.print(DBG_VERBOSE, fmt, ## __VA_ARGS__)

@per1234 per1234 added the topic: code Related to content of the project itself label Jan 3, 2025
@pennam
Copy link
Collaborator

pennam commented Jan 8, 2025

Hi @kensheldon
The body is commented out because enabling debug verbose you will get a remarkable flash increase usage and on some boards (MKRWiFi 1010 and Nano 33 IoT) will leave few flash space to write user application. I think it would be feasible to add more ifdefs and enable DEBUG_VERBOSE on boards that has more flash space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: code Related to content of the project itself
Projects
None yet
Development

No branches or pull requests

3 participants