[meta-xilinx] [meta-xilinx-bsp][PATCH v2 3/9] meta-xilinx-standalone: Create layer, distro and machine to build standalone components

[Manjukumar Matha]

From: Alejandro Enedino Hernandez Samaniego <alejandr at xilinx.com>

This layer is meant to augment Yocto/OE functionality to provide a
toolchain to build standalone components for Xilinx architectures.

Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr at xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha at xilinx.com>
---
 meta-xilinx-standalone/README.md                   | 54 ++++++++++++++++++++++
 .../conf/distro/xilinx-standalone.conf             | 13 ++++++
 meta-xilinx-standalone/conf/layer.conf             | 14 ++++++
 .../conf/machine/zynqmp-pmu.conf                   | 11 +++++
 4 files changed, 92 insertions(+)
 create mode 100644 meta-xilinx-standalone/README.md
 create mode 100644 meta-xilinx-standalone/conf/distro/xilinx-standalone.conf
 create mode 100644 meta-xilinx-standalone/conf/layer.conf
 create mode 100644 meta-xilinx-standalone/conf/machine/zynqmp-pmu.conf

diff --git a/meta-xilinx-standalone/README.md b/meta-xilinx-standalone/README.md
new file mode 100644
index 0000000..b800f37
--- /dev/null
+++ b/meta-xilinx-standalone/README.md
@@ -0,0 +1,54 @@
+meta-xilinx-standalone
+======================
+
+This layer is meant to augment Yocto/OE functionality to provide a Baremetal/Standalone Toolchain.
+
+
+Maintainers, Mailing list, Patches
+==================================
+
+Please send any patches, pull requests, comments or questions for this layer to
+the [meta-xilinx mailing list](https://lists.yoctoproject.org/listinfo/meta-xilinx):
+
+	meta-xilinx at lists.yoctoproject.org
+
+Maintainers:
+
+	Alejandro Enedino Hernandez Samaniego <alejandr at xilinx.com>
+	Manjukumar Harthikote Matha <manjukumar.harthikote-matha at xilinx.com>
+
+Dependencies
+============
+
+This layer depends on:
+
+     URI: git://git.yoctoproject.org/poky
+
+     URI: git://git.yoctoproject.org/meta-xilinx/meta-xilinx-bsp
+
+Usage
+=====
+
+1.- Clone this layer along with the specified layers
+
+2.- $ source oe-init-build-env
+
+3.- Add this layer to BBLAYERS on conf/bblayers.conf
+
+4.- Add the following to your conf/local.conf to build for the microblaze architecture:
+
+DISTRO="xilinx-standalone"
+
+MACHINE="zynqmp-pmu"
+
+GCCVERSION="7.%"
+
+5.- Build a package:
+
+for example:
+
+$ bitbake newlib
+
+or
+
+$ bitbake meta-toolchain
diff --git a/meta-xilinx-standalone/conf/distro/xilinx-standalone.conf b/meta-xilinx-standalone/conf/distro/xilinx-standalone.conf
new file mode 100644
index 0000000..7cd23cc
--- /dev/null
+++ b/meta-xilinx-standalone/conf/distro/xilinx-standalone.conf
@@ -0,0 +1,13 @@
+DISTRO = "xilinx-standalone"
+DISTRO_NAME = "Xilinx Standalone Distro"
+DISTRO_VERSION = "1.0"
+TARGET_VENDOR = "-xilinx"
+
+TCLIBC = "newlib"
+TCLIBCAPPEND =""
+
+# Change SDK name
+SDK_VERSION = "xilinx-standalone"
+
+require conf/distro/include/yocto-uninative.inc
+INHERIT += "uninative"
diff --git a/meta-xilinx-standalone/conf/layer.conf b/meta-xilinx-standalone/conf/layer.conf
new file mode 100644
index 0000000..7d9cc59
--- /dev/null
+++ b/meta-xilinx-standalone/conf/layer.conf
@@ -0,0 +1,14 @@
+# We have a conf and classes directory, add to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have recipes-* directories, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
+	${LAYERDIR}/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "xilinx-standalone"
+BBFILE_PATTERN_xilinx-standalone = "^${LAYERDIR}/"
+BBFILE_PRIORITY_xilinx-standalone = "5"
+
+LAYERDEPENDS_xilinx-standalone = "core xilinx"
+
+LAYERSERIES_COMPAT_xilinx-standalone = "thud"
diff --git a/meta-xilinx-standalone/conf/machine/zynqmp-pmu.conf b/meta-xilinx-standalone/conf/machine/zynqmp-pmu.conf
new file mode 100644
index 0000000..2f692db
--- /dev/null
+++ b/meta-xilinx-standalone/conf/machine/zynqmp-pmu.conf
@@ -0,0 +1,11 @@
+DEFAULTTUNE ?= "microblaze"
+
+require conf/machine/include/microblaze/arch-microblaze.inc
+
+# Endianess, multiplier, barrel shift, pattern compare, floating point double or single, are the possibilities
+AVAILTUNES += "microblaze"
+TUNE_FEATURES_tune-microblaze = "microblaze v9.2 barrel-shift pattern-compare"
+PACKAGE_EXTRA_ARCHS_tune-microblaze = "${TUNE_PKGARCH}"
+SOC_FAMILY = "zynqmp"
+
+TARGET_LINK_HASH_STYLE_microblaze = ""
-- 
2.7.4