Hello Friends,
I'm using a second Rpi Pico (DBG Pico) to debug the main Rpi Pico (MAIN Pico).
Yesterday I've been able to connect and read UART from MAIN Pico using the COM port of DBG Pico.
For some reason I've made a mistake and moved the DBG Pico UART end wires to other pins of MAIN Pico, but before flashing the new configuration (some pins where I connected the UART were High or Low state...) , so the DBG Pico stop to work (maybe a short circuit, no green light at the end).
I replaced the board and now I'm using a new DBG Pico, but some strange behaviour I noticed...
On VS Code once the debugger is launched, I'm only able to stop the thread but not pheripherals. I noticed that today because I included a PWM on GPIO 25 (green led). It doesn't stop.
If I stop the debugging session, PWM on GPIO25 continues flashing. But if I try to run again the debugger, I receive an error "Failed to launch GDB: Error finishing flash operation (from target-download)".
Before to burn the first DBG Pico, I don't remember to receive that kind of messages, the debugger was capable of restart and reload the new firmware.
Then... to use the debugger, I need to unplug the DBG Pico and plug again.
So this are my questions:
Is it enough to declare PICO_DEFAULT_UART_TX_PIN and PICO_DEFAULT_UART_RX_PIN to change UART position?
Is there a way to stop all clock signals from pheripherals during debugging?
Is it normal that the MAIN Pico keeps running it's program after debugging session stops?
If the DBG Pico can start the first debugging session and load the firmware then, I suppose, there is no damaged pins.
I'm using a second Rpi Pico (DBG Pico) to debug the main Rpi Pico (MAIN Pico).
Yesterday I've been able to connect and read UART from MAIN Pico using the COM port of DBG Pico.
For some reason I've made a mistake and moved the DBG Pico UART end wires to other pins of MAIN Pico, but before flashing the new configuration (some pins where I connected the UART were High or Low state...) , so the DBG Pico stop to work (maybe a short circuit, no green light at the end).
I replaced the board and now I'm using a new DBG Pico, but some strange behaviour I noticed...
On VS Code once the debugger is launched, I'm only able to stop the thread but not pheripherals. I noticed that today because I included a PWM on GPIO 25 (green led). It doesn't stop.
If I stop the debugging session, PWM on GPIO25 continues flashing. But if I try to run again the debugger, I receive an error "Failed to launch GDB: Error finishing flash operation (from target-download)".
Before to burn the first DBG Pico, I don't remember to receive that kind of messages, the debugger was capable of restart and reload the new firmware.
Then... to use the debugger, I need to unplug the DBG Pico and plug again.
So this are my questions:
Is it enough to declare PICO_DEFAULT_UART_TX_PIN and PICO_DEFAULT_UART_RX_PIN to change UART position?
Is there a way to stop all clock signals from pheripherals during debugging?
Is it normal that the MAIN Pico keeps running it's program after debugging session stops?
If the DBG Pico can start the first debugging session and load the firmware then, I suppose, there is no damaged pins.
Statistics: Posted by mathestro — Thu Mar 28, 2024 10:53 pm — Replies 0 — Views 29