Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ox64 flashing added Archlinux commands #90

Closed
wants to merge 7 commits into from
Closed

ox64 flashing added Archlinux commands #90

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
05f6de2
ox64 - flashing added Archlinux commands
giorez Apr 29, 2024
84927d8
as per https://github.com/pine64/website/pull/90#discussion_r1583338668
giorez Apr 29, 2024
f222e85
ox64 flashig on archlinux fixed
giorez Apr 30, 2024
9fe197b
Update Flashing.adoc
giorez Apr 30, 2024
0d77750
Update Flashing.adoc
giorez Apr 30, 2024
26dc4c5
Update Flashing.adoc
giorez Apr 30, 2024
61f6f91
Update Flashing.adoc
giorez Apr 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 30 additions & 2 deletions content/documentation/Ox64/Software/Flashing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,7 +261,7 @@ You have a choice of flashing software:

=== CLI packages installation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would strongly recommend to keep this one instruction for all distributions, not for random selected distributions. Steps are to install Pipenv, the library and then to change into the pipenv shell. If the packages are named differently then it can be mentioned as "Install packages x (under Debian it is called "x-x", under Arch it is called "xx") and y (under Debian it is called "y-y", under Arch it is called "yy").

Some basic knowledge can be generally imputed.


Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:
Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows for Debian-based systems:

[source,console]
----
Expand All @@ -271,6 +271,17 @@ $ . ~/ox64_venv/bin/activate
$ pip install bflb-iot-tool # we are *not* using bflb-mcu-tool
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would change it to pipenv in those blocks too.

----

In case you're on Archlinux systems, slightly adapt the commands:
x1y marked this conversation as resolved.
Show resolved Hide resolved

[source,console]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mind the "$" in front of the console commands in this block.

----
$ sudo pacman -S python
$ python -m venv ~/ox64_venv
$ . ~/ox64_venv/bin/activate
$ pip install setuptools
x1y marked this conversation as resolved.
Show resolved Hide resolved
$ pip install bflb-iot-tool # we are *not* using bflb-mcu-tool
----

NOTE: Each time you open a new terminal window you will need to re-run `. ~/ox64_venv/bin/activate` to reactivate the virtual environment.

=== DevCube installation
Expand Down Expand Up @@ -361,7 +372,6 @@ $ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:


[cols="~,~"]
|===
|Interface
Expand Down Expand Up @@ -394,6 +404,24 @@ Then, switch to the [IOT] tab:
* Click 'Create & Download' again and wait until it's done
* Close DevCube

== Erasing the microSD card

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

[source,console]
----
$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1
----

Optionally you can zeroes the whole device:

[source,console]
----
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)
----

== Flashing the microSD card

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:
Expand Down
Loading