I have the most recent Intel MacBook pro with latest MacOS etc. which I use for ESP32 development rather than my M2Pro MBP for various reasons (compiles faster and supports running virtual MacOS's, Linux, Windows, etc. Anyhow, works fine until the minute I updated to 2.3.3 IDE. Now it returns the following error:
bash: /Users/recurry/Library/Arduino15/packages/esp32/tools/esptool_py/4.8.1/esptool: Bad CPU type in executable
exit status 126
Compilation error: exit status 126
On checking it out it appears esptool_py 4.8.1 is for Apple silicon only. However, 4.5.1 is also present under the esptool_py folder and it works fine.
I suspect this error is related to the update because that's the only thing I did before I started getting the error.
I could move the files around or go back to an older version of the IDE but I'd rather have an official fix. Can someone advise on a fix for this.
I can not help you as I don't have a Mac and I don't use ESP32 boards.
What was the previous version?
I have some doubts that it is the update of the IDE; it's more likely that it is an update of the ESP32 board package. If you did update, did you update that on purpose or by accident?
If you did update, you can check if the changes between the previous version that you used and the current one are relevant and roll back if desired.
Hi @recurry. I see that esptool 4.8.1 is only used by the development version of the "esp32" boards platform. Is there a specific reason you are using the development version?
The development version is intended to be used by those who are contributing to the development work on the platform or beta testing it. It is not intended to be used by normal users.
It is possible that they will produce an Apple Silicon build of esptool by the time they are ready to make a production 3.1.0 release of the "esp32" boards. So the solution might be to simply use the latest production release 3.0.7 until 3.1.0 comes out.
You can install 3.0.7 by replacing your current boards Manager URL with the URL provided under the "Stable release link" section of the installation documentation here:
Thanks, not sure why I had the developers link installed. I also had the stable link. I seem to remember there was a reason but can't remember now. Anyhow this solved the problem. It's odd that it only showed up after the update though. Thanks so much for the quick, clear, concise, and helpful reply!