From b8e7242ffaaea1bbce935204ba6fe5587c5750a3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Hru=C5=A1ka?= Date: Sun, 7 Feb 2016 13:25:38 +0100 Subject: [PATCH] rdm --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 983dbbe..fd5cade 100644 --- a/README.md +++ b/README.md @@ -52,11 +52,9 @@ PROG_TYPE = arduino PROG_ARGS = -c $(PROG_TYPE) -p $(MCU) -b $(PROG_BAUD) -P $(PROG_DEV) ``` -Adjust `PROG_DEV` to the device your board is connected to. On Linux it's usually `/dev/ttyUSB0`, but it can also be `/dev/ttyACM0` or something else. On Mac, it'll be `/dev/cu.xxx`, on Windows it's some `COMx`. - -Linux and Mac users can just `ls /dev` to see what devices they have. Windows users can find this in their Device Manager. - -You may also adjust the baudrate (`PROG_BAUD`). Some boards need `115200`. +- Adjust `PROG_DEV` to the device your board is connected to. On Linux it's usually `/dev/ttyUSB0`, but it can also be `/dev/ttyACM0` or something else. On Mac, it'll be `/dev/cu.xxx`. On Windows it's some `COMx`. + Linux and Mac users can just `ls /dev` to see what devices they have. Windows users will find this in their Device Manager. +- You may also adjust the baudrate (`PROG_BAUD`). Some boards need `115200`. **TIP:** You can look what the Arduino IDE is using - it's running avrdude too.