Hi all,
My setup :
Suse Linux machine running vscodium and gdb -> over network to second Linux machine running openocd and an official picoprobe connected to my target board. This allows me to program remotely without having to have the target board near my working machine. This works nicely.
However in my current project about 1/4 of the time when I launch with Run->start debugging I end up with the source trace in :
Specifically on the hardfault line. The rest of the time it seems to work without problems. My project is mostly running from flash, with some speed critical sections tagged with __no_inline_not_in_flash_func() so they go into RAM.
Board is a Pico 2, so RP2350, and have tried several picos, and get the same result which suggests it's not down to the hardware.
Anyone know what may be causing this?
Cheers.
Phill.
My setup :
Suse Linux machine running vscodium and gdb -> over network to second Linux machine running openocd and an official picoprobe connected to my target board. This allows me to program remotely without having to have the target board near my working machine. This works nicely.
However in my current project about 1/4 of the time when I launch with Run->start debugging I end up with the source trace in :
Code:
#if !PICO_MINIMAL_STORED_VECTOR_TABLE// these are separated out into individual BKPT instructions with label for claritydecl_isr_bkpt isr_nmidecl_isr_bkpt isr_hardfaultdecl_isr_bkpt isr_svcalldecl_isr_bkpt isr_pendsvdecl_isr_bkpt isr_systick#endifSpecifically on the hardfault line. The rest of the time it seems to work without problems. My project is mostly running from flash, with some speed critical sections tagged with __no_inline_not_in_flash_func() so they go into RAM.
Board is a Pico 2, so RP2350, and have tried several picos, and get the same result which suggests it's not down to the hardware.
Anyone know what may be causing this?
Cheers.
Phill.
Statistics: Posted by PhillHS — Wed Feb 18, 2026 9:05 pm — Replies 0 — Views 26