A Solution to BSP Version Mismatch in SDKManager setup

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

I encountered a BSP version mismatch error in SDKManager similar with topic :
https://forums.developer.nvidia.com/t/bsp-version-mismatch-in-sdkmanager-setup/227921/8

https://forums.developer.nvidia.com/t/jetson-sdk-component-bsp-version-failure-when-installing-jetpack-5-0-2-rev1/228743

During my flash process(Xavier NX, jetpack 4.6.5, deepstream 6.0.1) when installing multimedia API, SDKMnanger kept popup “BSP version mismatch” and fail, after a careful digging, I found multimedia API requires BSP>32.7, but no matter how many times I tries, I got BSP 32.5 in my device, that is why it says “BSP version mismatch”.

But in theory, everything is provided by SDKManager, there won’t be such a low-level mistake, until I noticed that the SDKManager indeed downloaded BSP 32.7.5.

So I finally found out that the SDKManager won’t erase the device before flashing Jetson OS, so the BSP 32.5 of the old OS in the device keeps stays in the device.
So the solution is: format the target drive of your Jetson device manually before flashing, e.g. EMMC or NVME, this fixes all the errors for me and made a perfect flash result.

2

I guess it is more like boot device mistake.
Not erase problem.

The device you boot with is not the device you tried to flash. It is common mistake.

4

Wrong guess, only working with single boot device also have same error, and formatting indeed fixed it.

5

I don’t want to waste your time.
But is what you are telling here still reproducible on your side?

There is no one ever reported this and rel-32 has been there many years.

Need to do some further check.

6

For example, how did you format your emmc manually by not using sdkmanager?

7

If I have time I will check.

And If this is useful to you, the very original system version of this device is a bit old, maybe released around 2021

1 Like
8

using mkfs on the jetson device, mkfs.ext4 /dev/mmcblk0p1

1 Like