Error Recompiling: atmelsam @ 8.0.0

Development Platforms
,
1

Hi, i’m a highschool student trying to build this project for school: AI Smart nose

Part of the project requires us to recompile the provided source code after making changes to the library folder: source code on github

We’re trying to use platformio on VS code to recompile our code into firmware (we are complete novices no experience whatsoever) and we ran into this issue when trying to make a build off the file


Processing seeed_wio_terminal (platform: atmelsam @ 8.0.0; board: seeed_wio_terminal; framework: arduino)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Platform Manager: Installing atmelsam @ 8.0.0
UnknownPackageError: Could not find the package with 'atmelsam @ 8.0.0' requirements for your system 'windows_amd64'

not sure what atmelsam @8.0.0 is or how to download it? Also what do they mean by package? is that like a file or dependency we need to have on the computer beforehand?

Please help we’ve got no idea what we’re doing lol

2

The 8.0.0 version is so ancient (May 30, 2022) that PlatformIO deleted it from the registry (compare PIO registry, oldest one is 8.1.0).

However, it’s still on Github. You can reference it by using

platform = https://github.com/platformio/platform-atmelsam/archive/refs/tags/v8.0.0.zip

in the platformio.ini.

If that works, please check if platform = atmelsam@8.3.0 also works. It should be a straightforward upgrade.

3

hello, thank you for your advice. We tried coping and pasting that link in the platformio.ini in place of the original platform = atmelsam@8.0.0 but we’re still getting the same error. Any other methods we could take?

4

The very same error? That should be impossible. Compiling a new project with atmelsam@8.3.0 for the seeed_wio_terminal works just fine.

What’s the error? What’s the full platformio.ini?

grafik
grafik1200×800 59.8 KB

5

Hi again,
we gave it another try again today, and this time we didn’t get that same error thankfully. No clue why is wasn’t working yesterday, must’ve been a mistake on our side of things lol. Thank you for your help!