boards: nxp: mimxrt1160_evk: set LinkServer as the default runner

Sets LinkServer as the default runner for mimxrt1160-evk boards,
as the board is configured for CMSIS-DAP by default.

Signed-off-by: Andrej Butok <[email protected]>

Author: butok

boards/nxp/mimxrt1160_evk/board.cmake

@@ -14,6 +14,6 @@ board_runner_args(pyocd "--target=mimxrt1160_cm4")
 board_runner_args(jlink "--device=MIMXRT1166xxx6_M4")
 endif()
 
-include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
 include(${ZEPHYR_BASE}/boards/common/linkserver.board.cmake)
+include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
 include(${ZEPHYR_BASE}/boards/common/pyocd.board.cmake)

boards/nxp/mimxrt1160_evk/doc/index.rst

@@ -209,15 +209,6 @@ The secondary core can be debugged normally in single core builds
 secondary core should be placed into a loop, then a debugger can be attached
 (see `AN13264`_, section 4.2.3 for more information)
 
-Configuring a Debug Probe
-=========================
-
-A debug probe is used for both flashing and debugging the board. This board is
-configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,
-however the :ref:`pyocd-debug-host-tools` do not yet support programming the
-external flashes on this board so you must reconfigure the board for one of the
-following debug probes instead.
-
 Launching Images Targeting M4 Core
 ==================================
 If building targeting the M4 core, the M7 core must first run code to launch
@@ -237,26 +228,34 @@ so:
 If desired, this behavior can be disabled by building with
 ``-DSB_CONFIG_SECOND_CORE_MCUX_LAUNCHER=n``
 
+Configuring a Debug Probe
+=========================
+
+A debug probe is used for both flashing and debugging the board. The on-board
+debugger :ref:`opensda-daplink-onboard-debug-probe`
+works with the LinkServer runner, or can be reprogrammed with JLink firmware.
+
+Using LinkServer
+----------------
+
+Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
+search path. LinkServer works with the default CMSIS-DAP firmware included in
+the on-board debugger.
+
 Using J-Link
 ------------
 
-Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
-path.
+Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.
 
-There are two options: the onboard debug circuit can be updated with Segger
-J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
+The on-board debug circuit can be updated with Segger J-Link firmware,
+or :ref:`jlink-external-debug-probe` can be attached to the
 EVK. See `Using J-Link with MIMXRT1160-EVK or MIMXRT1170-EVK`_ for more details.
 
-Using LinkServer
-----------------
+Use the ``-r jlink`` option with West to use the jlink runner.
 
-Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
-search path.  LinkServer works with the CMSIS-DAP firmware include in LinkServer
-install. Please follow the ``LPCScrypt\docs\Debug_Probe_Firmware_Programming.pdf``
-for more details.
+.. code-block:: console
 
-Linkserver is the default runner. You may also se the ``-r linkserver`` option
-with West to use the LinkServer runner.
+   west flash -r jlink
 
 Configuring a Console
 =====================