My TX2 can't started system. after updata jetpack4.2 on myself PCB carrier plate.

I didn’t find tegra186-quill-p3310-1000-a00-00-base.dts in public_sources\hardware\nvidia\platform\t18x\common\kernel-dts\t18x-common-platforms

Is it OK to add this node to this file?

	nvdisplay@15200000 {
		status = "disabled";
	};

nvdisplay@15100000 {
status = “disabled”;
};

	nvdisplay@15220000 {
		status = "disabled";
	};

When I run make O=$TEGRA_KERNEL_OUT tegra18_defconfig
Tips error:

user@Host:~/HDMI/public_sources/kernel_src/kernel/kernel-4.9$ export TEGRA_KERNEL_OUT=/home/user/dtb/
user@Host:~/HDMI/public_sources/kernel_src/kernel/kernel-4.9$ export ARCH=arm64
user@Host:~/HDMI/public_sources/kernel_src/kernel/kernel-4.9$ make O=$TEGRA_KERNEL_OUT tegra18_defconfig
make[1]: Entering directory ‘/home/user/dtb’
HOSTCC scripts/basic/fixdep
GEN ./Makefile
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf


*** Can’t find default configuration “arch/arm64/configs/tegra18_defconfig”!


/home/user/HDMI/public_sources/kernel_src/kernel/kernel-4.9/scripts/kconfig/Makefile:113: recipe for target ‘tegra18_defconfig’ failed
make[2]: *** [tegra18_defconfig] Error 1
/home/user/HDMI/public_sources/kernel_src/kernel/kernel-4.9/Makefile:565: recipe for target ‘tegra18_defconfig’ failed
make[1]: *** [tegra18_defconfig] Error 2
make[1]: Leaving directory ‘/home/user/dtb’
Makefile:171: recipe for target ‘sub-make’ failed
make: *** [sub-make] Error 2
user@Host:~/HDMI/public_sources/kernel_src/kernel/kernel-4.9$

Hello
I tried to change the device tree in the following way
Tegra186-quill-p3310-1000-a00-00-base.dts added
Nvdisplay@15210000{
Status = disabled;
}

And recompile
But the problem remains unsolved.
UART log is attached
Hope to continue to give me some help.
log2.txt (63 KB)

What did you add exactly?

You have typo and wrong upper/lower case in your comment. I cannot tell whether you are writing the correct thing to device tree.

You could use “dtc” tool to reverse the compiled dtb to dts and check if you are setting it correctly.

I’m sorry

I added.

nvdisplay@15210000{
   status = disabled;
}

in “tegra186-quill-p3310-1000-a00-00-base.dts”

11.PNG

11.PNG

Got it. Could you make sure your final dtb flashed into device also has this setting?

  1. Confirm which dtb file is flashed to device through flash log

  2. use dtc tool with below usage
    dtc -I dtb -O dts -o <input dtb name based on the answer from question 1>

check the content inside test.dts or attach on forum to us.

I used it.

dtc-i dtb-o dts-o < reverse compiled DTS name e.g. test.dts > < input DTB name based on the answer from question 1 >

Tools on TX2 of my JetPack 4.2 get disassembled documents.

test.dts.txt (444 KB)

Looks like it has been disabled. May I ask how you replace the dtb and flash the board?

1.I used the following method but it didn’t work.
Copy the new /dtb file to nvidia_sdk/JetPack_4.2_Linux_p3310/Linux_for_Tegra/kernel/
and
Use command ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1 at host PC

.
2.Then I copied the dtb file directly to /boot/dts/ in

I’m not sure that’s the right way to do it, but neither of them will solve the problem in the end.

358271128,

Step 1 is enough. Step 2 is not necessary.

Which dtb file are you flashing? Could you share the name?

The following files are in my dtb/

tegra186-quill-p3310-1000-a00-00-base.dtb
tegra186-quill-p3310-1000-as-0888.dtb
tegra186-quill-p3310-1000-c03-00-base.dtb
tegra186-quill-p3310-1000-c03-00-dsi-hdmi-dp.dtb
tegra186-quill-p3489-0888-a00-00-base.dtb
tegra186-quill-p3489-1000-a00-00-ucm1.dtb
tegra186-quill-p3489-1000-a00-00-ucm2.dtb
tegra194-p2888-0001-p2822-0000.dtb
tegra194-p2888-0001-p2822-0000-maxn.dtb

No, I mean the one you flash to the device…

You could check it from jetson-tx2.conf.

Is this?

BPFDTB_FILE=tegra186-a02-bpmp-quill-p3310-1000-a00-00-te770d-ucm2.dtb;

source “${LDK_DIR}/p2771-0000.conf.common”;

No, it should be the one with “DTB_FILE”. Please make sure this dtb is the same one you shared with me in previous comment.

Dear:
I don’t understand what this means. In the attachment is my jetcon-tx2.conf. Please tell me how to do it.
Thinks.
tegra186-quill-p3310-1000-c03-00-base.dtb.txt (336 KB)

For example,
This line in p2771-0000.conf.common is included in jetson-tx2.conf
DTB_FILE=tegra186-quill-p3310-1000-a00-00-base.dtb;

It means the fine you flashed into your device is tegra186-quill-p3310-1000-a00-00-base.dtb. You have to make sure nvdisplay is set to disabled in this file.

I cannot make sure if your dtb file is same as mine because I am using old release.

Dear:
I’ve dealt with the problem that I can’t boot up. With your help, the only problem is that the monitor can’t be connected. Hope to have a more perfect solution.
Thank you very much!!!:-)

Dear WayneWWW,

If we don’t judge booting by using HDMI,what is another option for us to judge it is booting correctly.If you have idea please provide us.Our custom carrier board is not booting(iam not seeing NVIDIA logo on screen using HDMI).

Thanks in advance.

For devkit usecase, there are some debug methods

  1. HDMI monitor
  2. UART debugger
  3. Remote access (ssh)

Remote access can be used by ethernet/wifi or usb-eth virtual interface.

The last option is added after rel-28.2.1. You could ping the device with ip 192.168.55.1 once you connect a micro usb cable to the port on devkit. Your host side would also have similar interface and you could see it through ifconfig.

What you can use depends on your custom carrier board. For me, UART debugger is the most stable way which can see the bootloader log while HDMI and remote access can only dump kernel log.

The nvidia boot logo is in cboot which is also bootloader. If you want to debug that part, you must use UART debugger.