EvgeniiDidin
commented
5 years ago Hi @jshoen, I am sorry for late response. I prepared a patch, which introduces support of arcv2 for Zephyr in openOCD: https://github.com/foss-for-synopsys-dwc-arc-processors/openocd/commit/dbe09528bf6a7358bfc7b4ffd451747c384d304c Now the openocd log is:
Info : 1689 3902 Zephyr.c:673 Zephyr_detect_rtos(): Zephyr: does it have symbol 0 (mandatory)?
Info : 1690 3902 Zephyr.c:673 Zephyr_detect_rtos(): Zephyr: does it have symbol 1 (mandatory)?
Info : 1691 3902 Zephyr.c:673 Zephyr_detect_rtos(): Zephyr: does it have symbol 2 (mandatory)?
Info : 1692 3902 Zephyr.c:673 Zephyr_detect_rtos(): Zephyr: does it have symbol 3 (optional)?
Info : 1693 3902 Zephyr.c:681 Zephyr_detect_rtos(): Zephyr: all mandatory symbols found
Info : 1694 3902 rtos.c:275 rtos_qsymbol(): Auto-detected RTOS: Zephyr
Info : 1695 3902 Zephyr.c:700 Zephyr_create(): Zephyr: looking for target: arcv2
Info : 1696 3902 Zephyr.c:707 Zephyr_create(): Zephyr: target known, params at 0x8de2f8Currently I am working on correctly reading Thread information: (gdb): info threads
Also I have a question. When you tried to run your binary have you seen such messages in serial port:
***** Exception vector: 0x6, cause code: 0x10, parameter 0x0
Address 0x40
EV_ProtV: Normal vector table in secure memory
Current thread ID = 0x80000320
Faulting instruction address = 0x40
Fatal fault in essential thread! Spinning...or
**FATAL: ***** Exception vector: 0x6, cause code: 0x10, parameter 0x0
FATAL: Address 0x40
FATAL: Faulting instruction address = 0x40
FATAL: >>> ZEPHYR FATAL ERROR 0: CPU exception
FATAL: Current thread: 0x80000058 (unknown)
FATAL: Halting system? And was the result of running (gdb): info threads like:
Id Target Id Frame
* 1 Remote target k_cpu_idle () at /zephyr/arch/arc/core/cpu_idle.S:47?
jshoen
abrodkin
I am trying to used gdb and openOCD for thread aware debugging of an ARC EMSK board configured with an EM4 CPU. I am using branch: https://github.com/zephyrproject-rtos/openocd/tree/zephyr-20190226. I built openOCD and copied to to the correct locations in the zephyr-sdk tree. I then edited the snps_em_sk_fpga.cfg file to add the '-rtos auto' option to the 'target create' line.
With these changes the openOCD tries to detect the RTOS, but errors out with a message that it cannot detect the arcv2 target: Info : Zephyr: does it have symbol 0 (mandatory)? Info : Zephyr: does it have symbol 1 (mandatory)? Info : Zephyr: does it have symbol 2 (mandatory)? Info : Zephyr: does it have symbol 3 (optional)? Info : Zephyr: all mandatory symbols found Info : Auto-detected RTOS: Zephyr Info : Zephyr: looking for target: arcv2 Error: Could not find target in Zephyr compatibility list
After that attempting to list threads shows only a single thread (the idle thread) even though multiple threads are running.
When examining the Zephyr_params_list in Zephyr.c it appears that the "cortex_m" is the only supported target.
To reproduce, add the following configuration settings to one of the sample targets such as blinky. CONFIG_DEBUG=y CONFIG_INIT_STACKS=y CONFIG_STACK_SENTINEL=y CONFIG_ARC_EXCEPTION_DEBUG=y CONFIG_LOG=y CONFIG_OPENOCD_SUPPORT=y Then build and attach gdb with 'make debug'.