OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/common/openocd-nrf5.board.cmake

34 lines
1.1 KiB
CMake
Raw Normal View History

boards: arm: add generic openocd-via-jlink support for nRF5x boards This support is Zephyr RTOS aware, so you can debug threads as well. Add a CMake fragment which adds openocd support for nrf5 boards which can also be flashed via JLink. This ought to work for nRF51 and nRF52 based boards at time of writing with openocd 0.10.0 or later (zephyr SDK 0.10.3 also worked when I tried for nrf52840_pca10056). Use it from the nRF DKs from Nordic which have interface MCUs with Segger compatible firmware. I'm also including Thingy:52, even though it doesn't, to make it easier when connecting to it via a standalone JLink dongle. The board has a nice connector for that. I'm leaving non-Nordic boards alone for now because I don't know them. It's just one line of CMake to add it for other boards, which should be easy for their maintainers to do. Suggested-by: Radosław Koppel <radoslaw.koppel@nordicsemi.no> Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-01 23:08:28 +08:00
# SPDX-License-Identifier: Apache-2.0
# Infer nrf51 vs nrf52 etc from the BOARD name. This enforces a board
# naming convention: "nrf5x" must appear somewhere in the board name
# for this to work.
#
# Boards which don't meet this convention can set this variable before
# including this script.
if (NOT DEFINED OPENOCD_NRF5_SUBFAMILY)
string(REGEX MATCH nrf5. OPENOCD_NRF5_SUBFAMILY "${BOARD}")
endif()
if("${OPENOCD_NRF5_SUBFAMILY}" STREQUAL "")
message(FATAL_ERROR
"Can't match nrf5 subfamily from BOARD name. "
"To fix, set CMake variable OPENOCD_NRF5_SUBFAMILY.")
endif()
# We can do the right thing for supported subfamilies using a generic
# script, at least for openocd 0.10.0 and the openocd shipped with
# Zephyr SDK 0.10.3.
set(pre_init_cmds
"set WORKAREASIZE 0x4000" # 16 kB RAM used for flashing
"source [find interface/jlink.cfg]"
"transport select swd"
"source [find target/${OPENOCD_NRF5_SUBFAMILY}.cfg]"
"$_TARGETNAME configure -rtos auto"
)
foreach(cmd ${pre_init_cmds})
west: prepend -c to openocd commands commit 0df4a53107817b080d694ca8a18810d91d498799 changed the behavior of how openocd commands are passed to openocd. We used to add -c to each command, now the commands are being added without -c causing an error. This adds "-c" to all commands instead of just passing a list. Also fixes #20449. Signed-off-by: Anas Nashif <anas.nashif@intel.com> Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-12 22:07:33 +08:00
board_runner_args(openocd --cmd-pre-init "${cmd}")
boards: arm: add generic openocd-via-jlink support for nRF5x boards This support is Zephyr RTOS aware, so you can debug threads as well. Add a CMake fragment which adds openocd support for nrf5 boards which can also be flashed via JLink. This ought to work for nRF51 and nRF52 based boards at time of writing with openocd 0.10.0 or later (zephyr SDK 0.10.3 also worked when I tried for nrf52840_pca10056). Use it from the nRF DKs from Nordic which have interface MCUs with Segger compatible firmware. I'm also including Thingy:52, even though it doesn't, to make it easier when connecting to it via a standalone JLink dongle. The board has a nice connector for that. I'm leaving non-Nordic boards alone for now because I don't know them. It's just one line of CMake to add it for other boards, which should be easy for their maintainers to do. Suggested-by: Radosław Koppel <radoslaw.koppel@nordicsemi.no> Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2019-11-01 23:08:28 +08:00
endforeach()
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)