HDMI Display does not work after update to JetPack 5.0.2

請問在用Pilips、Voc冠捷 這兩款螢幕的時候 不插拔hdmi而是直接跑xrandr. 這種狀況下xrandr給你的解析度是正確的嗎? 如果xrandr有給你正確的解析度, 這時用xrandr切去別種解析度會讓桌面出現嗎?

還有, 請問你剛才貼的log是哪個螢幕的測試?

When you are using Pilips、Voc monitors, if you don’t hotplug hdmi but only run xrandr, will xrandr give you correct resolution in such situation?
If so, could you switch the mode with xrandr? Would this make desktop show?

Also, which monitor was in use w.r.t. the log you just posted?

刚才贴的log用的是 Pilips 屏幕。

用Pilips、Voc冠捷 這兩款螢幕的時候,不插拔hdmi而是直接跑xrandr,resolution是正确的,如下
orin@nvidia-agx-orin:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080 60.00*+ 74.97 59.94 50.00
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x720 60.00 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94 59.93

那請問這個測試結果是…?

如果xrandr有給你正確的解析度, 這時用xrandr切去別種解析度會讓桌面出現嗎?

How about the test result of this?

If so, could you switch the mode with xrandr? Would this make desktop show?

Pilips屏:xrandr切换mode后(如下),仍然没有显示;
调试屏:xrandr切换mode后,可正常切换显示;

orin@nvidia-agx-orin:~$ xrandr --output HDMI-0 --mode 1920x1080
orin@nvidia-agx-orin:~$ xrandr --output HDMI-0 --mode 1024x768
orin@nvidia-agx-orin:~$ xrandr --output HDMI-0 --mode 1280x720
orin@nvidia-agx-orin:~$ xrandr --output HDMI-0 --mode 800x600

Hi,

麻煩先照這個步驟上patch, 做full flash. 這是有其他用戶已經驗證過的檔案.
另外, 麻煩對照一下flash log確認你燒進去的pinmux跟dtb真的是你改的那一份
因為市面上有多款Orin module. dtb跟pinmux檔案有可能不是你預期要改的那份

  1. apply the [orin-hdmi-support-pinmux.patch]
  2. use the new hdmi dcb file '[tegra234-dcb-p3701-0000-a02-p3737-0000-a01-hdmi-4-ga5.0.2.dtsi]
  3. apply the kernel hdmi hotplug patch [0001-orin-hdmi-hotplug-support-kernel-dts.patch]
  4. rebuilt the kernel dtb and “reflash the image” //Note : make sure ‘reflash’ the image, no substitute dtb in exlinux!!
    0001-orin-hdmi-hotplug-support-kernel-dts (4).patch (1.3 KB)
    orin-hdmi-support-pinmux (3).patch (1.1 KB)
    tegra234-dcb-p3701-0000-a02-p3737-0000-a01-hdmi-4-ga5.0.2.dtsi (26.8 KB)

Please follow above instructions to apply patch to your pinmux and device tree first. Also, make sure the one that got flashed are really the files you flash to the board. There are multiple kinds of orin module in the market so it has multiple dtb and pinmux files too.

按照上述步骤并 full flash之后,Pilips屏启动后仍然没有显示;调试屏启动后可以显示,插拔后不再显示。
Pilips屏、调试屏插拔HDMI都会弹出如下WARNING

[ 287.426836] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0
[ 287.436386] —[ end trace 1348f3ef37846e22 ]—
[ 351.903007] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0
[ 351.913145] —[ end trace 1348f3ef37846e23 ]—
[ 352.573247] WARNING: CPU: 0 PID: 328 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0
[ 352.583072] —[ end trace 1348f3ef37846e24 ]—
[ 352.773179] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0
[ 352.782824] —[ end trace 1348f3ef37846e25 ]—
[ 439.417670] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0
[ 439.427814] —[ end trace 1348f3ef37846e26 ]—
[ 439.432692] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1a0/0x1e0

通过flash log确认烧录的是打patch的自定义pinmux文件
cat flash.log | grep pinmux

copying pinmux_config(/home/pyq/local/nvidia/orin/sdk/5.0.2/target_hw_image/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/Orin-ys-acu-pinmux.dtsi)... done.
./tegraflash.py  --bl uefi_jetson_with_dtb.bin  --odmdata gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0  --overlay_dtb L4TConfiguration.dtbo,tegra234-p3737-overlay-pcie.dtbo,tegra234-p3737-audio-codec-rt5658-40pin.dtbo,tegra234-p3737-a03-overlay.dtbo,tegra234-p3737-a04-overlay.dtbo,L4TRootfsInfo.dtbo,tegra234-p3737-camera-dual-imx274-overlay.dtbo,tegra234-p3737-camera-e3331-overlay.dtbo,tegra234-p3737-camera-e3333-overlay.dtbo,tegra234-p3737-camera-imx185-overlay.dtbo,tegra234-p3737-camera-imx390-overlay.dtbo  --bldtb tegra234-p3701-0000-p3737-0000.dtb --applet mb1_t234_prod.bin --cmd "flash; reboot"  --cfg flash.xml --chip 0x23 --concat_cpubl_bldtb --cpubl uefi_jetson.bin --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --pinmux_config Orin-ys-acu-pinmux.dtsi --gpioint_config tegra234-mb1-bct-gpioint-p3701-0000.dts --pmic_config tegra234-mb1-bct-pmic-p3701-0000.dts --pmc_config Orin-ys-acu-padvoltage-default.dtsi --deviceprod_config tegra234-mb1-bct-cprod-p3701-0000.dts --prod_config tegra234-mb1-bct-prod-p3701-0000.dts --scr_config tegra234-mb2-bct-scr-p3701-0000.dts --wb0sdram_config tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram.dts --br_cmd_config tegra234-mb1-bct-reset-p3701-0000.dts --dev_params tegra234-br-bct-p3701-0000.dts,tegra234-br-bct_b-p3701-0000.dts --mb2bct_cfg tegra234-mb2-bct-misc-p3701-0000.dts  --bins "psc_fw pscfw_t234_prod.bin; mts_mce mce_flash_o10_cr_prod.bin; mb2_applet applet_t234.bin; mb2_bootloader mb2_t234.bin; xusb_fw xusb_t234_prod.bin; dce_fw display-t234-dce.bin; nvdec nvdec_t234_prod.fw; bpmp_fw bpmp_t234-TE990M-A1_prod.bin; bpmp_fw_dtb tegra234-bpmp-3701-0000-3737-0000.dtb; sce_fw camera-rtcpu-sce.img; rce_fw camera-rtcpu-t234-rce.img; ape_fw adsp-fw.bin; spe_fw spe_t234.bin; tos tos-optee_t234.img; eks eks.img"  --sdram_config tegra234-p3701-0000-p3737-0000-TE990M-sdram.dts  --cust_info custinfo_out.bin  --secondary_gpt_backup  --bct_backup  --boot_chain A 
[   2.0305 ] Pre-processing config: Orin-ys-acu-pinmux.dtsi
[   2.4454 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --wb0sdram tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram_cpp.dtb --pinmux Orin-ys-acu-pinmux_cpp.dtb --pmc Orin-ys-acu-padvoltage-default_cpp.dtb --pmic tegra234-mb1-bct-pmic-p3701-0000_cpp.dtb --brcommand tegra234-mb1-bct-reset-p3701-0000_cpp.dtb --prod tegra234-mb1-bct-prod-p3701-0000_cpp.dtb --gpioint tegra234-mb1-bct-gpioint-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb --deviceprod tegra234-mb1-bct-cprod-p3701-0000_cpp.dtb
[   2.4470 ] Parsing config file :Orin-ys-acu-pinmux_cpp.dtb 
[   2.4590 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --wb0sdram tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram_cpp.dtb --pinmux Orin-ys-acu-pinmux_cpp.dtb --pmc Orin-ys-acu-padvoltage-default_cpp.dtb --pmic tegra234-mb1-bct-pmic-p3701-0000_cpp.dtb --brcommand tegra234-mb1-bct-reset-p3701-0000_cpp.dtb --prod tegra234-mb1-bct-prod-p3701-0000_cpp.dtb --gpioint tegra234-mb1-bct-gpioint-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb --deviceprod tegra234-mb1-bct-cprod-p3701-0000_cpp.dtb
[   2.4608 ] Parsing config file :Orin-ys-acu-pinmux_cpp.dtb

device-tree新增了os_gpio_hotplug_a

orin@nvidia-agx-orin:~$ ll /proc/device-tree/display@13800000/os_gpio_hotplug_a
-r–r–r-- 1 root root 12 Sep 20 11:35 ‘/proc/device-tree/display@13800000/os_gpio_hotplug_a’

TEGRA234_MAIN_GPIO(M, 0) 无 os_gpio_hotplug_a 字样
cat /sys/kernel/debug/gpio|grep PM
gpio-424 (PM.00 )
gpio-425 (PM.01 )
gpio-426 (PM.02 )
gpio-427 (PM.03 )
gpio-428 (PM.04 )
gpio-429 (PM.05 |camera-control-outpu) out lo
gpio-430 (PM.06 )
gpio-431 (PM.07 )

Hi,

  1. 請問你的"调试屏" 跟其他種類的螢幕有何不同?

  2. 請問有除了這三款螢幕之外的螢幕可以做測試嗎?

  3. warning不需要在意. 那只是代表hotplug gpio有收到interrupt.


  1. What is difference between your “test monitor” from the other kind of monitors?

  2. Do you have a 4th monitor which is not Philips/VOC or your test monitor?

  3. No need to worry about the warning log. They just indicate your hotplug gpio is working.

  1. 调试屏参数如下,网上买的这个屏幕只是因为尺寸较小,方便携带调试,没有其他特别要求。

  2. 测试了一款lenovo屏幕(支持hdmi转DVI,不支持hdmi直接输入,ps 之前测试的3款都是hdmi直接输入),没任何显示,xrandr也不显示。这是因为 jp5.0.2 不支持 hdmi转 dvi吗?
    另外,测试了与之前Pilips同款的另外1pcs屏幕,启动后不显示,通过xrandr仍然不显示,调换之前Pilips屏幕用的hdmi线,启动后和xrandr仍然都不显示。

  3. 调试屏(或Pilips屏通过run xrandr方式显示后),在 apply HPD patch之前,插拔后可显示;apply HPD patch 之后,插拔后不再显示。是否是该 HPD patch 不适用?
    HPD patch指如下patch:

另外,以下是custom carrier board HDMI 接线线序,色彩不对是否与 TX0 TX1 TX2线序有关。如果是的话,是否可以在orin端通过配置dtb调整线序。
orin side → hdmi Type A
HDMI_DP2_TX0_N → D2N
HDMI_DP2_TX0_P → D2P
HDMI_DP2_TX1_N → D1N
HDMI_DP2_TX1_P → D1P
HDMI_DP2_TX2_N → D0N
HDMI_DP2_TX2_P → D0P
HDMI_DP2_TX3_N → CLKN
HDMI_DP2_TX3_P → CLKP
图片

Hi,

  1. 請問你的硬體目前能改動嗎? 如果你的接線已經跟我們的hw design guide文件有不同, 我會建議先照文件做
    Data lane 接反的話也有機會讓螢幕畫面出不來. 以前我們在Xavier的平台上看過不少這種問題.

  2. 關於這點

调试屏(或Pilips屏通过run xrandr方式显示后),在 apply HPD patch之前,插拔后可显示;apply HPD patch 之后,插拔后不再显示。是否是该 HPD patch 不适用?

可以請你比較一下是dcb還是pinmux相關的patch被替換之後造成的影響嗎? 我的意思是一個一個patch做置換 看看是哪個patch造成你的调试屏 hpd有問題.


  1. Are you able to change the hardware design? If your connection is different from our design guide, then it has chance monitor fails to show. We had some similar case on Xavier platofrm before.

  2. About this one.

调试屏(或Pilips屏通过run xrandr方式显示后),在 apply HPD patch之前,插拔后可显示;apply HPD patch 之后,插拔后不再显示。是否是该 HPD patch 不适用?

Could you compare which patch is causing the HPD issue one by one?

  1. 我们已有一批custom carrier boards,这批硬件无法改动。我们希望可以通过软件配置解决 Data lane 接反的问题;

  2. 确认是如下 pinmux patch导致的。

diff --git a/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi b/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
index df735b4..66c62d9 100644
--- a/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
+++ b/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
@@ -362,7 +362,7 @@
 
 			dp_aux_ch0_hpd_pm0 {
 				nvidia,pins = "dp_aux_ch0_hpd_pm0";
-				nvidia,function = "dp";
+				nvidia,function = "rsvd1";
 				nvidia,pull = <TEGRA_PIN_PULL_NONE>;
 				nvidia,tristate = <TEGRA_PIN_ENABLE>;
 				nvidia,enable-input = <TEGRA_PIN_ENABLE>;
diff --git a/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi b/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
index 8afec26..307cfba 100644
--- a/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
+++ b/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
@@ -39,6 +39,7 @@
 				TEGRA234_MAIN_GPIO(Q, 6)
 				TEGRA234_MAIN_GPIO(Q, 7)
 				TEGRA234_MAIN_GPIO(R, 1)
+				TEGRA234_MAIN_GPIO(M, 0)
 				TEGRA234_MAIN_GPIO(N, 4)
 				TEGRA234_MAIN_GPIO(N, 1)
 				TEGRA234_MAIN_GPIO(G, 0)


diff --git a/hardware/nvidia/platform/t23x/concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts b/hardware/nvidia/platform/t23x/concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts
index 0a4d2bbd0..0dd9c1d8e 100644
--- a/hardware/nvidia/platform/t23x/concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts
+++ b/hardware/nvidia/platform/t23x/concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts
@@ -60,6 +60,7 @@
 
 	display@13800000 {
 		status = "okay";
+		os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) GPIO_ACTIVE_HIGH>;
 	};
 
 	dce@d800000 {
-- 
2.17.1

Hi,

  1. 關於那個lane接反的問題, 需要內部確認一下

  2. 請問是三個檔案一同才會造成問題 還是只要其中一個檔案更改就有問題?
    tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
    tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
    concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts


  1. Regarding to that lane reversal problem, need to do some internal chekc.

  2. Does it fail to work with all 3 patches applied or even one of them would cause failure?

已确认是Data lane 接反导致的一系列奇怪现象。
在custom carrier board上飞线调整Data lane后,可正常显示,热插拔也正常(with HPD patch)。

期待您这边的答复,谢谢!

1 Like

Got it. Will reply to you later.

Hi @nkpyq

抱歉詢問一個無關目前狀況的問題. 所以你最後加上我們給的patch之後熱插拔是能正常使用的嗎? 還是說要用你原本的版本?

Sorry for asking a irrelevant question. Does the hotplug function work fine after you applied the patch we shared? Or you are still using the old version?

reflash确认以下两种方式都能正常使用,热插拔也都能正常使用。

  1. 原来的版本,即hdmi patch from R34.1
    https://docs.nvidia.com/jetson/archives/r34.1/DeveloperGuide/text/SD/Kernel/DisplayConfigurationAndBringUp.html

  2. HPD pacth版本

1 Like

Hi @nkpyq

抱歉, 發現一件事. 你們目前燒錄進去的dtb看起來是tegra234-p3701-0000-p3737-0000.dts.
但是我們給的pinmux patch 應該是a04那個檔案的dtsi ->tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi

如果要匹配, 應該會是 tegra234-mb1-bct-pinmux-p3701-0000.dtsi.

可以請你確認一下你的flash log (燒錄時host打印的log) 裡面的pinmux file是用哪份嗎? 因為如果你改的是a04那份 但燒的是0000那個, 其實patch就沒有加到了


Sorry that I notice one thing here. The dtb you flashed to the board is tegra234-p3701-0000-p3737-0000.dts.
But the pinmux patch we shared to you is tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi. The correct one that matches to your kernel dtb should be tegra234-mb1-bct-pinmux-p3701-0000.dtsi.

Could you check your flash log and confirm which one is getting flashed to the board? And confirm if that one is really patched?

我没有使用 tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi 和 tegra234-mb1-bct-pinmux-p3701-0000.dtsi,用的是《Orin_Jetson_Series_Pinmux_Config_Template.xlsm》自定义生成的pinmux,见如下配置和相应的flash log。
所以HPD patch相关pinux和gpio部分,我是手动添加patch里面的变更内容到自定义pinmux和gpio。

PINMUX_CONFIG=“Orin-ys-acu-pinmux.dtsi”;
PMC_CONFIG=“Orin-ys-acu-padvoltage-default.dtsi”;

1 Like

Hi @WayneWWW
我测试了第2块Orin核心板模组的时候,发现不需要任何hdmi 相关patch,hdmi也可以正常显示和热插拔。第1块Orin Dev Kit和第2块Orin核心板模组 flash log相关Chip 信息如下

    第1块:
            Chip sku: 0xd0
            Board ID(3701) version(500) sku(0000) revision(H.0)
    第2块:
            Chip sku: 0xd2
            Board ID(3701) version(500) sku(0004) revision(G.0)

以下是测试步骤:
step1. full flash,kernel为 0000版。

$ cat /proc/device-tree/compatible
nvidia,p3737-0000+p3701-0000nvidia,tegra234nvidia,tegra23x

step2. 删除 /boot/extlinux/extlinux.conf 中的 FDT /boot/dtb/kernel_tegra234-p3701-0000-p3737-0000.dtb后,reboot,kernel为 0004版。hdmi可正常显示,支持热插拔。
kernel 0004 版dtb,没有apply任何 hdmi相关patch,是jp5.0.2 release纯净版本,有通过 hexdump /proc/device-tree/display@13800000/nvidia,dcb-image 确认。

$ cat /proc/device-tree/compatible
nvidia,p3737-0000+p3701-0004nvidia,tegra234nvidia,tegra23x

另外一个疑问是,烧录到第2块核心板模组分区的是 0004版kernel(dtb),extlinux.conf使用的却是 0000版kernel,这个是否是bug,该核心板应该使用哪个版本kernel?谢谢!
我发现0004版比 0000版多了以下配置。

/ {
	funnel_top_ccplex@26020000 {
		in-ports {
			/delete-node/ port@2;
		};
	};

	/delete-node/ funnel_ccplex2@26050000;
	/delete-node/ cpu11_etm@27B40000;
	/delete-node/ cpu10_etm@27A40000;
	/delete-node/ cpu9_etm@27940000;
	/delete-node/ cpu8_etm@27840000;
	/delete-node/ dsu-pmu-2;

	cpus {
		cpu-map {
			/delete-node/ cluster2;
		};
		/delete-node/ cpu@8;
		/delete-node/ cpu@9;
		/delete-node/ cpu@10;
		/delete-node/ cpu@11;
	};

	thermal-zones {
		CPU-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		GPU-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		CV0-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		CV1-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		CV2-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		SOC0-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		SOC1-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
		SOC2-therm {
			cooling-maps {
				map0 {
					cooling-device = <&cl0_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&cl1_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>,
							 <&tegra_ga10b THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
				};
			};
		};
	};
};

Hi nkpyq,

不知道能否提供你的0004版本module的燒錄log?


Could you provide the flash log of your 0004 sku version?

flash-new-board.log (85.3 KB)