Description
Hello,
I tried to install arduino-esp32 2.0.0-alpha for Sloeber IDE (4.3.3.202004230915) on an openSuSe 15.2 x86_64 (5.3.18-lp152.72-default Kernel) machine.
I added https://github.com/espressif/arduino-esp32/releases/download/2.0.0-alpha1/package_esp32_dev_index.json
to the list of third party index urls in "Arduino->Third party index url's" in Preferences . Afterwards I selected the esp32-2.0.0-alpha1 entry in the "Arduino->Platforms and Boards" in Preferences and hit "Apply".
But "Adopting Arduino Board Platform" in step "Installing Arduino Board Plattforms" returned with the following error:
Failed to install esp32
No valid system found for "mkfatfs".
I took a look into the package_esp32_dev_index.json
and found that the entry for mkfatfs
reads
{
"version": "0.3.6",
"name": "mkfatfs",
"systems": [
{
"host": "i686-pc-linux-gnu",
"url": "https://github.com/lorol/arduino-esp32fatfs-plugin/raw/master/extra/mkfatfs.tar.gz",
"archiveFileName": "mkfatfs.tar.gz",
"checksum": "SHA-256:41dc0346a38d6aab5674d4301937868e69471b69d8317ed667d2eeb7c4a077ee",
"size": "102575"
},
{
"host": "i686-mingw32",
"url": "https://github.com/lorol/arduino-esp32fatfs-plugin/raw/master/extra/mkfatfs.zip",
"archiveFileName": "mkfatfs.zip",
"checksum": "SHA-256:966f378da8bba524197d7d8a919e93b21b4680ead03ae69cac8bb56f8ec864a6",
"size": "612169"
}
]
}
missing an entry for x86_64-pc-linux-gnu
.
Is this entry not required, supported or missing out of some other reason?
If it is simply missing please add it.
Sloeber is quite aggressive in terms of configuration strictness. So it might be that it tries to install something not required.
PS: I added it assuming I could reuse the entry for "i686-pc-linux-gnu", but that failed changing the error message to
Failed to install esp32
Failed to extract tar.bz2. "/home/Sebastian/programme/eclipse/sloeber/Sloeber/arduinoPlugin/downloads/mkfatfs.tar.gz".
Invalid archive: it must contain a single root folder
which is correct, the archive contains a single file called "mkfatfs", instead of the usual folder.
As soon as I have time I am going to provide it with a dummy on my own Webserver to see if this resolves the issue as workaround.