When i start the SDKManager, it is detecting the jetson nano board, But when it comes to Flashing Part, it is not showing that no board is connected.
Is there any issues with ‘0955:7118’
Regards
Ramesh
Hi Ramesh,
You posted in the community feedback category, this should be posted in the Jetson Nano forum.
I will move it over for you.
Tom
Hi ramesh493,
Are you using Nano-emmc or Nano-SD modules?
Can you try with manual put device into recovery mode?
Hi Carolyuu,
I am using Nano emmc, and try to keep the carrier board in recovery mode manually. Still the issue is same.
Regards
Ramesh
Two possibilities
-
Your successfully put the board into recovery mode, but your host is not able to detect it → Mostly when your host is a VM.
-
You didn’t put the board into recovery mode. → Please share the steps you are using to put board into recovery.
Hi Wayne,
I am using a separate Linux PC.
The Nano is in Recovery mode.
When i run th SDKmanager, it is detecting the jetson nano board and i have downloaded the necessary files.
When it comes to Flashing Process, it is not detecting the Jeston nano board.
Regards
Ramesh
Hi,
Could you directly try to use flash.sh instead of sdkmanger?
SDKM should already download the tool in your ~/nvidia/. There should be a Linux_for_Tegra folder under this.
For nano emmc, please run
sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1
Hi Wayne,
it is not Devkit, it is Nano module with different carrier board.
Please see the attached screenshot.
Regards
Ramesh
Are you sure that flash port on the custom carrier board is really the usb0?
BTW, That board name is a fixed string/file. You cannot remove “devkit” just because it is not a devkit board.
Those board names are those *.conf file under your Linxu_for_Tegra folder. If there is a tegra123.conf, then you can run → flash.sh tegra123 mmcblk0p1.
Hi Wayne,
I have this reply from the support of carrier board.
" It is very weird that the flash script does not find your Nano, likely due to the USB product id which seems off. Your Nano shows as ‘0955:7118’ when it should be ‘0955:7f21’. Even after checking google I can only find a single hit with this USB id which is this post in NVIDIAs developer forums:
Jetson Nano booting up to TinyLinux
Could you also check how the SDK Manager reacts? After connecting the Nano to your host PC and starting the SDK Manager it should show you a popup that it has found a device. Maybe try flashing the Nano from there in case this works. Other than that I am not sure what else the problem might be and you may need to post on the NVIDIA forums or contact the the vendor whom you purchased your module from to check if they have heard about this."
Steps to install from the support.
"You can either find the Nano firmwares just below the Xavier NX firmware section or by clicking the following download link for our latest Nano firmware for JetPack 4.6 (L4T 32.6.1): https://www.auvidea.eu/download/firmware/Jetpack_4.6/JetPack_4.6_NANO_JN30B_v1.zip
To apply the firmware extract the downloaded .zip file as well as the compiled_kernel.zip inside. Copy the dtb folder to ~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/kernel/ (change path according to your install) to merge the folders and overwrite the stock .dtb files. Next with your terminal ‘cd’ into the Linux_for_Tegra directory and enter ‘sudo ./apply_binaries.sh’ to apply the changes. Now you can either flash your Nano using the SDK Manager or via 'sudo ./flash.sh jetson-nano-emmc mmcblk0p1. "
Regards
Ramesh
Hi,
Do you have only this jetson nano on your side or you have any other board/module that could be in use?
Hi Wayne,
I have only this Jetson Nano and this carrier board Search Results for “JN30B ” – Auvidea
Regards
Ramesh
Hi Wayne,
If you are available, can we have a remote session?
Regards
Ramesh
There is no such service here.
I understood that, thank you
Please try to use the cable to dump the uart log when you power on the board.
This case is for devkit. I don’t know whether your board has those pins or not. You could consult with your board vendor for info.
Hi Wayne,
Does it have any issue with the USB product ID? 0955:7118’ when it should be ‘0955:7f21’
There are two kinds of USB product ID that would come from the board.
When the board is correctly in recovery mode, it should be ‘0955:7f21’ for jetson nano.
However, when the board is booting into kernel, the kernel usb device mode driver will also have it own usb product id . I don’t remember what it that. Maybe that is the 0955:7118.
If you always see 7118, it probably means you didn’t put your board into recovery mode at all. That is why I asked you to dump log. Because the log will tell whether it is in recovery mode.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.