I have a production module Jetson Nano Production Module. I started the flash process using the SDK manager and connected Keyboard, Mouse, and Monitor before flashing ( I tried connecting them after the flash process too.) The Jetson successfully boots up and the monitor attached shows the ubuntu installation GUI (screenshot attached) but Jetson does not recognize the keyboard and mouse (they are not even receiving power). It seems like the ports are suddenly not working. So I cannot interact with the OS to complete the installation.
I cannot perform a headless setup since I am booting from an eMMC instead of the SD card and requires to have the image already flashed to the card.
I have also tried using Serial Console (minicom and screen) but does not receive any data in the terminal and is black.
This method does not seem to work. The sdk manager still asks for Target device pwd and username, the display of the jetson is still not recognizing the usb ports and gets stuck at system configuration.
Is there any way I can boot from a USB and change the installation partition to the emmc storage?
Used the command along with the script sudo ./flash.sh jetson-nano-emmc mmcblk0p1
Still getting the System Config page on boot up.
I have tried using the minicom serial console but nothing is displayed in the serial console. The port connection has been checked.
Any fixes / alternative methods i can try?
It sounds like you didn’t run the script correctly. Where and how did you use this script? Please note that if you run this script, you shall never let sdkmanager run again to overwrite the existing files.
Also, please also share your flash log to make sure you really let the board get correctly flashed.
I used SDK manager to download the OS and its dependencies. After doing that I downloaded the script into /home/<user>/nvidia/nvidia_sdk/JetPack_4.5.1_Linux_JETSON_NANO/Linux_for_Tegra/
after which extracted it and ran sudo ./l4t_create_default_user.sh -u <usr_name> -p password
then finally ran the flash command
What I can suggest now is you can follow this page to use the serial console from uart instead of the usb one. This serial console setup is very common when we are dealing with boot problem. If your script really sets the user account correctly, this serial console will serve as a ubuntu terminal and ask your user account and pwd. Otherwise, it will just stuck and no prompt.
Actually, I think your board has high possibility that requires to RMA. The behavior sounds like the usb port has broken. Thus, whether you need to follow this page and dump the uart log depends on you. Even after we see the log, we may still need to ask you to do RMA if this is really hardware problem.
