I have several jetson nano motherboards. According to the seller, jetpack4.6.5 was successfully written using BSP and patch pack, and they could enter the desktop. However, these motherboards could not enter the desktop using the same SDK manager 4.6.5, and jetpack 4.6.6 could not enter the desktop. Is SDK4.6.5 jetpack and SDK4.6.6 jetpack not patched and not compatible with the DRAM indicated by PCN21181?
I have a few questions
1, in the website (Jetson Linux R32.7.5 | NVIDIA Developer) to download BSP and Additional Files with the JETPACK SDK Mangers 4.6.5 what’s the difference
2. Can Micron DRAM: MT53E512M32D1ZW-046 in PCN 211181 only use jetpack 4.6.5?
Sdkmanager is same as the thing downloaded from the website.
I would say you don’t need to focus too much on the PCN thing but just share us the serial console log first.
I used SDK to brush jetpack successfully, but I couldn’t display the desktop normally. It is OK to brush with BSP alone. I don’t know what the problem is, how do I use SDK to correctly display the desktop
It sounds more like you don’t know how to dump serial console log. You should read this post first.
If you don’t know what problem is, then just follow our instructions and I will tell you what is going on.
But from your description, I can say that your issue is definitely has nothing to do with PCN.
Thank you, tomorrow I will provide you with serial log,
This is my abnormal boot log, please help to see what is the reason
log.txt (76.1 KB)
What option did you choose in sdkmanager to flash the board?
Could you also provide a log with successful boot up case for this board?
I just used SDK to burn 4.6.5 OS, I have SDK burning log, do I need to check? I will also provide you with the log of the successfully started motherboard
SDKM_logs_JetPack_4.6.5_Linux_for_Jetson_Nano_2024-12-13_10-04-01.zip (107.8 KB)
Normal startup log.txt (41.5 KB)
I found that the phenomenon of writing only using BSP is the same as that of writing with SDK, but I can normally enter the desktop when I add this additional file, is it possible that the SDK does not contain this additional file
ok…then it is related to the PCN. You should clarify that first… I thought you are talking about you didn’t chagne anything and website BSP can work fine…
Yes, the sdkmanager and website BSP do not include this PCN. That is why it is put on the website…
As I told, sdkmanager and website BSP are equal.
Ok, so I have a few more questions:
1, when to add this additional file to SDK, because we also need to use SDK to brush into the desktop normally.
2. Does this phenomenon mean that my jetson nano can only use jetpack 4.6.5? Can’t we do the follow-up upgrade of jetpack? I don’t quite understand this
-
I am not sure what is your point to “I must use sdkmanager” when you already can use the BSP to flash the board.
-
The version that after this 4.6.5 will include this patch already. But the versions before 4.6.5 do not have this patch so if you want to use older version, you need to apply similar patch too. But we don’t provide such package for each old release either. We suggest to use latest version.
1, I have many customers, in their opinion, using the official SDK can not display normally itself is an exception, rather than the need to replace the attachment file in the SDK, SDK should be authoritative and can be used directly, why don’t you add the additional file to the SDK to facilitate the use of users? Hope you can feedback this question
2. Currently, there is no attached file for SDK and BSP jetpack4.6.6, so I cannot use jetpack4.6.6 for normal use, so I can only use the 4.6.5 version now. Do you know when the attached file will be updated so that I can use more different versions of jetpack?
What I am talking about here is jetpack4.6.6 should not have this problem so no need to apply the package.
If you still hit this problem do the same check again with logs provided.
Ok, I will provide you with the log of jetpack 4.6.6 startup failure later, thank you for your reply
There is a wrong concept for that customer part.
If you have “customer” here, it means you are providing a board to them. If you are providing boards, then it should not be NV devkit. It means a custom board.
NVIDIA sdkmanager never guarantee it would directly work with non NV devkit board. The correct way is you should provide you own custom BSP to your customer and that custom BSP could include the overlay we provided. That was why we posted in on NV webstie.
Sdkmanager won’t have silent update for PCN because we always want you to upgrade the version.
For example, I don’t expect anyone still use rel-32.1 in 2024.
Sorry that I just double checked the source code. Looks like jetpack4.6.6 does not include this patch either.
Please apply this to the BSP too.
Can I use the add-on file of jetpack 4.6.6 plus 4.6.5? If SDK 4.6.6 does not have this add-on file, when will you update SDK to solve my problem? As you said, you will keep updating SDK to adapt to the previous DRAM part
Now you have found that jetpack4.6.6 also does not have this additional file, so users who have purchased new DRAM have this problem, please timely feedback and timely solution