Hi, I am using Jetson Nano Oring to do some data processing and machine learning. While I need to install the CProfileV. After pip install it in virtural environment, and diable the GUI and reboot it again.
But then I found, I cannot connect to it throug SSH, and cannot even find it through serial after connect it through typeC to my mac. Since I diabled the GUI, I cannot even see what happened through GUI.
I’ve also try to reset it through pin hearder (connect 9 and 10), but no thing happend. Now I feel like it a little bit hot, but the fan does not rotate, even the PWR grenn light is on.
After connect hdmi to screen after I power it, there is a wanning: test key is used and then the screen will shunt down. And I try to entery the recorver mode (connet pin 9 to pin 10 and then pulg power input), but the SDK Manager still cannot detect a board.
I even try to download nano orin image to a new sd card and insert to it. No thing changed. Is it a hardware issue? >_< really do not know what I should do
Does anyone have any solution about it? Appreciate it a lot!!!
But now I found that, every time when I open it, it will first hit LT4 launcher issue and winning with test keys, and then I will try to reboot again, after this second automatically reboot it will open normally. Is this correct? Or how could I solve this problem?
But now I found that, every time when I open it, it will first hit LT4 launcher issue and winning with test keys, and then I will try to reboot again, after this second automatically reboot it will open normally. Is this correct? Or how could I solve this problem?
This sounds abnormal. I think you didn’t understand that post. That post is just a temporary solution. It does not really root cause the reason why you get crashed.
I see… Could I try to flash the board with SDK maganer? Will it solve the problem? Since Test key warnning is keeping showning every time during the boot, and I use mmc card to reload the image, it still doesn’t work. I saw your suugetion in this post: Jetson AGX Orin shows Test key warning when booting - #20 by WayneWWW
I’ll try to see if this solve the problem.
Just want to clarify, “Test key warnning is keeping showning every time” is not a bug.
It is just a log printed in every boot. Even a normal boot situation would have this log.
You can follow this page to operate the serial console on your board. If the console still responds to you, it means the board is booting up, but maybe the desktop gui cannot be launched due to some unknown reason which we can check after you dump the log.
Will this be the reason of the crash of OS? Or it will just influence the booting time(boot again)?
Here is the dmesg.log I got after boot. dmesg.log (68.7 KB)
Oh! Actually after it boot twice (first boot will get L4TLancher: Attempting direct boot, and then will go to the second boot), I could then enter the GUI and could even develop on it. Currently it works well during the development, it just will encounter twice boot every time when I power it.
Each of your line in the log file got truncated. Please read it by yourself first.
For example, you can see there is a fixed length cut for each line and the log after that cannot be read…
I think, actually it is “twice boot”, there is a large blank after first boot. And the sercond boot is down by the system, after the first boot, it will enter the L4TLauncher and automatically boot again.
This is new log (the blank between them indicts the second boot by itself) log (85.2 KB)
And I check the log, I’m not sure, but does the problem happend around here?
