-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Support phy/cert_test for ESP32 chip (IDFGH-10756) #11972
Comments
It doesn't work for ESP32-S3 platform I (45) boot: ESP-IDF v5.1.1-dirty 2nd stage bootloader error message is :
after following configuration option enabled on ssdkconfig. It is fixed |
Hi, We're having this problem too. Built on espidf 5.1.1 and platformio 6.4.0:
I added these to the include paths already:
Are there any workarounds to get this to work on the good old esp32 board? |
Hello, I am also trying to get cert_test to work on esp32, any thoughts? Thanks |
Any update on this? |
Could you provide more details on the ESP32-C6? I noticed that the RF test tool binary includes an option for testing Thread/Zigbee channels. Are there specific header files available, similar to Bluetooth and Wi-Fi? |
Is your feature request related to a problem?
We are designing a product centered on the ESP32 chip. For the certification tests, we need access to the certification APIs, and currently they are only supported for ESP32-S3 and ESP32-C3.
Describe the solution you'd like.
We would like the certification APIs to be ported and made available for the ESP32 chip (including the
phy/cert_test
example included in latest esp-idf).Describe alternatives you've considered.
We have considered using the certification test Windows application provided in Espressif webpage, but unfortunately it is not possible for us to use it because the system needs to configure additional peripherals for the board to work, and also during operation we have no direct access to the ESP32 UART.
Additional context.
No response
The text was updated successfully, but these errors were encountered: