Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.versionbot v2.37.0+rev1 Jun 10, 2019
balena-yocto-scripts @ 9003c4c balena-yocto-scripts: Update to v1.2.0 Jun 7, 2019
layers resin-image.inc: Install fb-unblank to keep display on Jun 7, 2019
.gitignore versionist.conf.js: Add versionist config file Aug 27, 2018
.gitmodules Rename meta-resin to meta-balena in repository Apr 24, 2019
CHANGELOG.md v2.37.0+rev1 Jun 10, 2019
LICENSE Create repo May 12, 2017
README.md Rename meta-resin to meta-balena in repository Apr 24, 2019
VERSION v2.37.0+rev1 Jun 10, 2019
blackboard-tx2.coffee blackboard-tx2.coffee: Add coffee file for blackboard-tx2 machine May 15, 2019
blackboard-tx2.svg blackboard-tx2.svg: Add icon May 17, 2019
jetson-tx2.coffee jetson-tx2.coffee: Update flashing instructions Feb 5, 2019
jetson-tx2.svg Add icon Jul 2, 2017
n510-tx2.coffee n510-tx2.coffee: Mark as community board Mar 11, 2019
n510-tx2.svg Add support for Aetina N510 TX2 Carrier Board Nov 2, 2018
orbitty-tx2.coffee orbitty-tx2.coffee: Clarify shutdown flashing instruction Jul 26, 2018
orbitty-tx2.svg orbitty-tx2.svg: Add icon for CTI Orbitty Jul 17, 2018
repo.yml Update repo.yml to be able to trigger VersionBot with `meta-balena` Apr 24, 2019
skx2.coffee skx2.coffee: Fix boot partition number Apr 9, 2018
skx2.svg skx2.conf: Fix naming bug Oct 25, 2017
spacely-tx2.coffee spacely-tx2.coffee: Add new .coffee file Jul 18, 2018
spacely-tx2.svg spacely-tx2.svg: Add icon for CTI Spacely Jul 19, 2018
srd3-tx2.coffee srd3-tx2.coffee: Add coffee file for srd3-tx2 machine May 3, 2019
srd3-tx2.svg srd3-tx2.svg: Add icon May 8, 2019

README.md

balena-jetson-tx2 repository

Clone/Initialize the repository

There are two ways of initializing this repository:

  • Clone this repository with "git clone --recursive".

or

  • Run "git clone" and then "git submodule update --init --recursive". This will bring in all the needed dependencies.

Build information

Build flags

  • Consult layers/meta-balena/README.md for info on various build flags. (setting up serial console support for example). Build flags can be set by using the build script (barys). See below for using the build script.

Build this repository

  • Run the build script: ./balena-yocto-scripts/build/barys

  • You can also run barys with the -h switch to inspect the available options

Contributing

Issues

For issues we use an aggregated github repository available here. When you create issue make sure you select the right labels.

Pull requests

To contribute send github pull requests targeting this repository.

Please refer to: Yocto Contribution Guidelines and try to use the commit log format as stated there. Example:

<component>: Short description

I'm going to explain here what my commit does in a way that history
would be useful.

Changelog-entry: User facing description of the issue
Signed-off-by: Joe Developer <joe.developer@example.com>

The header of each commit must not exceed 72 characters in length and must be in 1 line only.

The header and the subject of each commit must be separated by an empty line.

The subject of each commit must not exceed 72 characters per line and can be wrapped to several lines.

The subject and the footer of each commit must be separated by an empty line.

Every pull request must contain at least one commit annotated with the Changelog-entry footer. The messages contained in these footers will be used to automatically fill the changelog on every new version.

Also, every update to meta-balena should be separated into its own commit, if the body of that commit contains the following line Updated meta-balena from X to Y the generated changelog will include a button to show all the updates in meta-balena from the version after X to Y.

An example of a valid commit updating meta-balena is:

layers/meta-balena: Update to v2.24.0

Update meta-balena from 2.19.0 to 2.24.0

Changelog-entry: Update the meta-balena submodule from v2.19.0 to v2.24.0

Make sure you mention the issue addressed by a PR. See:

You can’t perform that action at this time.