@@ -147,29 +147,30 @@ The Segger J-Link tools are the default for this board, therefore it is not
147147necessary to set ``OPENSDA_FW=jlink `` explicitly when you invoke ``make
148148debug ``.
149149
150+ With these mechanisms, applications for the ``mimxrt1050_evk `` board
151+ configuration can be built and debugged in the usual way (see
152+ :ref: `build_an_application ` and :ref: `application_run ` for more details).
153+
150154The pyOCD tools do not yet support this SoC.
151155
152156Flashing
153157========
154158
155159The Segger J-Link firmware does not support command line flashing, therefore
156- the `` make flash `` build target is not supported.
160+ the usual `` flash `` build system target is not supported.
157161
158162Debugging
159163=========
160164
161165This example uses the :ref: `hello_world ` sample with the
162- :ref: `nxp_opensda_jlink ` tools. Use the ``make debug `` build target to build
163- your Zephyr application, invoke the J-Link GDB server, attach a GDB client, and
164- program your Zephyr application to flash. The following commands will do all
165- that, and leave you at a gdb prompt.
166-
167- .. code-block :: console
168-
169- $ cd <zephyr_root_path>
170- $ . zephyr-env.sh
171- $ cd samples/hello_world/
172- $ make BOARD=mimxrt1050_evk debug
166+ :ref: `nxp_opensda_jlink ` tools. Run the following to build your Zephyr
167+ application, invoke the J-Link GDB server, attach a GDB client, and program
168+ your Zephyr application to flash. It will leave you at a GDB prompt.
169+
170+ .. zephyr-app-commands ::
171+ :zephyr-app: samples/hello_world
172+ :board: mimxrt1050_evk
173+ :goals: debug
173174
174175
175176.. _MIMXRT1050-EVK Website :
0 commit comments