Comments (5)
Which GDB server and microcontroller family are you using? I know the st-util server has some issues where it doesn't properly report all of the registers (and reports a few that don't exist or are incorrectly named).
from cortex-debug.
Hi Marus, thanks for coming back!
I was testing this on a STM32F405RG with a BMP as programmer.
from cortex-debug.
OK - I'll look into it - but I expect its another case where the GDB server (the one built into the probe in this case) doesn't report all registers. Might end up being something that will need to reported to the BMP team.
from cortex-debug.
Hi - I just took a peak with my BMP here - and as I expected those 4 registers are not reported by the BMP GDB server. Unfortunately since the processor core registers are not memory mapped I do not believe I can work around the GDB server not reporting them correctly/completely.
If you need access to those 4 registers I would suggest filing an issue with the BMP team at https://github.com/blacksphere/blackmagic - once they have fixed it in their firmware it should appear properly in the Cortex-Debug extension.
Wish I had better news and could fix it for you quickly and easily.
from cortex-debug.
Thank you for looking into this, I have already contacted them with reference for a fix for it
from cortex-debug.
Related Issues (20)
- RTT support for Black Magic Probe HOT 1
- SEGGER rtt connection ended immediately after lunch the cortex-debug
- Take ipAddress from environment variable HOT 1
- gdbsever debugging is suddenly unavailable, everything was fine before
- loadFiles not working as expected with PE Micro servertype HOT 3
- Default value of "Live Watch Refresh Rate" should be a number HOT 1
- Installed extension failure
- Peripherals, registers, memory and disassemble all read "There is no data provider registered that can provide view data." when using the attached SVD file. HOT 6
- Missing variables in the Variables View HOT 1
- Live watch not updating value on esp32s3 with esp-prog; "Warn : [esp32s3.cpu0] target not halted" HOT 2
- Windows/WSL, debugger attempts to open unix-style file HOT 2
- Project status, is it still actively developed/maintained? HOT 2
- Status of this extension HOT 3
- GDB session ended. but the debug toolbar won't close. HOT 13
- OpenOCD stdout not showing up in the DEBUG CONSOLE HOT 9
- To what extent does this extension rely on plugins for the JLink GDB server? HOT 4
- Peripheral Register/SVD Error HOT 1
- Slow listing of threads when hitting breakpoint HOT 6
- ram .data section error (all FF) when debug (run to main) armclang build + jlink HOT 4
- NUCLEO-H503 Debug Support HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cortex-debug.