"Could not initialize project"

hary66 · June 14, 2022, 9:17am

I’m trying to make a fresh install of VScode and PlatformIO on a Raspberry pi 4, but I’m getting this error when trying to open a new project : (VScode and PlatformIO installation already done and went fluently)
Here is the error :

Could not initialize project
PIO Core Call Error: "Resolving lolin32 environment packages...\nTool Manager: Installing espressif/toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3\n\n\nError: Could not find the package with 'espressif/toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3' requirements for your system 'linux_aarch64'"

ivankravets · June 14, 2022, 10:57am

Depends on

github.com/platformio/platform-espressif32

Support cross-arch toolchain packages

opened 06:26AM - 28 Feb 22 UTC

closed 08:42AM - 16 Jun 22 UTC

quentinmit

package management registry

- [x] **Feature Request**. Start by telling us what problem you’re trying… to solve. Often a solution already exists! Don’t send pull requests to implement new features without first getting our support. Sometimes we leave features out on purpose to keep the project small. ### Configuration **Operating system**: Debian 11 on aarch64 **PlatformIO Version** (`platformio --version`): `PlatformIO Core, version 5.2.5` ### Description of problem Some processors support multiple instruction sets (e.g. x64 supports x86 binaries, arm64 supports arm32 binaries). Currently PlatformIO doesn't know that it can use 32-bit packages on a 64-bit system, so it refuses to use a 32-bit package unless Python is run inside `linux32` (which causes `uname` to lie about the architecture, but actually doesn't mean Python is running as a 32-bit binary). This is because platformio is currently just calling `platform.machine()` to get a single architecture name: https://github.com/platformio/platformio-core/blob/834c7b0defe39ff998cd9dc856657aeb837c86ca/platformio/util.py#L92 I'm not sure of the best generic way to solve this; there are many different combinations of architectures that can be used together (e.g. x86 on x64, arm32 on arm64, ppc on ppc64, but also x86 on arm with `qemu-user-binfmt`. Maybe it could default to checking what [multiarch directories](https://wiki.debian.org/Multiarch/Tuples) exist in `/usr/lib` with a configuration override to enable extra architectures? #### Steps to Reproduce On aarch64: ``` # If not already enabled on your system sudo dpkg --add-architecture armel sudo apt update sudo apt install libc6:armel libstdc++6:armel # Now build hello world mkdir /tmp/test cd /tmp/test pio project init --board esp32-c3-devkitm-1 pio run linux32 pio run ``` ### Actual Results `pio run` fails with: ``` Error: Could not find the package with 'espressif/toolchain-xtensa-esp32 @ 8.4.0+2021r2' requirements for your system 'linux_aarch64' ``` `linux32 pio run` succeeds ### Expected Results `pio run` with or without `linux32` succeeds. ### If problems with PlatformIO Build System: Exactly as generated by `pio project init`: **The content of `platformio.ini`:** ```ini [env:esp32-c3-devkitm-1] platform = espressif32 board = esp32-c3-devkitm-1 framework = espidf ``` **Source file to reproduce issue:** ```cpp void app_main() {} ``` ### Additional info See also https://github.com/espressif/crosstool-NG/issues/21 requesting that `espressif/toolchain-xtensa-esp32` be built for aarch64; if that's resolved, you won't be able to use the reproduction steps above, but any other 32-on-64 combination will also be affected.

hary66 · June 14, 2022, 12:37pm

Hi and thanks for giving help.

But what can I do to fix my issue ?
It seems the ““version”: “8.4.0+2021r2-patch3”,” exists, but what to do with it ?
The exchange is by far too specialised so I can understand what to do !
I’m a so humble beginner level user !

maxgerhardt · June 14, 2022, 12:47pm

PlatformIO does not yet have the compiler packages needed for ESP32 projects for your CPU architecture (aarch64, / ARM64), per compatibility matrix. The PlatformIO or Espressif people (who make the toolchain) could solve this.

Very technically you could also solve this if you manage to compile GitHub - espressif/crosstool-NG: crosstool-NG with support for Xtensa for your system, but this is far beyond “simple” even for more advanced users.

A very simple “solution” for your Raspberry Pi 4 is to downgrade the operating system from the 64-bit one to the 32-bit one, so that it falls in the armv8l architecture, for which PlatformIO does have the needed package. So, if you have a spare SD card, download the “Raspberry Pi OS with desktop”, “System: 32-bit” version from Operating system images – Raspberry Pi and flash that and set everything up again with VSCode and PlatformIO.

If this downgrade is not acceptable, then someone (here on the forum, PlatformIO or Espressif people) gets into compiling the toolchain for aarch64, and the wait time on that is undefined.

maxgerhardt · June 14, 2022, 12:55pm

Nah actually don’t do what I’ve written above, the Epsressif people are already uploading the package (Support cross-arch toolchain packages · Issue #753 · platformio/platform-espressif32 · GitHub), so it might be solved very soon. Developing story.

hary66 · June 14, 2022, 1:24pm

Thank you so much.
You’re amazing people indeed !

hary66 · June 15, 2022, 9:12am

Hi.

I’ve seen me-no-dev’s message
But I still have the error.
Does it take more time for the package to be available, or do I need to do something special on my side.

maxgerhardt · June 15, 2022, 9:59am

The PlatformIO staff has to review + accept the package in the registry before it’s visible, that will take a tiny bit. Once done, the green checkmark should appear for Linux ARM64 at PlatformIO Registry.