Failure generating pio header files with Pico SDK v 2.1.1

[deonm]

When  building project’s containing Raspberry Pi Pico PIO files, failure occurs when executing  pico_generate_pio_header,

Below is the the build output log from the pio_blink example project using Pico SDK v2.1.1

Selecting Pico SDK v2.1.0 or v2.0.0 the project builds correctly.

`

Run “C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe ” in directory “C:\Temp\code\pico_pio/build/VisualGDB/Debug” on local computer
C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe
[1/64] Generating blink.pio.h
FAILED: blink.pio.h C:/Temp/code/pico_pio/build/VisualGDB/Debug/blink.pio.h
C:\WINDOWS\system32\cmd.exe /C “cd /D C:\Temp\code\pico_pio\build\VisualGDB\Debug && C:\Users\deon\AppData\Local\VisualGDB\PicoSDK\2.1.1-Package\prebuilt\pioasm\bin\pioasm.exe -o c-sdk -v 1 C:/Temp/code/pico_pio/blink.pio C:/Temp/code/pico_pio/build/VisualGDB/Debug/blink.pio.h”
[2/64] Building ASM object pico-sdk/src/rp2350/boot_stage2/CMakeFiles/bs2_default.dir/compile_time_choice.S.obj
ninja: build stopped: subcommand failed.
————————————————————-
Command exited with code 1
Executable: C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe
Arguments:
Directory: C:\Temp\code\pico_pio/build/VisualGDB/Debug
Environment: LANG=en_US.UTF-8|PATH=C:\SysGCC\arm-eabi\bin;C:\SysGCC\arm-eabi\bin;%PATH%;C:\Users\deon\AppData\Local\VisualGDB\PicoSDK\2.1.1-Package\prebuilt;C:\Users\deon\AppData\Local\VisualGDB\Python-3.8.10|TOOLCHAIN_ROOT=C:/SysGCC/arm-eabi|EFP_BASE=C:/Users/deon/AppData/Local/VisualGDB/EmbeddedEFPs|TESTFW_BASE=C:/Users/deon/AppData/Local/VisualGDB/TestFrameworks|TESTFW_BASE_LOCAL=C:/Users/deon/AppData/Local/VisualGDB/TestFrameworks
Command-line action failed

========== Project Build Summary ==========
pico_pio built in 00:00
========== Build: 0 Succeeded, 1 Failed, 0 Skipped ==========

`

 

• This topic was modified 3 days, 20 hours ago by deonm.

[support]

No problem, we have managed to reproduce and fix it. Turns out, the latest SDK had some changes interfering with our previous patches, so we ended up shipping prebuilt tools with external dependencies.

We have rebuilt the package on our side. Feel free to delete the %LOCALAPPDATA%\VisualGDB\PicoSDK\2.1.1-Package folder and create another project via the VisualGDB Project Wizard to re-download the SDK. Once downloaded, both new and old projects should work just fine.

[deonm]

Thank you,

I have tried to re download the SDK v2.1.1 but get the error below. The error does not occur when downloading any other SDK version,

 

`

VisualGDB version: 6.0.108.5338
—————— py2+o ——————
py2+o: Some packages could not be installed:
The remote server returned an error: (404) Not Found.
Please check the error log for more details.
at py2.j1.a(zz a)
at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass2_0`1.<RunAction>b__0()
trace=[py2+j1.a:0, VisualGDB.Common_GUI.WPF.ItemizedProgressWindow+<>c__DisplayClass2_0`1.<RunAction>b__0:0]

`

[support]

Hi,

Please try deleting %LOCALAPPDATA%\VisualGDB\PackageCatalog.xml. It should reset the cache and get the correct package.

[deonm]

Hi.

I did that and it got me up and running with SDK v2.1.1

Thanks again

[Author]

Posts