Build repository for Arm64 builds of specific boards

Hi,

I am referring to this document: Enable Full Graphics and Multimedia Support for NVIDIA Jetson AGX Orin Hardware — eLxr 12 Project Documentation
By any chance, does anyone here know where is the gitlab project for building ‘elxr-tegra-12.11.0.0-arm64.tar.gz’ (or whichever is the latest) and how these releases are produced? I am asking since I need to incorporate some changes and test it out on the jetson device.

All I know as of now, is that, there is a separate branch called ‘aria-orin’, ‘aria-nxp’, ‘aria-base’ and such in the elxr kernel project that allows us to build the kernel for different boards, but if I understand correctly, it does not do the full build.

Hello Deepak,

Thanks for the question. The build for the rootfs is done using rucksack. Unfortunately the documentation on rucksack today is not very complete and something to be worked on.

The best way to get started is to use the README.container. That describes how to setup your environment for building an image.

The elxr-tegra-12.11.0.0-arm64.tar.gz file is built using the rootfs.yaml description from the elxr-config project.

The eventual command that you want to be running to build the rootfs, from within your rucksack build environment, should be something like:

$ rs build --debug --config elxr-config/boards/arm64/orin/rootfs.yaml

Hopefully this will help you get started in building your rootfs.

1 Like

I did know about rucksack, but did not know that you could build orin from this as well.
Thanks for the help!

Just an extension to this question, but, is there a defined way to override installation of some default packages?
for e.g. if I have a locally built linux-image package, is there a way for me to specify it someplace and include it in this ‘rs build’ command?

For now, I have tried modifying the elxr-config/manifests/packages-orin.yaml file, elxr-config/boards/arm64/orin/rootfs.yaml, but it still looks like it is trying to find the file from mirror.elxr.dev, and ‘rs build’ command fails to find the package.

I believe there are several ways to achieve this. I would advise to look at the mmdebstrap manual page, as pasha bootstrap is a wrapper around mmdebstrap.

It believe the easiest way, if you only want to use it for local testing, might be the ‘workaround’ way of achieving this. This is done in some of the image.yaml files today, by syncing-in the .deb files from the workarounds directory and then installing it as a customize hook.

An alternative could be to setup a local mirror or package repository and specify it as a mirror, but that would probably be a bit more work to setup.

I must confess I never tried this myself, but this is the way I would try to achieve this for local debugging purposes.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.