You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
For device production, we are using the test partition so we can segment the test code from the application code.
To activate the test partition we configure the CONFIG_BOOTLOADER_NUM_PIN_APP_TEST with the same gpio as the UART0 RX pin. This way we can activate the test partition sending a BREAK over UART.
The problem with ESP32-S3 is that the default UART0 RX gpio is the gpio 44 but the Kconfig only supports the range 0-39
This can be easily fixed changing the Kconfig to support custom ranges depending of the target
range 0 39 if IDF_TARGET_ESP32
range 0 44 if IDF_TARGET_ESP32S3
I would like an official fix from espressif.
Can you add a custom range for all the supported targets to the CONFIG_BOOTLOADER_NUM_PIN_APP_TEST and CONFIG_BOOTLOADER_NUM_PIN_FACTORY_RESET
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
CONFIG_BOOTLOADER_NUM_PIN_APP_TEST pin configuration for ESP32-S3
CONFIG_BOOTLOADER_NUM_PIN_APP_TEST pin configuration for ESP32-S3 (IDFGH-13623)
Sep 4, 2024
Hello @Psyjonas,
I updated CONFIG_BOOTLOADER_NUM_PIN_APP_TEST and CONFIG_BOOTLOADER_NUM_PIN_FACTORY_RESET with target specific ranges. The modifications were merged internally and will be available with the next sync with GH.
Answers checklist.
General issue report
For device production, we are using the test partition so we can segment the test code from the application code.
To activate the test partition we configure the CONFIG_BOOTLOADER_NUM_PIN_APP_TEST with the same gpio as the UART0 RX pin. This way we can activate the test partition sending a BREAK over UART.
The problem with ESP32-S3 is that the default UART0 RX gpio is the gpio 44 but the Kconfig only supports the range 0-39
This can be easily fixed changing the Kconfig to support custom ranges depending of the target
I would like an official fix from espressif.
Can you add a custom range for all the supported targets to the CONFIG_BOOTLOADER_NUM_PIN_APP_TEST and CONFIG_BOOTLOADER_NUM_PIN_FACTORY_RESET
The text was updated successfully, but these errors were encountered: