From aafedd03a68c58010e1d6b6b7d436ceedb2a73f2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Hru=C5=A1ka?= Date: Sun, 7 Feb 2016 13:26:33 +0100 Subject: [PATCH] readme --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 3d8f942..258e273 100644 --- a/README.md +++ b/README.md @@ -52,10 +52,8 @@ 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 will find this in their Device Manager. - +- 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 use `ls /dev` to see their devices. 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.