[dcomer]

I should have also mentioned that a “regular” C++ “hello world” project works fine.

[dcomer]

Hum, I would have thought the datasheet for the specific part was the source, which does show the timer register definitions for a specific part (with respect to the question I have). That said, I suppose that would mean you guys would have to have resources to monitor all device datasheets that VisualGDB  supports and update files for the individual revisions. Compilers such as Rowley’s CrossWorks for ARM does this in their BSP’s. So, I would hope that your guys would become successful enough to a) Have that expertise in-house, or, b) successful enough to have a relationships with the various manufacturers TI to foster inside support in this respect.

Don’t take this as a complaint/criticism. Just a thought process I am going through on how I resolve other issues that come up similar to this. VisualGDB a far better tool than, say Code Compose, to program in (my opinion). Rowley CrossWorks is great, but I still like VisualGDB better in terms of user experience.
Dave

[dcomer]

Looks like the RCGCTIMER register needs updating as well. There should only be bits R0-R5 defined where there are now 8 bits; R0-R7.

 

Dave

[dcomer]

Hello again (or que Pasa as we say in this part of the world):

 

I believe I found another register error. The TM4C123GH6PGE has 6 16/32 and 6 32/64 bit timers. The register map has 8 16/32-bit timers(TIMER0-TIMER7) timers listed and should have only 6 (TIMER0-TIMER5). The invalid timers (TIMER6 and TIMER7) are mapped into undefined memory (or at least, unpublished).

Thanks for your help!

Dave

[dcomer]

One bug did pop up when I reloaded. After successfully re-loading the update, the application is hung on the “Manage VisualGDB Packages” dialog. By hunk, I mean I cannot close the dialog due to a hidden window preventing any action with the “BEL” sounding. I’ve looked at all windows behind (Alt_TAB) and there is not indication of another active dialog.

 

Dave

[dcomer]

Thanks You. By the way, I did figure out where the definitions were. I’m sure you fixed it all, but just wanted to mention, pretty much everything in the 0xc001.cxxx memory space were incorrectly mapped. I will download your update and test. I’ll let you know if I see any other issue.

 

Dave

[dcomer]

Ah, got it now. I was looking in the right-click menu for the project. I did not realize that I should have, instead, been right-clicking on the VisualGDB settings project item, looking on the left hand side of the tabbed dialog that says “Debug Settings, and in the middle of tab with the debug settings indeed there is the “Run debugger as root with sudo (this can cause debugging to hang)” check box. I’m being a little verbose in my reply should someone else have the same issue. I’d include an image here but not sure it would remain with my reply.

Thanks for your help. I LOVE VisualGDB. It is perfect for the development I do!

 

Dave

[dcomer]

Sorry, I know that was an old post. I have the same issue, but I do not see “run debugger as root with sudo”. Is this accessable via the VW (2015 in my case) IDE, or a VisualGDB dialog. I’ve looked all over and do not see this option.

 

Thanks,

 

Dave

[Author]

Posts