-
Notifications
You must be signed in to change notification settings - Fork 15
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
Error in driver when using board manager esp32 v3.0.1 #40
Comments
It has already been fixed in v0.6.1. Please try |
The first compilation problem listed above is not yet fixed. I compiled
The field |
It’s a warning, but can’t you compile? (in CI and my env compiles successfully) |
Yes, it is a "only" warning, but I need my project to compile clean. I believe this 3.x Arduino board support package from espressif has a newer c compiler and/or more stringent settings. Although this is a warning, I think it should be fixed. The compiler complains that one field of a (inherited) struct is not initialized. This sounds like the "base class" works with uninitialized data. It's just one extra line of code. |
If you want to keep your project clean, I recommend sending me a pull request or creating your own ;) |
I'm back from vacation, and wanted to make a pull request, but it compiles clean now. Looking at your fix, you clearly know much more than me about this stuff. Thanks for solving it. |
Espressif has released their board support package for esp32 in the 2.x line up to 2.0.17.
But they recently switched to 3.0.1, the switch in major version number indicating major changes.
Unfortunately, there are now compiler errors in the ESP32SPIslave driver.
I compiled
transfer_one_by_one_slave
:Quick analysis
missing initializer for member 'spi_bus_config_t::isr_cpu_id'
suggests a field has been added to a base struct; suggest to replace the comment on line 69 by
.isr_cpu_id = INTR_CPU_ID_AUTO,
???error: 'string' is not a member of 'std'
suggests a missing header file; add
#include <string>
to top of fileerror: 'task_name' was not declared in this scope;
is probably caused by the previous error
The text was updated successfully, but these errors were encountered: