Jon Carstens
Jon Carstens
This changes the `mix burn` (and subsequently `mix firmware.burn`) to use the FWUP `upgrade` task by default. If the upgrade fails because the device does not actually have upgradable firmware...
By default `mix burn` (and subsequently `mix firmware.burn`) will completely overwrite the SD card because it defaults to using the `complete` task, losing all data on it However, it may...
Running fwup writes while another fwup process is writing the same drive could be detrimental. Adding a lock file that can be used to infer another fwup process is running...
In very specific cases, it might be desirable to fallback to another task when the target task fails. Most commonly this will be falling back to the `complete` task when...
**Is your feature request related to a problem? Please describe.** Since OTP >=24.3, `certificate_authorities` extension is configurable for the client and defaults to `false`. However, in a peer-to-peer setup (i.e....
CPIO is letting us down. So, let's optimize and start handling it on own on. This is beginning steps of an idea to create our own file tree with native...
Circle CI supports [multiple executor types](https://circleci.com/docs/2.0/executor-intro/#section=configuration) including MacOS and Windows, so we should try to run the tests in multiple different executors to cover more compatibility checks: - [x] Alpine...
Currently compiles for MacOS Working on Nerves targets
For https://github.com/nerves-project/nerves/issues/576 This allows us to use the build path for the specific target/env when compiling the firmware. Requires https://github.com/nerves-project/nerves_system_br/pull/674
This is a general discussion based on work in #576. Specifically, to solve that issue we needed to get details from the top level firmware project being used and pass...