Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

My first Pico 2 SDK 2.0 issue #400

Open
Some0neS0mewhere opened this issue Aug 24, 2024 · 3 comments
Open

My first Pico 2 SDK 2.0 issue #400

Some0neS0mewhere opened this issue Aug 24, 2024 · 3 comments
Assignees

Comments

@Some0neS0mewhere
Copy link

Hi All,

I've just run through the SDK Getting started guide using a Pico 2 and SDK 2.0 under visual studio code as mentioned in the getting started guide. When running the debug routine using a pico debug probe the following is reported for the blink project:

image

@kilograham kilograham transferred this issue from raspberrypi/pico-sdk Aug 24, 2024
@will-v-pi
Copy link

Yes, this is a known issue with the Arm toolchain gdb on Windows - but it shouldn’t actually affect functionality. Other than this warning, did the debugging work fine?

@Some0neS0mewhere
Copy link
Author

Some0neS0mewhere commented Aug 25, 2024

Hi will-v-pi,

Yes all seems to work fine with the Pico 2 under vs code and the Pico extension (SDK 2) when trying the blink example.

I am having another issue however with blink and blink_w when switching to either the original Pico and/or the Pico W. This issue is even after installing Zadig. Perhaps this issue is meant for a different platform.

The issue after installing Zadig is:

image

Cheers

@lurch
Copy link
Contributor

lurch commented Aug 25, 2024

Yeah, issues with picotool should be reported at https://github.com/raspberrypi/picotool/issues please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants