Nvidia Jetson Xavier AGX devkit L4T35.5

We have a fleet of NVIDIA Jetson Xavier AGX devices that we would like to manage with Balena cloud. However L4T 35.5 is a requirement.

Given the fact that Yocto project exists and is working for L4T 35.5 (see here: GitHub - OE4T/meta-tegra at scarthgap-l4t-r35.x) can you build a balena image using this layer?

Hello @y1thu first of all, welcome to the balena community!

We are currently working on bringing the L4T 36.x on balenaOS, Is that ok for your project or you might need specifically L4T 35.5?

Dear @mpous ,

that would of course also work for me as long as it works for NVIDIA Jetson Xavier AGX. To my knowledge the last supported release for this hardware is 35.5.: https://developer.nvidia.com/embedded/jetson-linux-archive. 36 is only supported by Orin, …

Or am I mistaken?

Hello @y1thu as you mentioned before the current production image only support L4T 32.7.4, so we don’t suppport the L4T 35.5.0 for Xavier AGX.

Could you please tell us more about your project to evaluate the support for Xavier AGX for newer versions on balena?

Thanks!

Hi @y1thu , are you using AGX Xavier Devkits for your fleet or other types of carrier boards? If it’s not Devkits, are they fully compatible with the AGX Xavier Devkit or do they need changes in the board configuration files, like custom pinmux settings?

1 Like

@acostach to my understanding they are 100% compatible with AGX Xavier Devkit (however the supplier is AAEON). In all my yocto compiles I treated as as devkit and it nearly all worked.
This works for me (but A/B boot is a bit strange): scarthgap-l4t-r35.x kas build errors by tjhgit · Pull Request #403 · mendersoftware/meta-mender-community · GitHub
And this as well (including A/B boot): GitHub - OE4T/meta-tegra-community at scarthgap-l4t-r35.x

Can you integrate balena layer into one of these please?

In all my yocto compiles I treated as as devkit and it nearly all worked.

Just to confirm, is there something that didn’t work but you need that to be working @y1thu ? Like specific USB or LAN ports, WiFi, peripherals, specific GPIOs, or anything else. Or all these work fine?

@acostach yes ALL worked for me. I am currently not using the GPIO, so cannot tell.

1 Like