Skip to content
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

Update Jetson Xavier AGX, NX SD-CARD and NX eMMC to L4T 35.4.1 #163

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

acostach
Copy link
Collaborator

No description provided.

@@ -177,12 +173,13 @@ module.exports = class ResinJetsonFlash {
},
['jetson-xavier-nx-devkit']: {
url:
'https://developer.nvidia.com/downloads/remksjetpack-463r32releasev73t186jetsonlinur3273aarch64tbz2',
'http://127.0.0.1/Jetson_Linux_R35.4.1_aarch64.tbz2',
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@acostach is this file supposed to be downloaded automatically?

I found it at https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/jetson_linux_r35.4.1_aarch64.tbz2, is the right step to modify build.sh to add this path?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cbecker that should be https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/jetson_linux_r35.4.1_aarch64.tbz2 , or as it is if you want to serve the archive locally using a http server.

Copy link

@cbecker cbecker Jul 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok thanks.

To make it work with the docker image I had to change it in a few places, becuase build.sh writes the file with another name, see this line:

RUN wget "$bsp_url" -O "/tmp/L4T_BSP_$device_type.tbz2"  && echo "BSP archive for $device_type saved in /tmp/L4T_BSP_$device_type.tbz2, can be downloaded from http://127.0.0.1/L4T_BSP_$device_type.tbz2"

so it'll never be able to fetch that file, because it'd have to be named L4T_BSP_xxx instead, or am I missing something?

@dadaroce
Copy link

Hello there,

In order to flash directly without using the takeover tool, which image should I use? The roofs generated by: balena-os/balena-jetson-orin#424?

How could I bind that image to my account? I just noticed the classic balena os configuration ... doesn't work on this kind of image

@acostach
Copy link
Collaborator Author

@dadaroce yes, the balenaOS image generated by balena-os/balena-jetson-orin#424

In L4T 35.X the partition layout has changed for all devices, and the cli is only taking into consideration the production images and their partition layout. You can use sudo losetup -fP balena-image....rootfs.balenaos-img , then mount the loop device which corresponds to the resin-boot partition and replace the config.json fine with one downloaded from balena-cloud. Then, unmount the mount-point used for resin-boot and detach the loop device (losetup -d /dev/loopX). Finally, flash the image to the device

@dadaroce
Copy link

@acostach where exactly should be the config.json I can't find the file to replace it or is it missing directly? in that case, where should I place it?

@dadaroce
Copy link

dadaroce commented Aug 15, 2024

Nevermind, I use the disk application to mount it
/dev/loop35p43

Change-type: patch
Signed-off-by: Alexandru Costache <alexandru@balena.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants