Hi.
I am trying to biuld a drone using an esp32devkit as the fc. I have followed the instructions on [AP_HAL_ESP32] (ardupilot/libraries/AP_HAL_ESP32/README.md at master · ArduPilot/ardupilot · GitHub) for porting ardupilot and was able to reach step 5 without much problem. However when attempting to run ESPBAUD=115200 ./waf plane --upload
it failed due to Build failed -> task in 'esp-idf_flash' failed (exit status 1): {task 140365409052144: cmake_build_task -> }
and stated that 0 serial ports found.
I have gone through the troubleshooting page and what i think is all the common causes for this problem eg. switching ports, cables, installing the correct driver for my computer and closing all other windows. The device is recognized in my device managers and i am unsure of how to fix this.
Thanks for any help.
Which esp32 dev module you are using with which on Board USB to Serial Converter.
Did you tried to program the esp32 with some other tool (for example with esp32 on arduino.ide)
Are you using Windows building in WSL?
I usually don’t upload through WSL but locate the compiled files, look at the corresponding flash locations and flash it manually with the ESP Flasher: Flash Download Tool User Guide - ESP32 - — ESP Test Tools latest documentation
Hi
I currently do not know the Dev kit(trying to find out from the teach who gave it to me). it is using a cp2102 USB to serial converter and uploading through Arduino. Ide works with the same cable and com port.
Yes sorry forgot to say i am using WSL on windows 11 running ubuntu. I have managed to use the flash download tool to read the chip data but im not sure how to find the compiled files and there flash location.
Did you tried to press the boot button during the time the esp_idf_flash search for the device?
Yes, i believe its a problem with with Linux accessing com ports or some sort of error with the installation of the esp_idf. From what I’ve read wsl is not normally able to access com ports?
I run the esp_idf also on WSL without this problems. But I know that some esp devboards have a problem to enter bootloader mode automatically. These boards need to hold the boot button pressed until the flashing starts. Also a external 10yF Cap on pin EN to GND can help