-
Notifications
You must be signed in to change notification settings - Fork 94
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
Tuning cfg.toml doesn't work as expected #399
Comments
Only thing I could think of is that the cfg wasn't picked up in the first try. With info-level debug esp-wifi should also show what the current config looks like:
|
Yes, the cfg wasn't picked up in my first try. The logging is attached below:
I performed command 'cargo clean' to my workspace, then recompiled and this issue didn't occur any more. 😂
My guess is that the compiler doesn't watch the cfg.toml file in some case. |
Great to hear it's working! 🎉 |
Hi,
I try to play ESP32C6 with no-std esp-wifi and coex profile. It paniced when initialized the BLE because of OOM, and I followed 'tuning.md' to create a cfg.toml and set 'heap_size' to 200K. After that, it still paniced by OOM error. The logging is attached below:
Per I set the 'HEAP_SIZE' to 200K, the heap should be big enough. I suspected the cfg.toml doesn't work. My workspace structure is like:
And the cfg.toml is:
So then I patched the esp-wifi crate to local repository for hack and debug:
After I recompiled and flashed the firmware, I found the BLE initialized successfully! That means the 'cfg.toml' was working.
What is the difference between remote git revision patch and local repository patch?
The text was updated successfully, but these errors were encountered: