How do I edit the command that is run at build?

[NonRidiculousAdjective]

On a fresh project on Nobara Linux, I tried to run the example through USB with SPI and I2C code but I am getting this output:

Executing task: /home/user/.pico-sdk/picotool/2.1.1/picotool/picotool load /home/user/Documents/Pico/PiCon/build/PiCon.elf -fx 

No accessible RP-series devices in BOOTSEL mode were found.

but:

RP2040 device at bus 3, address 5 appears to be in BOOTSEL mode, but picotool was unable to
    connect. Maybe try 'sudo' or check your permissions.

Where can I add sudo, there's a lot of config files, not sure which one contains this. I am just a little overwhelmed.

[will-v-pi]

The tasks are in .vscode/tasks.json as they're just normal VS Code tasks, so you can edit them there. But a better fix than adding sudo would be to add the udev rule from picotool (https://github.com/raspberrypi/picotool/blob/master/udev/99-picotool.rules) to your /etc/udev/rules.d/ folder (or the equivalent for your distro), which allows you to use picotool without sudo.

Edit: The udev rules are mentioned in the readme https://github.com/raspberrypi/pico-vscode?tab=readme-ov-file#linux

[NonRidiculousAdjective]

Tried to add the udev rule, did not work, likely did something wrong, so I tried with sudo instead

"label": "Run Project",
            "type": "process",
            "command": "sudo ${env:HOME}/.pico-sdk/picotool/2.1.1/picotool/picotool",
            "args": [
                "load",
                "${command:raspberry-pi-pico.launchTargetPath}",
                "-fx"
            ]

Yet I am getting this error:

Executing task: sudo /home/user/.pico-sdk/picotool/2.1.1/picotool/picotool load /home/user/Documents/Pico/PiCon/build/PiCon.elf -fx 


The terminal process failed to launch: Path to shell executable "sudo /home/user/.pico-sdk/picotool/2.1.1/picotool/picotool" does not exist. 

Even though the folder and the file both exist

[will-v-pi]

Yes, you'll probably need to make it a shell command instead of a process, and move the args into the command - see https://code.visualstudio.com/docs/debugtest/tasks#_custom-tasks for more details on writing custom tasks in tasks.json

Also, if the udev rule is not working, try renaming it to 60-picotool.rules - see raspberrypi/picotool#199

Closing this, as we don't plan on doing anything to automatically fix this on Linux, beyond linking to the udev rules