# My environment
Macbook Air M2 (Sequoia)
Raspberry Pi Pico (RP2040)
I am building a remote debugging environment using OPenOCD + GDB.
I have set up a debug probe on Pico.
I have wired the official docs and it works fine.
-------
Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, see
http://openocd.org/doc/doxygen/bugs.html
For bug reports, see -------
GNU gdb (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 14.2.90.20240526-git
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to modify and redistribute it.
There is NO WARRANTY to the extent permitted by law.
# My problem
I start OpenOCD and GDB and the program starts with the following command.
The timer interrupt process I set up is evaluated without any problems.
GDB> reset monitor
However, the timer interrupt process is not evaluated with the following command
GDB> monitor reset init
GDB> continue
# What I want to solve
Monitor reset does not allow me to set breakpoints or check variables.
The only way to debug is to put the process of flashing the LED in the code.
I would like to put a break or step execution on the interrupt process.
Has anyone encountered the same problem as me and solved it?
Please let me know how to solve it.
# Postscript.
I have found the register settings to be.
By setting a value in the timer register DEBUGPAUSE, the timer worked even when using DebugProbe.
DEBUGPAUSE.DBG0 <-- 0x00
DEBUGPAUSE.DBG1 <-- 0x00
Code added to the timer configuration.
Is this correspondence correct?
Macbook Air M2 (Sequoia)
Raspberry Pi Pico (RP2040)
I am building a remote debugging environment using OPenOCD + GDB.
I have set up a debug probe on Pico.
I have wired the official docs and it works fine.
-------
Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, see
http://openocd.org/doc/doxygen/bugs.html
For bug reports, see -------
GNU gdb (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 14.2.90.20240526-git
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to modify and redistribute it.
There is NO WARRANTY to the extent permitted by law.
# My problem
I start OpenOCD and GDB and the program starts with the following command.
The timer interrupt process I set up is evaluated without any problems.
GDB> reset monitor
However, the timer interrupt process is not evaluated with the following command
GDB> monitor reset init
GDB> continue
# What I want to solve
Monitor reset does not allow me to set breakpoints or check variables.
The only way to debug is to put the process of flashing the LED in the code.
I would like to put a break or step execution on the interrupt process.
Has anyone encountered the same problem as me and solved it?
Please let me know how to solve it.
# Postscript.
I have found the register settings to be.
By setting a value in the timer register DEBUGPAUSE, the timer worked even when using DebugProbe.
DEBUGPAUSE.DBG0 <-- 0x00
DEBUGPAUSE.DBG1 <-- 0x00
Code added to the timer configuration.
Code:
timer_hw->dbgpause = 0x0;
Statistics: Posted by kamuycikap — Sat Oct 19, 2024 4:52 pm — Replies 0 — Views 14