pi@raspberrypi:~ $ pio --version
-bash: pio: command not found
pi@raspberrypi:~ $ sudo pio --version
sudo: pio: command not found
pi@raspberrypi:~ $ ls -la /usr/local/bin/pio
ls: cannot access '/usr/local/bin/pio': No such file or directory
pi@raspberrypi:~ $ ls -la /usr/local/bin/platformio
ls: cannot access '/usr/local/bin/platformio': No such file or directory
pi@raspberrypi:~ $ sudo pip install -U platformio
This ran without error.
pi@raspberrypi:~ $ pio --version
PlatformIO, version 3.5.2
Cloned stm32tests from github following instructions and all went well.
Auto-detected: /media/pi/NODE_F303RE
Uploading .pioenvs/stm32f303-dev/firmware.bin
Firmware has been successfully uploaded.
(Some boards may require manual hard reset)
======================== [SUCCESS] Took 467.77 seconds ========================
================================== [SUMMARY] ==================================
Environment stm32f303-dev [SUCCESS]
Environment stm32f303 [SKIP]
======================== [SUCCESS] Took 467.77 seconds ========================
For the sake of completeness perhaps perhaps a note could be added in the various stm repositories that if using a Pi the first thing to check is to see if the Nucleo mounts and dismounts when plugged in and out.
Secondly a note also on a Pi you need to use sudo pip install -U platformio to install platformio.
Thatās good news, that means that (Pi) users installing by either method (Python+curl or pip) can just reissue the installation command with sudo if they omit it the first time.
Are you now able to use startx without any problems returning?
At this point Iāve still got no idea what has caused the issue and to my knowledge you are the only one to have experienced it (thus far), so Iām not really able to give a concise check, cure or even guidance on how to avoid it happening yet, The guide will get real messy if we include all the checks and explanations etc, it might not be clear to a user that it isnāt mounted, or it might actually be mounted to the root owned folder created by startx.
Here, however, I think we have established enough of a clear pattern for a warning, something like
Raspberry Pi (Raspbian) users should always use sudo to install platformio and generally never use sudo when using any platformio or pio commands, ever!