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

Logging problems... forced to use ESP_EARLY_LOGE; ESP_LOGx variants don't show on to idf.py monitor #14

Open
mosagepa opened this issue May 23, 2022 · 0 comments

Comments

@mosagepa
Copy link

mosagepa commented May 23, 2022

It appears to me (I've done several checks and spent all weekend with this problem), that use of 'esp-wolfssl' is preventing proper output e.g. within 'idf.py monitor' command, of logging information explicitly coded within either the app_main or subsidiary user functions calling ESP_LOGx(,,...) ESP-IDF macros.

I point this because even the basic client example provided, any additional user code can only putting out messages in the 'idf.py monitor' when I resort to ESP_EARLY_LOGE i.e. logging macros that are essentially ISR-safe and do not use printf()'s behind your back. Logging stuff coming from "system" modules seem to pass along effortlessly, though...

I also wish to know, does anyone here know whether the 'wolfssl_client' example properly address the WiFi API for recent versions of IDF properly? If you try to compile the example as it comes, it blocks trying to connecting to the WiFi AP, keeps retrying forever... does not give any explicit error though. I guess this comes down to using deprecated sequence of WiFi setting up commands wrt the "new way" of doing WiFi within IDF.

I can provide source code examples for you to appreciate the difference in WiFi handling wrt older ESP-IDF way.
Kind regards & thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant