I was working in my Jetson Orin Nano Dev Kit. earlier i was having an Issue with jtop as it was not detecting my jetpack version. with the help of the community i have resolved that issue and upgraded my L4T VERSION R36.4.4. but recently i found my orin has undergone a nvidia-l4t-bootloader installation and i got a notification window of the same(screenshot attached). after a reboot my l4t version was seen as 36.2.1 instead 36.4.4 and again jtop shows jetpackmissing. this time i didnt updated jetson_variables but i found that my firmware version is r36.4.4 during a reboot(screenshot attached).
same time i checked ‘jetson-release -v’ it shows l4t 36.2.1. due to this i am unable to operate my project sdk properly as it shows l4t version mismatch. I kindly request the community’s help on this.
This looks like a jetson-stats issue. It needs to be updated for L4T 36.4.4
elsaco@jetson:~$ jtop
[WARN] jetson-stats not supported for [L4T 36.4.4]
Please, try: sudo pip3 install -U jetson-stats or
open a Github issue (press CTRL + Click)
Jetpack Missing and Jetson-stats issue , i have resolved. But my main concern was the mismatch of the L4T version in jtop as well as in nvbootctrl. is it an issue with the jtop? I have checked in jetson_variables.py but i couldnt find the version 36.2.1 in that. but i was curious from where that version value was reflected in jtop.
I’m not sure how did your upgrade the devkit to r36.4.4 before.
Have you tried simply using SDK manager to flash Jetpack 6.2.1(L4T r36.4.4) to the devkit and check if there’s the similar issue?
The version read from nvbootctrl indicates the bootloader version. It seems Jetpack 6.2.1(L4T r36.4.4) in your case.
Earlier my system had an auto upgrade into JP6.2.1 but jtop was not detecting this due to some update in jetson-stats, which I have cleared manually with the help of community.
Later, I have turned off every auto update but at some day I saw a post installation notification window which was about l4t bootloader and was asking for a reboot of the device (SS Attached). I did the reboot and the jtop was showing my l4t version as 36.2.1, but in ‘nvbootctrl’ l4t was showing as 36.4.4. due to this mismatch i was unable to install some packages and jtop.service was also not restarting. I knew that the get through was to reflash the Orin using SDK manager, but I was looking for some other ways that doing a reflash since it will take considerable time for backup, reflash and setting up the required environment. the main concern was ‘why there was a different version of the l4t?’ and how to resolve it? is the only way was to reflash the orin with sdk manager into the required version of JP and l4t?
There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0910
Is this still an issue to support? Any result can be shared?
