# Relationship of openocd to debug options

I recently purchased a Segger jlink pro, and in attempting to make NetBeans talk embedded gdb, I have run across numerous blogs about the use of openocd. My initial understanding is that openocd was meant for use with cheap debuggers, yet I see jlink support.

At this point for me, the arm gdb exe connects to the jlink gdbserver though localhost:2331 which connects to the target via jlink. Everything mostly works, so what more would openocd do at this point? Is there something openocd is doing that Segger has not?

For reference, my target is an arm cortex a5.

• This questions isn't really specifically answerable. Generally OpenOCD is made to handle a wide variety of adapters and targets and to be extensible and patchable by the user. If you're happy with what you are using and don't mind spending $998 rather than$5-50 per adapter, no need for it, though if you are unhappy it might be worth looking at OpenOCD and compatible adapters. – Chris Stratton Jan 1 at 19:47
• What is wrong with this question? Isn’t the point of the site to ask questions that a person doesn’t have enough context to know how to ask all the time? There is no embedded stack exchange but there should be. Anyway, the above comment is helpful, thanks. – Erik Friesen Jan 2 at 4:08
• Questions on SE sites must be specifically answerable - this one is not. If you want to have a comparative discussion you need to go to a discussion site, perhaps somewhere like eevblog or similar. – Chris Stratton Jan 2 at 5:19