Yes, that is what I did and it works.
I was also using the flash script that is in your manual, it might need some adjustment.
Do you have the flash.sh config too just flash the kernel and device tree. I cannot get that one to work successfully and have to use sdkmanager to re-install every thing when it breaks and will not boot.
Jetson System firmware version 36.2.0-gcid-34956989 date 2023-11-30T18:35:35+00:
It is still R36.2.0 which is not the expected version to me.
Please get an Ubuntu host PC and use SDK manager to flash JP6.1(R36.4.0) for the devkit.
Or you can refer to the steps in Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation to setup and flash the board with command.
Congrat.!
It seems another request, please open another topic to discuss in details.
Hi,
I wanted to post in this thread to make sure it does not close itself. I have been trying to flash the board with the suggested method as well as with SDK manager since it seems like there is no pre-packed SD bundle to burn with etcher; but I am encoutering some errors. I will post once I manage to boot up the system by flashigh it from a host PC with either method.
A couple things I did find, wipe your install media before trying to flash.
I had to do this when using the stand alone scripts, not sdkmanager
sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Change to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
sudo update-grub
sudo reboot
Thanks, I will try again with this in mind. Despite following all the steps and manually fixing some problems while flashing, I have not been able to flash 6.1 even with SDK manager at the moment. I have seen you were able to change the pinmux with jetsion-io.py by flashing 5.1.4.
I will update any relevant findings. Its amazing to me how difficult its been to do something as simple as changing the GPIO mux …
Jorge
This is really odd, my dev workstation is the same model box as our yocto build machine. sdkmanager breaks on my dev workstation. So it must be something software specific to my machine.
My guess is the env variables. It runs perferctly on my yocto build machine(dedicated for one application) that is very clean. Had to setup a 20.04 ubuntu box to build r35.x / jp5/x and the sdkmanager is the first and only application on the box and it works perfect. It might need a source and setup script prior to launch, don’t know this for fact but it is possible.
Hello,
After some fighting with my host machine, I was able to flash the latest version using SDKmanager to an SD card.
jon@ubuntu:~$ uname -a
Linux ubuntu 5.15.148-tegra #1 SMP PREEMPT Thu Dec 12 15:37:09 PST 2024 aarch64 aarch64 aarch64 GNU/Linux
jon@ubuntu:~$ dpkg-query --show nvidia-l4t-core
nvidia-l4t-core 36.4.2-20241212160716
But now, jetsion-io.py closes itself inmediately after opening, what setup did you use for this?
Thanks,
Jorge
I guess for the moment I will wait for the next release
In case someone else ends up in this thread, I am marking it as solved but it’s not exactly solved. The version that I was flashig by using the SD image (see posts avobe) appears to be broken, as of now, there are no 6.X pre-packed SD card versions that worked for me with jetson-io.py, hence why I say it is not resolved. I was able to activate the I2S pin interface (at least, make it appear as activated after applying changes in jetson-io.py) by flashing R36.4.0 with the l4t_initrd_flash.sh tool (note that R36.4.2, the latest version flashed by SDK manager as of now does not work) .
I will make a separated post if further issues arise, but apparently is getting fixed for 6.1 in the next release with support for super mode.
Jorge
I’m running into this issue using JetPack 6.1 (rev1). The ‘jetson-io.py’ script exits immediately when run.
After instrumenting jetson-io.py I discovered that the /boot/*.dtbo do not match the expected compatibility string required by the dtb file.
The script is looking for anything that matches one of these substrings:
[nvidia,p3768-0000+p3767-0005-super nvidia,p3767-0005 nvidia,tegra234].
But for example the adafruit-uda1334a.dtbo file reports being compatible with one of these:
[nvidia,p3737-0000+p3701-0000 nvidia,p3737-0000+p3701-0004 nvidia,p3737-0000+p3701-0005 nvidia,p3737-0000+p3701-0008].
Seems like the nvidia-l4t-kernel-dtbs_5.15.148-tegra-36.4.0-20240912212859_arm64.deb contains the wrong dtbo files
It is a known issue that we’ve noticed and fixed in the next release.
Please wait for the next Jetpack release to get it resolved for super mode.