Enable spi,but cause screen display white

Hi,my board is TX2, jetpack4.4(32.4.3),i used “sudo ./jetson-io.py” to configure 40 pin of J21 for spi(19,21,23,24). when i restart the board, the screen holds white for a while. but finally it become OK.can you tell me what is the problem. I have uploaded dmesg log.dmesg.txt (74.9 KB)

Hi,

I see your dmesg tries to unblank the monitor at this time.

[ 24.605611] tegradc 15210000.nvdisplay: unblank

Could you check the dmesg and what was the time if you don’t enable SPI?

Also, is this issue on TX2 devkit?

[quote=“WayneWWW, post:4, topic:164287”]
nvdisplay
[/qu
on TX2 devkit,i did not enable spi,screen did not become white,but dmesg also tells “tegradc 15210000.nvdisplay: unblank”, and i uploaded log named “dmesg_tx2_devkit_do_not_enable_spi.txt”. And I also uploaded uart(J21.6.8.10) log for “enable spi” and “did not enable spi”,
and i think you will find something different in the two uart log after “staring kernel”. can you help me ?dmesg_tx2_devkit_not_enable_spi.txt (66.4 KB) dmesg.txt (74.9 KB) enable_spi_uart_log.txt (29.3 KB) not_enable_spi_uart_log.txt (25.1 KB)

We can reproduce this issue on our side. Need further check internally.

Issue will be fixed at the next release. Please wait for our announcement at coming weeks.

did this issue fixed at L4T32.5(JETPACK4.5)?, if fixed,how can i update my board(L4T32.4.3) to the latest 32.5?

Hello,

Please refer to the OTA document.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/updating_jetson_and_host.html

did the issue about display fixed at 32.5?

We already resolved this issue in the end of last year.
This is not display issue but more like uboot issue that causes display gone.

what should i do to resolve the issue at L4T32.4.3?update uboot?how

diff --git a/include/configs/tegra186-common.h b/include/configs/tegra186-common.h
index 16059c5..42141fd 100644
--- a/include/configs/tegra186-common.h
+++ b/include/configs/tegra186-common.h
@@ -68,6 +68,9 @@
 		"/serial-number:" \
 		"/trusty/status\0" \
 	"fdt_del_copy_node_paths=" \
+		"/reserved-memory/fb0_carveout:" \
+		"/reserved-memory/fb1_carveout:" \
+		"/reserved-memory/fb2_carveout:" \
 		"/reserved-memory/ramoops_carveout:" \
 		"/reserved-memory/vpr-carveout\0"

Please check if you can apply this patch to your uboot and then reflash it.