Jetson Nano won't boot when connected to the DP cable

When I try to start it, what I find is that my device doesnt boot up properly, the phenomenon is that it keeps rebooting over and over again. After that I tried to use ttl to get boot info and this what I got:

[  440.013747] mc-err: (255) csr_nvdisplayr: EMEM address decode error
[  440.020212] mc-err:   status = 0x20000092; hi_addr_reg = 0x0000007f addr = 0x7ffc136000
[  440.028518] mc-err:   secure: no, access-type: read
[  440.033565] mc-err: (255) csr_nvdisplayr1: EMEM address decode error
[  440.040109] mc-err:   status = 0x200020a1; hi_addr_reg = 0x0000007f addr = 0x7ffd300880
[  440.048358] mc-err:   secure: no, access-type: read
[  440.053398] mc-err: (255) csr_nvdisplayr1: EMEM address decode error
[  440.059955] mc-err:   status = 0x200020a1; hi_addr_reg = 0x0000007f addr = 0x7ffc5c6a80
[  440.068203] mc-err:   secure: no, access-type: read
[  440.073247] mc-err: (255) csr_nvdisplayr: EMEM address decode error
[  440.079703] mc-err:   status = 0x20002092; hi_addr_reg = 0x0000007f addr = 0x7ffd865080
[  440.088008] mc-err:   secure: no, access-type: read
[  440.093047] mc-err: Too many MC errors; throttling prints

When I unplugged the DP cable, it worked fine.
Device: Jetson ORIN NANO CLB 4G
JetPack SDK:5.1.2

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

Is this issue able to reproduce on devkit?

Here’s the full documentation of my inability to access the system after plugging in the DP cable.@ kayccc
result.txt (92.5 KB)

yes, i also uploaded the complete log.

yes, for some special nano, only can be resolved by reflash system using nvidiasdk.

  1. The log file you shared does not match the error you mentioned in the beginning.

  2. The log file you shared got truncated in each line. Resize the terminal and dump log again.

  3. According to the date, the BSP is already old one, please try to upgrade BSP version.

Sorry for the confusion.

  1. The problem in the title is due to the error displayed when i plug in the DP cable(system already start without plug DP cable), and screen fully white.

  2. The uploaded file is the log i get by typing reboot in terminal after plugging in the DP cable.
    So when i plugged in the dp cable and booted up to get the same log as in the case of the file i uploaded.

  3. Since the device has been reflashed now and is being used by someone else, i cant redo the demo for you.I will retest when the device is free.

PS:probably caused by booting with a nvme from another device(hardware model is exactly the same , and i can use it normally on other devices of the same hardware)

Yes, above is the possible cause of this issue.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.