Talk:Ox64

Flash memory producer

Hello. On this page I see datasheets for Gigadevice flash memory, but on my boards placed Winbond flash. Maybe we need to update datasheets?--ElektroNIK (talk) 11:58, 20 January 2023 (UTC)

I disagree with the name of section 10

[Placeholder for the initial message by User:Pavlos1]

Hello! Did you mean that the "Flashing Ox64 SBC and SD Card for Newbies" section title should be reworded? I'd agree about that, and I'd suggest that the "for Newbies" part is simply dropped. -- Dsimic (talk) 17:00, 4 January 2024 (UTC)

Went ahead and implemented this edit. -- Dsimic (talk) 17:55, 4 January 2024 (UTC)

Regarding PIP and --break-system-packages

To User:Giorez and other editors:

The instructions in the Open-Source Flashing Using CLI section involve installing a PIP package. Doing so is a bit awkward due to conflicts with system packages. I used to do it as follows, but for whatever reason that doesn't work anymore (at least on Gentoo and Arch).

pip install --user $PACKAGE

In the article itself I suggested creating a virtual environment as follows. That seems to be the "preferred" way of managing a separate set of Python packages to the ones installed by the OS package manager.

python -m venv ~/ox64_venv
. ~/ox64_venv/bin/activate
pip install $PACKAGE

Note that when you run pip install with the virtual environment activated, it installs the package to the virtual environment. So you need to re-activate the virtual environment each time you open a new terminal window; otherwise bflb-iot-tool will not be in your PATH.

The following is not recommended since it is instructing PIP to potentially introduce conflicts with system packages. And to be clear: running the command below is *not* necessary if you have already set up the virtual environment as described above.

sudo pip install $PACKAGE --break-system-packages

-- Pavlos1 (talk) 03:22, 6 January 2024 (UTC)

I agree with the way you described it above. -- Dsimic (talk) 17:13, 6 January 2024 (UTC)