Google Git
Sign in
apache / mynewt-blinky / 6326c96f2f08f8b9cd01d8628281955b23a37a58
commit6326c96f2f08f8b9cd01d8628281955b23a37a58[log] [tgz]
authorSzymon Janc <szymon.janc@codecoup.pl>Mon Nov 25 10:58:07 2024 +0100
committerSzymon Janc <szymon.janc@codecoup.pl>Mon Nov 25 11:51:24 2024 +0100
tree39de46ea55d57169992b6125a0558733b629c563
parentc04a9376af74249ee9f861bd10a4da257b378bf5 [diff]
Use master branch for core repository

This will be changed upon release, but newt from master downloads
blinky master and thus all project should be from master branches
1 file changed
tree: 39de46ea55d57169992b6125a0558733b629c563
  1. apps/
  2. targets/
  3. .asf.yaml
  4. .gitignore
  5. .rat-excludes
  6. LICENSE
  7. NOTICE
  8. project.yml
  9. README.md
README.md

Apache Blinky

Overview

Apache Blinky is a skeleton for new Apache Mynewt projects. The user downloads this skeleton by issuing the “newt new” command (using Apache Newt). Apache blinky also contains an example app and target for use with Apache Mynewt to help you get started.

Building

Apache Blinky contains an example Apache Mynewt application called blinky. When executed on suitably equipped hardware, this application repeatedly blinks an LED. The below procedure describes how to build this application for the Apache Mynewt simulator.

  1. Download and install Apache Newt.

You will need to download the Apache Newt tool, as documented in the Getting Started Guide.

  1. Download the Apache Mynewt Core package (executed from the blinky directory).
    $ newt install
  1. Build the blinky app for the sim platform using the “my_blinky_sim” target (executed from the blinky directory).
    $ newt build my_blinky_sim

The Apache Newt tool should indicate the location of the generated blinky executable. Since the simulator does not have an LED to blink, this version of blinky is not terribly exciting - a printed message indicating the current LED state. To learn how to build blinky for actual hardware, please see the Getting Started Guide.