Hi, kevinFFF
we use xavier nx development kit. 64GB SD nx-log.txt (492.5 KB)
Attached is the dtb updated via sudo dd if=/boot/kernel_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt of=/dev/mmcblk0p4
What did you change in the device tree? Normal usecase of NX won’t have 2 sdhci controller enabled at same time.
[ 5.448046] mmc0: SDHCI controller on 3440000.sdhci [3440000.sdhci] using ADMA 64-bit with 64 bit addr
[ 5.468017] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit with 64 bit addr
Hi, kevinFFF
I didn’t change the dtb and Image.
I used the same dtb and Image,kernel_supplements.tbz2 in xavier NX emmc+p3450,This problem did not appear.
Sorry, not quite sure what you wanted to say here. Please describe what is the difference between the NG case and the working case. Are you saying that only module has difference?
For example, you told us you modified dtb in comment #1. Now you say you didn’t change the dtb. Which one is true?
Hi,kevinFFF
I mean I didn’t modify the device tree and kernel,Then compile to generate dtb and Image.
When using compile-generated dtb updates xavier nx devkit ,The system fails to start.
When I use another set of equipment xavier nx emmc+p3450, Update dtb,This problem did not appear.
The system uses jetpack4.6
I have used sdkmanager,flash.sh, sd-card-image flash the system
Two methods of updating dtb have been used
cp kernel_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt to /boot/, then
sudo dd if=/boot/kernel_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt of=/dev/mmcblk0p4
sudo ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p1
No matter what method is used, After updating the dtb, the system fails to start.
Sorry that could you try to tell more about your comment? Is flashing with sdkmanager able to boot up or not?
Your comment only tells us how you flashed, but you didn’t tell us the result…
Hi,
sorry,
After the system fails to start, The system can be restarted only flash “jetson-nx-jp46-sd-card-image” . Using the other two flash methods(sdkmanager,flash.sh), the system will not boot.
[ 5.448046] mmc0: SDHCI controller on 3440000.sdhci [3440000.sdhci] using ADMA 64-bit with 64 bit addr
麻煩再確認一下你手邊的dtb檔案是否真的是你預期的檔案…
–Eng version
Are you sure your dtb flashed by sdkmanager is not something that is already changed by you…?
According to your log, I saw 3440000.sdhci device node. This is sdmmc3 controller. And none of the official dtb released by us ever enables it. Thus, I believe this error is still caused by your change in dtb… I don’t think what you said is true that you didn’t change anything in device tree.
Please check if the device tree is really as your expectation.
Hi,kevinFFF
It’s really the device tree problem.
This problem occurs when “sdhci@3440000” is enabled.
What I know , When using the nx emmc module on a custom carrier board, The carrier board contains an sd card slot. Need to enable sdhci. Even without the sd card slot on carrier board and nx emmc module, enabling sdhci will not cause the system to fail to boot.
Why does this problem occur when enabling sdhci on nx development kit?
[ 5.448046] mmc0: SDHCI controller on 3440000.sdhci [3440000.sdhci] using ADMA 64-bit with 64 bit addr
[ 5.468017] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit with 64 bit addr
-End ver-
Please put the order of your sdhci@3440000 node behind the sdhci@3400000.
Current situation is mmc0 is now owned by sdhci@3440000, which is the extra sdcard slot added by you. However, it should be owned by sdhci@3400000, which is the slot on module…
[ 5.448046] mmc0: SDHCI controller on 3440000.sdhci [3440000.sdhci] using ADMA 64-bit with 64 bit addr
[ 5.468017] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit with 64 bit addr
Currently, the module’s sdcard slot becomes mmcblk1p1… so changing the order may help.