zax
1
Hi,
I got a jetson nano module which is for devkit ( P3448-0000 the som with a sdcard slot )
I try to use sdkmanager to flash J4.6.6 and log shows flash success
But after it reboot, it just stuck at NV’s logo where uart log show it stop at uboot
I enter “boot”, it enter the kernel and I can login to the system
Some questions:
- Can I skip the step “enter “boot”” in Uboot to use the device?
- The flash.sh command will be “sudo ./flash.sh jetson-nano-devkit mmcblk0p1”?
- After I login to the system, uart always show many garble message, is it normal?
Here’s boot uart log and sdkmanager debug log
boot_uart.txt (20.8 KB)
SDKM_logs_2025-03-19_15-18-37.zip (1.2 MB)
>ubuntu login:
Ubuntu 18.04.6 LTS ubuntu ttyS0
����������������8�������������������������ਉչ�Õlogin:
Ubuntu 18.04.6 LTS ubuntu ttyS0
ubuntu l��������������������buntu login:
Ubuntu 18.04.6 LTS ubuntu ttyS0
ubuntu login: �����������������������������չ�Õlogin:
Ubuntu 18.04.6 LTS ubuntu ttyS0
����������������������������������������|ubuntu login:
Ubuntu 18.04.6 LTS ubuntu ttyS0
ubuntu login: ��������������������������ubuntu login: �Ubuntu 18.04.6 LTS ubuntu ttyS0
�����������������������������������չ�Õlogin:
Ubuntu 18.04.6 LTS ubuntu ttyS0
���������������>�ubuntu login:
Ubuntu 18.04.6 LTS ubuntu ttyS0`
I saw the uart console is already there waiting for you to enter and login. Did you configure any account there?
As for the garbled message, what is the command you are using to enable serial log?
zax
3
Hi,
I have preconfig username and password by using sdkmanager
sudo minicom
By the Way
It’s weird that I reflash the image last night then it is normal now
There’re too much experiment to list since several days
Is it possible that static electricity noise cause "Hit any key to stop autoboot " to be trigger in uboot?
sudo minicom
Please set the baud rate to 115200 explicitly.
Is it possible that static electricity noise cause "Hit any key to stop autoboot " to be trigger in uboot?
Don’t know what you are talking about here. Your log provided yesterday didn’t have any problem in uboot either.
zax
5
The baud rate always 115200 for our usage
actually it stuck here
“boot” is the command I entered, so it enter to kernel
Oh ok. Then it is indeed something wrong in the UART as noise that triggered the keyboard.
Do you have other wire for the UART? If this is devkit, I think hardware problem is more related.
zax
7
Hi,
Thanks for reply
We will conduct some tests on hardware
The ticket can now be closed. Thanks again
system
Closed
8
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.