FWIW the Orin NX integrations should all be very similar, just the carrier device trees would be a bit different. I also have a Seeed Orin NX board around, IIRC the J401. Unfortunately I’m usually lacking the time for the Orins to push more forwards.
Have you actually tried the board and are facing issues, or are you just evaluating options? If you could provide a bit more detail then I’m sure we can help, also maybe @Austriker or @aduskett (who has lately been touching Orins )
we’re actually deploying these boards on boats currently. But, currently, it’s a bit bloated with Ubuntu (as it’s shipped that way).
Originally, the main motivation was around making it more robust/stable towards random power loss. That brought me down the rabbit hole of OverlayFS, live OS setups, tmpfs-backed logging, and remounting / read-only..
Now I’m realizing that without proper A/B partitioning or OTA infrastructure, it’ll probably hit a wall at some point, especially if we want to update in the field and still be confident things boot back up cleanly after a hard shutdown. Currently, updates only affect the application layer.
What would you recommend as next steps in that case?
Generally speaking, I would try to build the existing demo configuration in meta-mender-community, specifically https://github.com/TheYoctoJester/meta-mender-community/blob/scarthgap/kas/tegra/jetpack6/jetson-orin-16gb-nx-p3786.yml for basing on Jetpack 6. To get started, I would leave out application specific requirements such as Nvidia runtime or similar for now, just make sure the device boots and can do A/B updates. After that, I would evaluate different strategies for updating, like “full OS plus application, every time”, or “OS as base rarely, application often”, and include considerations like data persistency respectively containerization.
If you’d like to bounce ideas off somebody, let me know