Po-util: The Ultimate Local Particle Experience for Linux and macOS

Tags: #<Tag:0x00007f03908e7868> #<Tag:0x00007f03908e7700> #<Tag:0x00007f03908e73e0> #<Tag:0x00007f03908e7250> #<Tag:0x00007f03908e70c0>


Well it appears that I have NPM APM and the particle cli stuff installed and functional on the rpi3. po utils is installed so I could now do a po update…first I will run an image…but the Aruduino Ide and Teensyduino and all the other stuff I put on this box appears functional…i supose I can even tweak my own pi agent on this machine with itself.

I will count my blessings and run an image …

I even like the performance…

How to Initiate JTAG Without DFU Mode / Automating Flashing

#2017-8-20: UPDATE

Po-util now uses gcc-arm 5.3 to be compatible with newer firmware.

Update on Linux:

po update
po install

Update on macOS:

brew uninstall gcc-arm-none-eabi-49
po update
po install


You can now use po-util.com/raw to view the po-util site in a more minimal form and access some handy redirect links.


I’ve made some updates to po-util recently:

  • A lot of the code has been cleaned up
  • Flash and Ram usage for firmware is displayed when firmware is built
  • If the project you are building or the platform you are building for is different from what it was the last time you built, the firmware will automatically clean before building

Preview the new features here.

Also, for now I’ve only implemented these features for Mac, as the Linux version needs an overhaul. You can view the Trello board here: https://trello.com/b/TSB40DMC/po-util


Thank you so much!


The Linux version now has the features mentioned above.

You can get the update with:

$ po update

As always you can install with:

$ bash <(curl -sL master.po-util.com/install)

The Trello board can be viewed here: https://trello.com/b/TSB40DMC/po-util

If anyone is interested in contributing to po-util, whether it be donations, publicity, code, documentation, etc, you can contact me here on the Particle Community with a PM, Join the Gitter Room, or Make an issue.


How to use this po-util tool in Visual Studio Code? Can I use same Atom Build shortcut?



Po-util uses the build package for atom to provide the shortcuts.

I bet there is a similar way to do this in Visual Studio Code but I haven’t looked into it because I don’t use Visual Studio Code personally.

Supporting multiple IDE’s is a goal for po-util.


Have you checked out CLion? It looks really neat…


After maintaining po-util for 2 years I have announcement to make. I have released the next generation of po-util, and named it po. I’ve refactored much of the script, broke it up into modular components, and reunited the Mac and Linux versions into a single, stable project.

All future development will be on po, but I will keep the old versions of po-util around.

Feel free to check it out, star it on GitHub, or install po.


I’ve made a lot of improvements recently, notably refactoring code and adding a few more commands, like the reboot command which allows you to quickly force a reboot on a device.


$ po reboot # Reboot an automatically chosen device
$ po reboot -d /dev/ttyACM0 # Reboot a specific device

Also, the Linux DFU sticking problem has been resolved.

As always you can install po using:

$ bash <(curl -sL get.po-util.com)

You can join the Gitter room as well to get the latest info or to get po support.


I’ve added a new feature that makes it easier to choose which version of Device OS you want to use when compiling.

You can now run po versions to get the list of all Device OS versions.


$ po versions
Finding Particle Device OS versions...
Use one of these versions with 'po config'

You can then select a version with po config:

$ po config release/v0.8.0-rc.8
$ po update # only necessary if the version has been released sooner than you've updated po

You can get this new feature by updating your po installation:

$ po update


If you had to pay a price for po-util what would you be willing to pay? (I’m not planning on monetizing po-util but I’m curious about the value it has.)

And yes, I’ll be adding Mesh support ASAP.


If you’ve got a few minutes, why don’t you offhand a feature comparison chart b/t other tools and po-util? I’ve used it and I’m not even sure what all it can do!


Here are the most distinctive features:
(There are many more but they are more technical.)

  • Po-util is the only comprehensive local Particle development experience. The installer can prepare a Mac or Linux machine for Particle development in minutes.

  • Po-util has a distinct flow for building and uploading firmware. You can compile a project and flash the firmware to a Particle device with a single command.

  • Po-util supports all Particle devices, even Raspberry Pi and Redbear Duo.

  • Po-util has an Atom integration that provides shortcuts for compiling projects and uploading firmware over USB or wirelessly.

  • Po-util has a library manager that can automatically download and link libraries from Particle or GitHub directly into your project. It also has an example manager that can list and import example projects from downloaded libraries.

  • Every po-util project is initialized as a Git repository that is Travis CI ready so you can test your code compilation on Travis CI.

  • Po-util can package projects as a folder and a .zip so that your projects can be compiled with tools other than po-util or on computers that don’t have the libraries your project may depend on.

  • Po-util has commands for controlling the state of Particle devices. There are commands to put devices into and out of listening mode, dfu mode, and safe mode.

  • Po-util is actively developed and you can reach out to me with any comments or suggestions.


I’m working on adding Mesh support to po-util.

Currently I have local building working on Linux and I’ll have it on Mac soon.


I have released support for mesh firmware in po-util on macOS.

You can get it with:

po update

It is still neccessary to manually select / initialize mesh firmware on your computer before compiling for mesh devices. You can do this with:

po config v0.8.0-rc.25-mesh duo false
po update
cd ~/.po-util/src/particle/firmware
git submodule update --init

More features coming soon…


I’ve fully released Mesh support for Linux and macOS. All commands now support xenon, argon, and boron.

To select / init mesh now only the following is required:

po config v0.8.0-rc.26
po setup-mesh

The config command will now automatically switch firmware to the version you select, so po update is no longer required in this instance.


Just tried again and having some success by not using ci-install and manually running:

sudo apt-get update

sudo apt install -y expect

./po-util.sh install

P.S. Thanks for making this, it looks really useful.

Guess it’s time to start learning how to use po-util :grinning:

Can you give some argon examples. I tried the steps above but it does not seem to work. The Photon example worked great.


You should make sure you are using https://github.com/nrobinson2000/po, not the older repository.

You can install it with:

bash <(curl -sL get.po-util.com)

For photon, I recommend v0.8.0-rc.14 for the Particle branch, duo for the Redbear Duo branch and no for the headers.

Also, how are you using cloud9? I’ve used it in the past but now it appears to have been bought out by Amazon and no longer uses ubuntu. I made a new workspace, and I tried to install po but it failed.

Oh wait. The old c9.io is still up.