Skip to content

Commit

Permalink
Merge pull request #93 from giorez/main
Browse files Browse the repository at this point in the history
ox64 flashing sudo deletion
  • Loading branch information
x1y authored May 2, 2024
2 parents 5ba25e4 + ed2cd7b commit a98b6df
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions content/documentation/Ox64/Software/Flashing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -347,25 +347,25 @@ 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
----

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
----

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

Expand Down Expand Up @@ -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.
Expand Down

0 comments on commit a98b6df

Please sign in to comment.