Add zephyr support to openocd upstream

[zephyrbot]

Reported by Anas Nashif:

See http://openocd.org/doc/html/GDB-and-OpenOCD.html

section

21.6 RTOS Support

(Imported from Jira ZEP-1461)

[zephyrbot]

by Leandro Pereira:

Zephyr will need support code for this. Already have a preliminary patch, will push for review/integration as soon as the OpenOCD part is finished (as there might be a few changes).

[zephyrbot]

by Leandro Pereira:

I'll have a final patch for integration into Zephyr tomorrow morning. The OpenOCD part can be upstreamed after Zephyr 1.7, but it seems to be working, although not exactly like I want it to.

[zephyrbot]

by Anas Nashif:

thanks, we should consider patching the openocd version we have in the SDK with this, openocd upstreaming usually takes some time, they have just released 0.10 one year after 0.9.0 was released ;-(

[zephyrbot]

by Leandro Pereira:

Yeah, my patch applies to 0.10 (HEAD+). I'm not sure if it'll apply cleanly to 0.9.0. Who should I talk to to get this rolling?

[zephyrbot]

by Leandro Pereira:

This has been merged. We're discussing now a way to get the OpenOCD patch at least in the next Zephyr SDK point release.

[zephyrbot]

by Leandro Pereira:

• 0001-Add-support-for-Zephyr-RTOS.patch (size: 13116)

[zephyrbot]

by Leandro Pereira:

Meanwhile, if one would like to patch OpenOCD locally (and use it instead of the one provided in the official SDK), I've attached a patch that applies to the current HEAD (0.10).

[zephyrbot]

by Mark Linkmeyer:

Assigned to Andy Ross for verification.

[zephyrbot]

by Mark Linkmeyer:

Andy Ross , what's the status?

[zephyrbot]

by Andy Ross:

Took a little puzzling, but I was eventually able to get thread-switching working at the gdb prompt on a FRDM-K64F using a patched upstream openocd. Looks good.

[zephyrbot]

by Jammy Zhou:

Andy Ross I'm also trying OpenOCD on FRDM-K64F with CMSIS-DAP for Zephyr debugging. I assume that the Zephyr side patches have been merged into v1.7.0. So besides applying the attached patch in this thread on tip of OpenOCD master branch, any additional changes I need to do? And did you try Eclipse with OpenOCD for Zephyr debugging as well or just use gdb without IDE? Which configure file did you use for OpenOCD on FRDM-K64F? Thanks in advance!

[zephyrbot]

by Leandro Pereira:

Jammy Zhou , I forgot to mention that you also need to edit kx.cfg ($SDK_ROOT/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts/target/kx.cfg), and add the option "-rtos Zephyr" to it at the end of the line that starts with "$_TARGETNAME configure -work-area-phys ...". This was not sent in the patch as that's a patch we should provide in our SDK, and not meant to be sent upstream. (Also, auto detection works, so you should be able to pass, IIRC, "-rtos auto".)

With that change in place, and if you substitute the SDK version of openocd with the one you built ($SDK_ROOT/sysroots/x86_64-pokysdk-linux/usr/bin/openocd), if you issue "make gdb BOARD=frdm_k64f" it should just work.

I have not tested this with anything other than vanilla GDB, as I'm not used to IDEs.

[zephyrbot]

by Jammy Zhou:

Leandro Pereira Thanks for your quick reply. By adding "interface cmsis-dap" to kx.cfg, openocd can basically work here. But it looks like there are still some problems. With "-rtos Zephyr" option in kx.cfg, I got some warning and errors below (I already applied the openocd patch for zephyr support, and added "CONFIG_OPENOCD=y" to $ZEPHYR_BASE/tests/include/test.config for hello_world building).
{color:#14892c}undefined debug reason 7 - target needs reset
Warn : RTOS Zephyr not detected. (GDB could not find symbol '_kernel_openocd_offsets')
...
Error: Please build Zephyr with CONFIG_OPENOCD option set
Error: Please build Zephyr with CONFIG_OPENOCD option set{color}

And with "-rtos auto" option in kx.cfg, I got the warning below.
{color:#14892c}undefined debug reason 7 - target needs reset
Warn : No RTOS could be auto-detected!{color}

Did I miss something?