Hi,
我不知道用中文說明會不會比較清楚一些. 所以你並沒有完全用跟你底板一樣的使用情境複製問題過對吧?
I’m terribly sorry，I didn’t read your previous reply clearly
My test under devkit was to brush the official super conf file normally.Then I put the module and the hard drive on my own board and wrote the official super conf file, which was normal.
And then it’s the same device and I’m now brushing our own bsp, off is white, and I attach a picture.
Could you tell what change did you make in your “own BSP” in comparison with NV BSP?
Just a moment, please. I’ll make a comparison. I am comparing the 36.4 version of you now, and it seems that they have not changed anything
Thank you for your reply
I have compared the bsp of 36.3 and 36.4.3, and it is exactly the same for dts nodes without modification, but I just tested 36.3 without this situation
dts.txt (4.5 KB)
super mode compared to the above file has the following more content：
/* Copy from tegra234-p3768-0000+p3767-0000-nv-super.dts for orin nx 16g with y-c11 usb super mode*/
/dts-v1/;
//include “tegra234-p3768-0000+p3767-0000-nv.dts”
include “y-c11-orin-nx-3643.dts”
/ {
compatible = “nvidia,p3768-0000+p3767-0000-super”, “nvidia,p3767-0000”, “nvidia,tegra234”;
model = “NVIDIA Jetson Orin NX Engineering Reference Developer Kit Super”;
};
Could it have something to do with the conf file on the machine?
Super mode involves kernel dts and bpmp dtb and also nvpmodel.
I don’t see any useful information from what you just shared.
You better doing more cross check and locate what change is making this situation first otherwise we are not able to help you.
Thank you for your reply
I’ll do some more cross-checking