From 1451f47cfcdee4cf6384b9fda09003ec333451d1 Mon Sep 17 00:00:00 2001 From: giorez Date: Wed, 1 May 2024 21:26:43 +0200 Subject: [PATCH 1/2] ox64 flashing sudo deletion --- content/documentation/Ox64/Software/Flashing.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/documentation/Ox64/Software/Flashing.adoc b/content/documentation/Ox64/Software/Flashing.adoc index 93732b5d..b8d42bed 100644 --- a/content/documentation/Ox64/Software/Flashing.adoc +++ b/content/documentation/Ox64/Software/Flashing.adoc @@ -347,7 +347,7 @@ Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_i [source,console] ---- -$ sudo bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ +$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ > --addr 0x0 --firmware bl808-combined.bin --single ---- @@ -355,13 +355,13 @@ Otherwise, run the following commands: [source,console] ---- -$ sudo bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ +$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ > --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single -$ sudo bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ +$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ > --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single -$ sudo bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ +$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD \ > --addr 0x800000 --firmware bl808-firmware.bin --single ---- @@ -450,14 +450,14 @@ Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial con [source,console] ---- -$ sudo minicom -b 2000000 -D /dev/ttyACM0 +$ minicom -b 2000000 -D /dev/ttyACM0 ---- If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing): [source,console] ---- -$ sudo minicom -b 2000000 -D /dev/ttyACM1 +$ minicom -b 2000000 -D /dev/ttyACM1 ---- Re-apply power to the Ox64. From ed2cd7befc7f80cff5c0c0fc6db3eec1d74f7857 Mon Sep 17 00:00:00 2001 From: giorez Date: Thu, 2 May 2024 13:00:57 +0200 Subject: [PATCH 2/2] ox64 find group allowed to serial ports --- content/documentation/Ox64/Software/Flashing.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/documentation/Ox64/Software/Flashing.adoc b/content/documentation/Ox64/Software/Flashing.adoc index b8d42bed..38509aef 100644 --- a/content/documentation/Ox64/Software/Flashing.adoc +++ b/content/documentation/Ox64/Software/Flashing.adoc @@ -365,7 +365,7 @@ $ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD > --addr 0x800000 --firmware bl808-firmware.bin --single ---- -If you get permission errors when running any of the commands above, you may need to add your user to the communication group (`dialout` for Debian or `uucp` for Arch Linux), using `sudo usermod -a -G [communication_gruop] $USER` and re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment. +If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment. === BLDevCube flashing method