Hi,
I’m trying to do some things with BBB using CCSv6 and a XDS560v2 USB.
Doing kernel debug and trying to use stop/mode debugging. The .ccxml file I made for BBB (selected the BBB board from the menu list when I set up target configuration) included a .gel file for the CortexA8 and so I stubbed that out as that was causing me problems at first.
Now when I run the debug configuration, it connects to target and loads symbols for the kernel I’m working on but before I can set a hardware breakpoint and click resume to start debugging … the board spontaneously runs (CCS changes from being suspended to running) and I see the board boot in my serial console.
So it is like a watchdog or something is firing and resetting the board … or something like that.
Anyone got experience with using JTAG and CCS with BBB and know what is going on?
Here is basically what I’m doing:
I have a kernel/rootfs etc. that works on SD card.
I hold down button while powering up to make BBB boot from SD.
I stop in u-boot.
Next I run the debug configuration I made for BBB that connects to target and loads kernel symbols.
Before I can do much of anything, the board takes off running when I don’t expect it to.
Regards,
Brian
Just to answer my own question ... I think I discovered part of my
problem. I'm using u-boot 2014.07 and I learned that turned on the
watchdog by default.
In uboot I tried:
U-Boot# mw.l 44e35048 0000aaaa
U-Boot# mw.l 44e35048 00005555
... to disable the watchdog and then I didn't get a reset when I ran my
debug configuration and connected to the target.
But now I can't get hardware brakepoints to work 
Regards,
Brian
A while back, I managed to get CCSV6 and USB560M working with BBB. Hardware breakpoints worked fine. Make sure you build the Kernel configured with the following options:
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_INFO_REDUCED is not set
CONFIG_LOCKUP_DETECTOR is not set
CONFIG_DETECT_HUNG_TASK is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
Currently I’m using a Lauterbach emulator which supports full kernel aware debugging. TI had kernel aware debugging in CCSV4, but they removed that feature in CCSV5 and CCSV6. They keep saying they plan to add it back, but nothing so far.
Regards,
John
Ah, man! I blew away my .config and didn't realize it and
CONFIG_DEBUG_INFO wasn't set! I bet that's it.
I have one project that works (another TI Cortex A8 target) with HW
breakpoints and one that doesn't and was scratching my head wondering why.
I've been able to debug some other TI Cortex A8 stuff with latest mainline
kernel and that appears to be working OK except for the annoying
optimisation jumping around problem. Still good enough to help me
determine what code is being used and what is dead while trying to figure
out dts.
Thanks for the heads up. I was like "I have that set" and double checked
and didn't. Hate it when that happens 
Regards,
Brian
Hey, don’t feel bad. It happens to all of us.
Regards,
John