Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Research
smarter
distribution
Commits
8ee7d4a1
Commit
8ee7d4a1
authored
Jun 25, 2021
by
Eric Van Hensbergen
Browse files
Update w/SMARTER README.md
parent
ac54698b
Changes
1
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
8ee7d4a1
#
tegra-demo
-distro
#
smarter
-distro
Reference/demo distribution for NVIDIA Jetson platforms
using Yocto Project tools and the meta-tegra BSP layer.

Metadata layers are brought in as git submodules:
| Layer Repo | Branch | Description |
| --------------------- | --------|---------------------------------------------------- |
| poky | master | OE-Core from poky repo at yoctoproject.org |
| meta-tegra | master | L4T BSP layer - L4T R32.5.1/JetPack 4.5.1 |
| meta-openembedded | master | OpenEmbedded layers |
| meta-virtualization | master | Virtualization layer for docker support |
| meta-mender | dunfell | For meta-mender-core layer used in tegrademo-mender |
| meta-mender-community | dunfell | For meta-mender-tegra integration layer |
Reference/demo distribution for SMARTER platforms
Based on meta-tegra
[
tegra-demo-distro
](
https://github.com/OE4T/tegra-demo-distro
)
For more information on SMARTER look
[
here
](
https://getsmarter.io
)
## Prerequisites
...
...
@@ -31,18 +19,14 @@ kits), the `bmap-tools` package is recommended.
1.
Clone this repository:
$ git clone -b hardknott https://github.com/OE4T/tegra-demo-distro.git
2.
Switch to the appropriate branch, using the
[
wiki page
](
https://github.com/OE4T/tegra-demo-distro/wiki/Which-branch-should-I-use%3F
)
for guidance.
$ git clone -b dunfell-l4t-r32.4.3 https://gitlab.com/arm-research/smarter/smarter-distro.git
3
.
Initialize the git submodules:
2
.
Initialize the git submodules:
$ cd
tegra-demo
-distro
$ cd
smarter
-distro
$ git submodule update --init
4
.
Source the
`setup-env`
script to create a build directory,
3
.
Source the
`setup-env`
script to create a build directory,
specifying the MACHINE you want to configure as the default
for your builds. For example, to set up a build directory
called
`build`
that is set up for the Jetson Xavier NX
...
...
@@ -55,7 +39,7 @@ kits), the `bmap-tools` package is recommended.
$ . ./setup-env --help
5
.
Optional: Install pre-commit hook for commit autosigning using
4
.
Optional: Install pre-commit hook for commit autosigning using
$ ./scripts-setup/setup-git-hooks
## Distributions
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment