Yesterday I made the mistake of updating the toolchain to version 5.4, which is not fully compatible with VisualGDB. After doing so, I tried to install version 5.3. When compiling the toolchain, an error is thrown on the usb_dwc_hal.c file. The error is in the included file usb_dwc_ll.h at line 224:
hw->gusbcfg_reg.ulpiutmisel = 0;
error: 'usb_dwc_gusbcfg_reg_t' has no member named 'ulpiutmisel'
The compiled file is the 5.3 toolchain, contained in the folder:
C:/SysGCC/esp32/esp-idf/v5.3/components/hal/esp32s3/include/hal/
Any idea? Or should i rollback to version 5.2?
Toolchain 5.3 compilation error
Re: Toolchain 5.3 compilation error
Have you tried cleaning out any vestigial build files
Delete the build folder and any components which may be suspect. All will be rebuilt at build time
So many dependencies, its a wonder that anything can be made to work
Delete the build folder and any components which may be suspect. All will be rebuilt at build time
So many dependencies, its a wonder that anything can be made to work
-
maurizio.scian
- Posts: 26
- Joined: Mon Jun 26, 2023 8:09 am
Re: Toolchain 5.3 compilation error
I completely uninstalled everything, and reinstalled VisualGDB, and updated to toolchain 5.4 (actually it works fine, I thought the reprogramming issue was due to the compatibility of the latest toolchain with VisualGDB).
The only TERRIBLE thing is that with the update to the latest version they added the option to burn the fuses that prevent reprogramming the board through the UART, by DEFAULT... So now I burned 3 boards and I can't use them anymore. Wouldn't it have been better if the default was the insecure option, which allows reprogramming the micro? I'm stuck, i have no word...
So BEWARE! Make sure that the UART ROM download mode option (CONFIG_SECURE_UART_ROM_DL_MODE) is set to "UART ROM download mode (Enabled (not recommended))" when updating your toolchain!!!
The only TERRIBLE thing is that with the update to the latest version they added the option to burn the fuses that prevent reprogramming the board through the UART, by DEFAULT... So now I burned 3 boards and I can't use them anymore. Wouldn't it have been better if the default was the insecure option, which allows reprogramming the micro? I'm stuck, i have no word...
So BEWARE! Make sure that the UART ROM download mode option (CONFIG_SECURE_UART_ROM_DL_MODE) is set to "UART ROM download mode (Enabled (not recommended))" when updating your toolchain!!!
Who is online
Users browsing this forum: Applebot, Bing [Bot], Qwantbot and 5 guests