You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kumar Gala 5fb8825036 add ci based on 1 year ago
.github/workflows add ci based on 1 year ago
cmake cmake: Introduce CMake package for Zephyr SDK 1 year ago
configs configs: Enable no-python GDB 1 year ago
meta-zephyr-sdk QEMU: Add support of ARCv2 processors 1 year ago
overlays xtensa: add config nxp_imx8m_adsp 1 year ago
patches crosstool-ng: add support for building a no-python gdb version 1 year ago
scripts template_dir: improved help text for toolchain install dir 1 year ago
.gitignore gitignore: Add Emacs style backup file pattern 2 years ago
.shippable.yml shippable: Update env to have python3.8 1 year ago
LICENSE license: add LICENSE file 3 years ago xtensa: add config nxp_imx8m_adsp 1 year ago
VERSION bump version for 0.11.3-beta-1 1 year ago cmake: Introduce CMake package for Zephyr SDK 1 year ago release-notes: Add new Intel and NXP xtensa ADSP tools. 1 year ago

Zephyr SDK with Crosstool NG

This project is to replace the current Yocto based SDK with a new framework for
building the Zephyr SDK using crosstool-ng.

The repoistory consists of configurations for the various architectures (not
fully tests) and a script that builds on Linux (x86_64) and Mac in a consistent
way, apply patches where needed.

Currently we build the following toolchains:

  • i586
  • nios2
  • arm
  • arm64
  • riscv64
  • sparc
  • xtensa (sample_controller, intel_apl_adsp, intel_s1000, intel_bdw_adsp,
    intel_byt_adsp, nxp_imx_adsp, nxp_imx8m_adsp)

To build for any of the above, run:

./ <arch>

Released Binaries packages

Pre-built binaries releases of the SDK are made and currently only available for
an x86_64 Linux host environment. The releases can be found here:

PR Builds

Successfull PR builds will get posted here:

Release Process

To release a new SDK:

  • Update the VERSION file with the new version, for example 0.11.0 or
    0.11.0-beta1 etc.
  • On, create the release
    tag and add the release information.
  • One the release is created, CI will build the SDK image and will upload it to
    the release page.