forked from EttusResearch/meta-ettus
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
114 lines (74 loc) · 3.33 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
meta-ettus
==========
This repository contains various layers for different NI (Ettus Research) Products
Supported devices
=================
- NI USRP N310/N300 series (meta-sulfur)
- NI USRP E320 series (meta-neon)
- NI USRP E310/E312/E313 (meta-e31x)
Repository organization
=======================
The repository is split into several sublayers to allow for greater modularity.
meta-alchemy:
Contains common distro configuration
meta-ettus-core:
Contains common core recipes, such as the developer-image
meta-neon:
Contains E320 BSP. Defines machines such as ni-neon-rev1, ni-neon-rev2, etc.
meta-mender-neon:
Contains changes for E320 mender.io integration.
Defines new machines ni-neon-rev2-mender to build with mender.io integration.
meta-sulfur:
Contains N310/N300 BSP. Defines machines such as ni-sulfur-rev3, ni-sulfur-rev4, etc.
meta-mender-sulfur:
Contains changes for N310/N300 mender.io integration.
Defines new machines ni-sulfur-rev{2,3,4,5,6}-mender to build with mender.io integration.
meta-e31x:
Contains E310/E312/E313 BSP
meta-mender-e31x:
Contains changes for E310/E312/E313 mender.io integration.
Building an Image using the image builder script
================================================
This repository provides a script that can be used to build filesystem images
for the various supported USRP devices.
From the top level of this repository, run ./contrib/build_imgs_package.sh
without arguments to get the help message of this script.
To run the script, other layers than meta-ettus are required. We provide
manifest files on our oe-manifests repository:
https://github.com/EttusResearch/oe-manifests
To get a consistent set of meta-ettus and other layers, find a suitable version
of the manifest file in the oe-manifests repository, and use repo to check out
the correct versions:
repo init -u git://github.com/EttusResearch/oe-manifests.git -b $branch
where $branch is the branch or revision of oe-manifests you wish to build. For
example, to reproduce the repositories used for the 3.14.1.1 release, run the
following command:
repo init -u git://github.com/EttusResearch/oe-manifests.git -b v3.14.1.1
Then, run the script, e.g., for the N310:
./meta-ettus/contrib/build_imgs_package.sh n3xx v3.14.1.1 .
This will build and zip up the filesystem image, the SDK, and the Mender
artefact.
Building an Image using the Alchemy distro
===========================================
In you local.conf set a MACHINE from above
MACHINE ??= "ni-sulfur-rev6"
DISTRO ?= "Alchemy"
Additionally when building with mender.io support:
MACHINE ??= "ni-sulfur-rev6-mender"
INHERIT += "mender-full"
In your bblayers.conf make sure you have the required layers
(see sublayer README for individual layer dependencies)
An example for N310/N300 (sulfur) with mender.io support:
BBLAYERS ?= " \
/home/oe-builder/oe-core/meta \
/home/oe-builder/meta-oe/meta-oe \
/home/oe-builder/meta-oe/meta-python \
/home/oe-builder/meta-ettus/meta-ettus-core \
/home/oe-builder/meta-ettus/meta-alchemy \
/home/oe-builder/meta-security/meta-tpm \
/home/oe-builder/meta-oe/meta-filesystems \
/home/oe-builder/meta-oe/meta-networking \
/home/oe-builder/meta-ettus/meta-sulfur \
/home/oe-builder/meta-ettus/meta-mender-sulfur \
/home/oe-builder/meta-mender/meta-mender-core \
"