Hello,
I am looking to flash the Jetson Orin Nano Devkit using the SDKManager.
I have connected pins 9 and 10 of the Jetson’s header pins to put it in force recovery mode.
However, I encountered an error stating ‘failed to read rcm_state’, and I am unable to complete a perfect flash.
The host PC is using Ubuntu 20.04.
Please advise me on how to resolve this error.
I will attach the log file.
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_Nano_modules_2023-12-20_10-32-43.zip (497.3 KB)
I am not sure what are you talking about. You don’t need to care about “failed to read rcm_state”. It is even there in a normal flash case.
Your log told the flash process is already done without error…
If there is still an error, then a serial console boot log would be more useful.
The flashed Orin Nano Devkit had several issues. I thought I needed to solve the error ‘failed to read rcm_state,’ but if it also occurs in normal flash cases, it seems that this error is not the cause of the problem. What could be the reason why the flashed Orin Nano Devkit does not have language, keyboard, timezone, and account settings at startup?
I would appreciate it if you could tell me how to check the boot log of the serial console.
Because you specified --nv-auto-config --username go…
Regarding the username, I specified it when flashing with the SDK Manager, but I don’t remember specifying the language or anything else. Is it default that the account settings, like the ones I did when I first booted up the Jetson after flashing, are not performed?
If you specify the username before flashing, then YES.
I see, I understand. However, when I used the SDK Manager to flash the Orin Nano Devkit around July previously, there were no errors, and account settings such as language, keyboard, and time zone were configured at startup. Has the specification for account settings changed since then? It seems that the current account settings default to the information on the host PC, but could you please tell me how to remove that and set up the Devkit at startup after flashing?
Delete the BSP and do not set user account before flashing.
I don’t know if the Orin Nano has USB-C now on the serial console port, it used to be micro-OTG. If you are facing the connectors of the Orin Nano though, it will be on the left (not the port used for flashing). Then you use an application like gtkterm, minicom, picocom, or PuTTY on a host PC while that port is connected. Similar documentation is here:
- https://developer.ridgerun.com/wiki/index.php/NVIDIA_Jetson_Orin/In_Board/Getting_in_Board/Serial_Console
- https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/
The port on the host PC is most likely “/dev/ttyACM0” (the number might differ if you’ve already got some sort of serial port there). The host PC itself can log the entire session via the serial console program. Settings are 115200 8N1. Example:
sudo apt-get install gtkterm
sudo gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyACM0
Should the BSP be deleted from the SD card? Or from the host PC?
Delete it on your host PC, download it again, and re-flash the device.
Should I uninstall it through the SDKManager to remove it? Or is there another method?
Delete stuff in these folders:
https://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html#step-2-review-components-and-accept-licenses
Download it again, and flash the device again.
Is that clear for you?
I understand about the deletion of the BSP.
I would like to know more about how to proceed without setting up a user account.
Leave OEM Configuration as Runtime in the link I posted above.
Any other thing you don’t know?
Thank you for helping me solve my problem. I have another issue. When I start the Orin Nano Devkit, the monitor displays “INPUT NOT SUPPORTED,” and the Jetson desktop does not appear. This issue started occurring after flashing the Devkit with the SDKManager. Do you know how to resolve this?
Please file another topic for unrelated issues.
I understand that this issue is not related to flashing the Devkit with the SDKManager. I will post a question in a different topic. Thank you for your assistance.