From eddc2990de5d808eb0f8f2ad8d165fd3a9c82936 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A1szl=C3=B3=20Monda?= Date: Sun, 19 Feb 2017 16:45:52 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7fedb44..8afb0b8 100644 --- a/README.md +++ b/README.md @@ -24,9 +24,9 @@ Before flashing the firmware of the *right keyboard half*, [the bootloader](http In KDS, click on *Run -> Debug Configurations*, then you have two choices: -1. You can select *C/C++ Application -> uhk-right vX release kboot* to flash the firmware via the bootloader. +1. Select *GDB SEGGER J-Link Debugging -> uhk-right vX release jlink* to flash the firmware via a SEGGER J-Link USB debug probe. In this case, the target device (left or right keyboard half, or add-on module) must be powered, and it must be connected to the debug probe. -2. You can select *GDB SEGGER J-Link Debugging -> uhk-right vX release jlink* to flash the firmware via a SEGGER J-Link USB debug probe. In this case, the target device (left or right keyboard half, or add-on module) must be powered, and it must be connected to the debug probe. +2. Alternatively, select *C/C++ Application -> uhk-right vX release kboot* to flash the firmware via the bootloader. This method will be the default, but right now it's experimental, and not very robust. Lastly, click on the *Debug* button to flash the firmware.