Hi Erich,
arm-none-eabi-gdb is definitely running, and it's taking 40% of the CPU time. I've also got gdb output in the console. Here's what I see:

I can enter commands on the left console, but they don't get any responses. I can't do anything with the debugger console on the right. What am I doing wrong?
I'm not having a good day so far - I'm trying to step into a function, and if I do it with F5 the target resets and the debugger loses its connection. If I turn on instruction stepping mode I can get into the function and hit F8 and *then* it will run to its breakpoint like it's supposed to. I'm even using the blue debug button, despite the fact that it takes 4x as long to launch because it makes me choose (twice!) which debug configuration to use each time, and *sometimes* it also makes me select the probe as well.
But one thing at a time. What's up with the gdb commands?
Scott