- This topic has 8 replies, 2 voices, and was last updated 8 years, 1 month ago by
.
-
Posts
-
I’m using the evaluation version of VisualGDB for a Texas Instrument “Launchpad” board, the TIVAC123GXL using the TM4C123GH6PM microcontroller.
It connects to the board and programs the micro fine.
Debugging is where I’m having problems. I have OpenOCD in use. The Hardware Register window is greyed out as is the Watch1 window.
I’ve attached a link to a screenshot.
https://drive.google.com/file/d/0BzJ7UeYkYzFrWkpzR1ZRSUFMVFE/view?usp=sharing
Hi,
This is actually by design and replicates the regular VS debugging experience. The watch window and hardware registers are only active when the target is stopped (e.g. at a breakpoint). To view the variables while the target is running, please use the Live Variables window.
Yes, of course, sorry about that. I’ve done plenty of debugging with AVR in Atmel Studio but have been away from it for a few months, and am forgetting the basics (new busy job and learning ARM now).
I’ve put breakpoints at various points in my code. The code simply turns each of the red, green, blue LEDs on in turn and switches them off for a certain time in between. The LEDs on the board are doing exactly as the code tells them to do and go on and off as I use the debugger to run to the breakpoints in turn. However in the Hardware Registers watch window the GPIO data register (PORT F) is always at zero whether the LEDs are on or off. The DIR register is giving a correct value of 0xE for Port F pins 1, 2, 3 being set to output.
Am I overlooking something.
Quite like this plugin for VS by the way. I use VS for doing a little C# and like the idea of using the same quality IDE for the ARM.
Keith.
I created a uint32_t variable to read PORTF data register, and got the exact value I was expecting, e.g. this
GPIOPinWrite(GPIO_PORTF_BASE, GPIO_PIN_3, GPIO_PIN_3);
portF_data_copy = GPIOPinRead(GPIO_PORTF_BASE, 0xFF);
would set portF_data_copy variable to 0x00000008 which is pin 3 high.
So it seems the value is there in PORTF data register but it doesn’t get displayed in the Hardware Registers watch window.
Is this normal ?
Keith.
Just a final update (sorry, can’t edit my earlier posts).
I ran the same code in Code Composer Studio and the hardware register watch window in that IDE did update the PortF data register display with the value I was expecting, so I’m guessing something isn’t right in the VisualGDB setup.
Keith.
OK, guess I’ll have to assume this a bug which can’t be fixed. I see plenty other questions being addressed while this one remains unanswered.
Hasn’t took long for my evaluation of VisualGDB to be over.
Back to Code Composer Studio for now.
Hi,
Sorry, an overnight fix on Sunday night is a bit beyond our capabilities.
We have investigated this and confirmed a bug in our register definitions for Tiva devices. We have updated our BSP with the correct definitions.
You can install the latest BSP via Tools->Manage VisualGDB Packages.
I wasn’t asking for or expecting an overnight fix. However, a simple “we’ll have a look into it” and I’d wait a week before checking up on what’s happening.
When I see support answering a few other questions (all after mine) while mine doesn’t even get acknowledged, you are left feeling like the matter is being ignored.
I’m a member of a forum for a PC based CNC product and this is how they operate, works good.
Just something for you to consider, it’s your business, your product, and it’s up to you how you deal with customers.
Anyway, thanks for the answer.
Edit:
Just tried it out as per your instructions and seems to be working good now. Thanks again.
- You must be logged in to reply to this topic.