[kicsoft]

Thank you for the quick help on this! I am impressed and very pleased with this high level of support.

I will patch the address_mapped.h for now like suggested in the PicoSDK bug report.

Cheers

[kicsoft]

Looks like the attachments were rejected.

I renamed the commands to .txt to see whether that helps…

Attachments:

You must be logged in to view attached files.

[kicsoft]

Just now I tried to disconnect the Segger JLink and simply drag the uf2 output file from the VisualGDB output folder to the RPI-RP2 drive but it still crashes just like before with the debugger…

Both projects use the latest PicoSDK 1.1.2.

Please find attached the elf files from the two builds.

And I have tried to export the configuration and build commands from VisualGDB as well, but I am not sure how to get these from the PicoSDK Visual Code build system.

[kicsoft]

Hi again,

Today I installed the Pico SDK and development tool using the latest release of “Pico Setup for Windows” found here: GitHub – ndabas/pico-setup-windows: Quickly get started with Raspberry Pi Pico/RP2040 on Windows

I then followed the getting started guide and got VS Code loading the pico-examples and after a complete rebuild of all samples and the necessary tools, I then loaded the unique_board_id.uf2 onto my Pico and this worked out of the box. I could now see the Unique ID on the serial debug port.

However: when I compile and run the same example that was created using the VisualGDB Pico wizard then it still crashes.

So I have to conclude that something is wrong/missing in the VisualGDB project when I create it from the exact same sample in the PicoSDK.

I installed my Segger JLink and used the SWD debugger in Visual Studio 2019 with VisualGDB in order to find out what happened and I see that an “Received a SIGINT: Interrupt” is thrown when the initialization code tries to read the ID from the flash (when trying to set the CS low on the QSPI bus).

Here is the stack trace:

0xfffffffe
<signal handler called>
> hw_write_masked C++ (gdb)
flash_cs_force C++ (gdb)
flash_do_cmd C++ (gdb)
flash_get_unique_id C++ (gdb)
_retrieve_unique_id_on_boot C++ (gdb)
runtime_init C++ (gdb)
platform_entry C++ (gdb)

 

It looks to me like the _retrieve_unique_id_on_boot() function might be called too early before the QSPI GPIO configuration has been initialized or perhaps something else is missing!?

Cheers

[kicsoft]

Thanks for the quick reply!

I was thinking the same that I probably need to build the sample manually directly using the PicoSDK. However I am a bit hesitant to install the C/C++ PicoSDK development tools because I am worried it break my VisualGDB toolchain settings.

Are you aware of any know issues (with respect to already having a working VisualGDB setup) if I run the Windows PicoSDK toolchain installer from the Raspberry Pi Pico forum? It will afaik install Microsoft Code and the ARM compiler and possibly change environment variables.

[Author]

Posts