Commit Graph

6 Commits

Author SHA1 Message Date
Marti Bolivar bf909a1fcc zephyr: port build system to CMake
Convert the Zephyr build to the new CMake-based sytem.

Signed-off-by: Marti Bolivar <marti@opensourcefoundries.com>
2017-11-20 18:10:29 -07:00
Marti Bolivar b716127b7d zephyr: update README-zephyr.rst
Add some clarifications and updates for recent development. Fix
spelling errors.

Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-04 20:36:34 -04:00
Marti Bolivar 61038df37f zephyr: move nRF5 target config into soc_family_nrf5.h
All of the information we need is in DTS or is the same across all
boards in the SoC family. There's no need for board-specific headers
for these targets.

Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-10-04 20:36:34 -04:00
Carles Cufi d783809566 zephyr: doc: Mention the DT flash description
In order to build for a particular Zephyr board, the Device Tree
definition for it in the Zephyr tree must include the flash description.

Additionally mention that a .hex version of the image is available,
useful for those flash tools that deal with Intel Hex files.

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-09-01 08:22:42 -06:00
Fabio Utzig 19356bf45f Make mcuboot less mynewt style
Remove most of mynewt specific stuff to a separate port package. This
should make mcuboot less "mynewt'y" and slightly easier to port to.

- Mynewt specific stuff moved to boot/mynewt.
- Sample app moved from apps/boot to boot/mynewt.
- Use MYNEWT_VAL macro only on mynewt port.
- BOOTUTIL_* and MYNEWT_VAL() usage moved to MCUBOOT_ defines.
2017-06-02 10:55:27 -07:00
David Brown 49aa88680e doc: Initial Zephyr build docs
Create a small document to describe how to build and use mcuboot for
Zephyr.
2017-02-06 08:10:16 -07:00