particle-iot/buildpack-hal

Name: buildpack-hal

Owner: Particle

Description: Buildpack for modern (HAL) Particle firmware

Created: 2015-08-21 13:43:40.0

Updated: 2017-01-21 08:03:24.0

Pushed: 2018-03-10 14:44:50.0

Homepage:

Size: 17

Language: Shell

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Buildpack for HAL firmware

Buildpack for modern (HAL based) Particle firmware.

[](https://imagelayers.io/?images=particle/buildpack-hal:latest 'Get your own badge on imagelayers.io')

| | |—| | Particle firmware | | HAL (you are here) / Legacy | | Base |

This image inherits base buildpack.

Building image

Before building this image, build or pull buildpack-base.

port BUILDPACK_IMAGE=hal
t clone "git@github.com:particle-iot/buildpack-${BUILDPACK_IMAGE}.git"
 buildpack-$BUILDPACK_IMAGE
scripts/build-and-push

Running

dir -p ~/tmp/input && mkdir -p ~/tmp/output && mkdir -p ~/tmp/cache
cker run --rm \
 ~/tmp/input:/input \
 ~/tmp/output:/output \
 ~/tmp/cache:/cache \
 FIRMWARE_REPO=https://github.com/particle-iot/firmware.git#v0.5.1 \
 PLATFORM_ID=6 \
rticle/buildpack-hal

Input files

Source files have to be placed in ~/tmp/input

Output files

After build ~/tmp/output will be propagated with:

• run.log - stdout combined with stderr
• stderr.log - contents of stderr, usefull to parse gcc errors

Files only available if compilation succeeds:

• firmware.bin - compiled firmware
• memory-use.log - firmware memory use

ARM GCC version

When building image, couple variations will be created (you can see them by typing docker images | grep particle/buildpack-hal). Most important are different ARM GCC versions you can use.