-
Notifications
You must be signed in to change notification settings - Fork 836
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
[Bug]: Missing "esp32/rom/aes.h" #8266
Comments
@gojimmypi help! |
Hi @AchimPieters and thank you for reaching out. We had your HomeKit working well with wolfSSL no? I didn't immediately see recent changes prior to this issue. Any insight as to what you think might be the root cause? The include files missing First thing that comes to mind is the chipset selection. I am certain the Don't forget to include wolfssl/wolfcrypt/settings.h in every source file that uses wolfSSL. Important also ensure I see you are still using a local copy of wolfSSL. Keep an eye on #8251 that will be the updated source code used for recent release 5.7.4 wolfSSL Espressif Managed Component. This release has considerably more flexibility with Coincidentally, that 8251 PR also addresses a concern where Managed Component files are not found: they actually go missing after being deleted when the build system detects them as not used. It would seem unlikely but not impossible that you might have something similar going on. I need to wrap up a few things, but I'll take a look at this as soon as I can. Cheers |
@gojimmypi Update: Tried the 5.7.4-preview1e as a managed component:
Got the same error:
The tried |
@gojimmypi Tried to compile
when compiling for an ESP32 everting works. Above is compiling when selecting an ESP32C3 |
Hello @AchimPieters and thank you so much for taking the latest wolfSSL Managed Component for a test drive!
ok, so that certainly got my attention, as the example apps need to work properly. I tested this on my ESP32-C3 and it successfully fetched the WRK_IDF_PATH=/mnt/c/SysGCC/esp32/esp-idf/v5.2
cd $WRK_IDF_PATH
. ./export.sh
cd /mnt/c/test/component
idf.py create-project-from-example "wolfssl/wolfssl^5.7.4-preview1e:wolfssl_benchmark"
cd wolfssl_benchmark
idf.py set-target esp32c3
idf.py -p /dev/ttyS44 -b 115200 build flash monitor If you encountered the above error in a Docker container, please try using the standard ESP-IDF the command-line to eliminate any internal configuration issues. Also: I too, was previously seeing some oddities in the managed components. It was not until I opened espressif/idf-component-manager#78 that I learned that the the component manager itself needs to be kept updated. It is a manual process, apparently completely separate from the ESP-IDF versions. I had a fairly old version and the update certainly helped. Here's the text presented when opening an "Check the version of the Component manager. Run Could you please give that a try and let me know your results? Any additional details on the steps needed to reproduce the error you encountered will be appreciated. Cheers. |
Hi @AchimPieters - additional details: Please see my #8251 comment. We cannot use I think that might also help with the |
This fails as noted in AchimPieters/esp32-homekit-demo#15:
The output:
Using my esp32-homekit-demo fork, instead with everything updated except for those submodules:
Note that I needed to apply these changes as suggested in AchimPieters/esp32-homekit-demo#14 (comment)
... and I was otherwise able to compile the LED example without the error described in this issue. Note that the copy of wolfssl that you have is still from the prior wolfSSL release, 5.7.2. I'd like to help with the error you are encountering. I need to first compile it with the latest code and see then error when not using docker. @AchimPieters Can you please fix the submodule problem on your repo? Thanks. |
@gojimmypi solved |
Are you referring to AchimPieters/esp32-homekit-demo#15 or this issue or both? Upon resolution of that issue, I am able to build your latest LED example without error (including no changes needed for mdns) in WSL, with your copy of wolfSSL 5.7.2:
My WSL does not support docker. I have a VM with regular Ubuntu but it is stuck waiting with some update message. I am unable to test your docker build at this time. Can you please confirm if this issue is resolved or if you are still encountering the same problem? It would be great to have you try this outside of Docker to determine the location of the problem. |
@gojimmypi Solved! here is what I did: ✅ docker pull espressif/idf:release-v5.2 idf:release-v5.2idf:release-v5.3idf:release-v5.4idf:latest |
aha! So this is only a problem with the I'm a bit reluctant to make changes for something that is not even an official release, but I'm also curious & don't want any surprises when We do have tests for Espressif latest but not for all chip types at this time in IDE/Espressif/ESP-IDF/compileAllExamples.sh. There are no ESP-IDF issues referencing "aes.h". btw - I also encountered similar, bad commit when refreshing my ESP-IDF
After resolving that and using the latest ESP-IDF, I do see compile errors, but not related to wolfSSL and not the |
@gojimmypi Okay, now that this "problem" is resolved and everything compiles as it should, I'm still getting the following warning:
How can I remove or suppress this warning? |
Hi @AchimPieters that warning occurs when RSA is enabled and there's less than 10K in You can either adjust the main stack size in Exactly which version of wolfSSL are you using? btw - have you resolved this for the most recent upstream ESP-IDF version (I believe it is v5.5). I still se some compile errors, unrelated to wolfSSL. |
@gojimmypi currently I'm using wolfSSL version 5.7.4-preview1e and to wich compile errors do you refer? |
Hi @AchimPieters -
That's a fairly good preview version of wolfSSL. There's a slightly newer There's a known issue in espressif/idf-component-manager#78 regarding exactly which version is used. That latest From your log file, it appears you are using
Disregard; I had compile errors near the end, but did not notice several of the submodules were giving warnings about being out of sync. Upon refreshing submodules, all is working as desired. This example works in ESP-IDF v5.2
Confirmed the same example with
Here's ESP-IDF v5.2 for your LED example; I needed to manually add the two managed components:
On your main branch, I'm still seeing the mdns errors. I needed to manually added the
That's excellent! Please see the respective user_settings.h line:
The generated
To fix the warning set the In the next release, I'll add something more robust in the Kconfig file to handle situations where the main stack is not the one used for RSA (e.g. when using FreeRTOS tasks). Please be sure you are using the most recent version of the component manager as noted in #8251 (comment) |
Contact Details
Version
5.7.2
Description
user_settings.h
user_settings.TXT
Reproduction steps
Reproduction steps
Install docker
Install IDF V5.0 - docker pull espressif/idf:latest
Clone repository - git clone --recursive https://github.com/AchimPieters/esp32-homekit-demo.git
start IDF - docker run -it -v ~/ESP32-HOMEKIT-DEMO:/project -w /project espressif/idf:latest
cd examples - cd led
idf.py set-target esp32c3
idf.py menuconfig
idf.py build
Relevant log output
The text was updated successfully, but these errors were encountered: