-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
L4T 34.1 requested for Xavier boards #317
Comments
[acostach] This issue has attached support thread https://jel.ly.fish/c7bc2524-bfc1-440c-a04f-f3748092109b |
[mpous] This has attached https://jel.ly.fish/c7bc2524-bfc1-440c-a04f-f3748092109b |
[rosswesleyporter] This has attached https://jel.ly.fish/641d2ef1-652a-428f-b895-f116effd12e7 |
L4T 34.1.1 is a developer preview release which has some known limitations, like for instance no A/B rootfs support and should not be used in production environments. There will not be a production image available in the dashboard for this L4T version as L4T 35.x releases will be destined for production. cc @rosswesleyporter |
@acostach nice progress! Where can I find the |
@SIGLOST You can find the latest Jetpack on Nvidias Website: https://developer.nvidia.com/embedded/jetpack-sdk-501dp - if I understand @acostach correctly, there will be no balenaOS release of 5.x until the first major / non-preview version of 5.x is available to the public. |
@SIGLOST @nmaas87 that's correct, there will be no 34.1.1 image release for the AGX Orin because it's a developer preview, and rootfs A/B is not implemented in the BSP. We'll have to see how that works in the final release and how we can use it for balenaOS. As for the rest of the Xavier boards that are currently supported on 32.7.1/32.7.2 I cannot give a L4T 35.x estimate because Nvidia switched from using cboot to a uefi launcher and I believe the partition layout was changed as well. This has an impact which will have to be evaluated on our side, but we can only have a look at that after we finish the Orin evaluation on the upcoming production L4T release. |
Perfect, thanks so much for clarification @acostach - yeah I thought I read a lot changed along the sides of the other Ubuntu version and more stuff which makes it incompatible for a lot of entry Jetson boards. So thanks a lot for keeping up with the state of things! :) |
Dear @acostach , I see that the AGX Orin was released 2 weeks ago with r35.x support. Does that mean that the Xavier update is imminent? Greetings |
[acostach] This has attached https://jel.ly.fish/9ed7c9cf-3c15-4677-b38c-8b7b1e0e82a3 |
Hello @acostach |
[alanb128] This has attached https://jel.ly.fish/a0339aea-2566-432c-b753-7f2e9390a9ba |
Yes, the r35x is on our roadmap @SIGLOST but I don't have a timeline. Would you like to experiment with local yocto build until we finish the work on this? |
@acostach Hello! We would be interested in experimenting with the local yocto build as we are currently maintaining two separate fleets for our Jetsons: (1) Orins on r35 and (2) Xaviers (AGX and NX) on r32 and we would like to investigate merging these two fleets to single Jetson fleet. |
Hi @volks73, a few questions to better understand the context:
|
Hello @acostach,
Yes, we have three (3) Jetson AGX Xavier dev kits and three (3) Jetson Xavier NX dev kits running L4T 32.7.x. These are spread between two fleets in balenaCloud.
We do not plan to provision any new Jetson AGX Xaviers or Jetson Xavier NX devices as we are focusing on the Jetson Orin line of devices.
In addition to our dev kits for the AGX and NX within the Jetson Xavier product line, we have 24 Jetson Xavier NX SoMs in a separate fleet across six Jetson Mate carrier boards with three to four SoMs per carrier board. Some of the Jetson Mates originally came with Jetson Nanos, but we have removed the Nano SoMs because they were under-powered for our application. All Jetson Xavier NX SoMs are the "eMMC" device type and running L4T 32.7.x across two fleets in balenaCloud. |
No description provided.
The text was updated successfully, but these errors were encountered: