From 379a0f70cb7acc8403b57ec667f10e380b7a85e5 Mon Sep 17 00:00:00 2001 From: Yatekii Date: Fri, 17 Jul 2020 01:05:16 +0200 Subject: [PATCH] Update flashing-program.md The debug interface present on the nRF52 devices is actually SWD and not JTAG. --- embedded-workshop-book/src/flashing-program.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/embedded-workshop-book/src/flashing-program.md b/embedded-workshop-book/src/flashing-program.md index ae7b91c..0264a3f 100644 --- a/embedded-workshop-book/src/flashing-program.md +++ b/embedded-workshop-book/src/flashing-program.md @@ -14,4 +14,4 @@ The `cargo-flash` subcommand flashes and runs the program but won't display logs **🔎 How does flashing work?** -The flashing process consists of the PC communicating with a second microcontroller on the nRF52840 DK over USB (J2 port). This second microcontroller, named J-Link, is connected to the nRF52840 through a electrical interface known as JTAG. The JTAG protocol specifies procedures for reading memory, writing to memory, halting the target processor, reading the target processor registers, etc. +The flashing process consists of the PC communicating with a second microcontroller on the nRF52840 DK over USB (J2 port). This second microcontroller, named J-Link, is connected to the nRF52840 through a electrical interface known as SWD. The SWD protocol specifies procedures for reading memory, writing to memory, halting the target processor, reading the target processor registers, etc.