From 11ae693ac284ddf1447caee342957783f4a1c4eb Mon Sep 17 00:00:00 2001 From: Benjamin Valentin Date: Sat, 24 Oct 2020 01:10:15 +0200 Subject: [PATCH] boards/microbit: fix documentation There were some random `bash` strings inside the code examples that are just confusing. Also we need to specify the board not only for emulation but for normal flashing too. --- boards/microbit/doc.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/boards/microbit/doc.txt b/boards/microbit/doc.txt index 618fc1ab1a..9c8c184068 100644 --- a/boards/microbit/doc.txt +++ b/boards/microbit/doc.txt @@ -52,9 +52,9 @@ file onto the board, and that's it. The `micro:bit` port comes with a little script that does this automatically, so you can flash the board as usual with + ``` -bash -make flash +BOARD=microbit make flash ``` The DAPLink interface provides however not means for debugging the board. @@ -67,9 +67,9 @@ the process is very simple and you can revert the firmware back to the DAPLink default anytime ([as described here](https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/)). Once you have flashed the JLink firmware, you can flash the board like this: + ``` -bash -FLASHTOOL=jlink make flash +BOARD=microbit FLASHTOOL=jlink make flash ``` With the JLink firmware, you can now also do in-circuit debugging etc.