STM32 PlatformIO

[pb66 (Paul)]

@ian

pi@raspberrypi:~ $ sudo pip install -U platformio

This ran without error.

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?

@ian

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.

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.

@ian

Secondly a note also on a Pi you need to use sudo pip install -U platformio to install platformio.

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!