Production Module eMMC Flash Procedure

nanoj · January 21, 2020, 10:48pm

Are there instructions to flash the eMMC on a Jetson Nano production board?

I tried using the SDK manager to program the board’s eMMC , but there were only options for micro SD card.

The Jetpack SDK Manager states “Verify the SD card is inserted in the Jetson Nano module”, and to “make sure the Jetson Nano’s Ubuntu OS is up and running”.

Any help will be appreciated.

mdegans · January 22, 2020, 12:55am

Are you sure you have the right hardware selected for the “Target Board”? There should be multiple choices in the dropdown for Nano, one for dev and one for production.

WayneWWW · January 22, 2020, 6:05am

Please share what target board you chose in sdkmanager. You could try to paste a screenshot directly.

nanoj · January 22, 2020, 1:52pm

For Hardware Configuration, I have Host Machine selected, and Target Hardware selected as “Jetson Nano (P3448-0020)”

When it gets to the Flash procedure, step 2 states “Verify the SD card is inserted in the Jetson Nano module”, and then step 3 includes a dropdown for Automatic Setup or Manual Setup.

Please see screenshots linked below:

Target Selection:
https://imgur.com/X2Pi7Vv

Flash Screen:
https://imgur.com/a/RaG3MWO

Thanks

WayneWWW · January 22, 2020, 2:10pm

Hi nanoj,

No worry. This is not a error. It is asking for the user account and password of your tegra device.

nanoj · January 22, 2020, 3:43pm

@WayneWWW

I do not have a user account and password on the tegra device because I did not yet load anything onto it. I was expecting the Jetpack SDK manager to flash the board with OS and NVIDIA SDK. Must I flash Ubuntu OS onto the board first before using the SDK manager? If so, how can this be done?

nanoj · January 22, 2020, 4:39pm

UPDATE: I was able to use the SDK Manager to load the OS and NVIDIA SDK’s. On our production board, the board enters boot mode when attaching USB Micro B cable from target board to Host. I attached the USB Micro B cable before launching the SDK manager, and this time the flash occurred automatically immediately after all setup files were downloaded.

WayneWWW · January 30, 2020, 4:39am

Hi nanoj,

Sorry for late reply. Have you resolved your issue?

john.roberts · May 12, 2020, 6:58pm

I am using Auvidea JN-30 Board for a Jetson Nano with 16GB of emmc. How do I flash Ubuntu Core onto it?

WayneWWW · May 13, 2020, 2:28am

Hi John,

Please read the document on the dlc.

john.roberts · May 24, 2020, 7:16pm

Wayne,

I’ve the Dev Kit working. Bought some SOMs and the carrier boards (Auvidea JN-30) for the same, can not find instructions as to how to flash the eMMC on the Production Board, it does not have an SD card. Can you please point me to a specific link?

Tried a few more times, think the problem is the Board goes into Continue Boot … mode. Per the instructions, I need to get it into Fast Recovery mode, I’ve keyboard connected to the USB Board of the Carrier Board, but it seems non-functional. I can not use the Arrows to move it up or down while its booting up. Any ideas?

john.roberts · May 27, 2020, 2:49pm

Wayne,

Anything further here?

WayneWWW · May 28, 2020, 7:35am

Hi,

Sorry missing your reply. Your carrier board should have recovery mode pin. Maybe need to consult with Auvidea or check with their board datasheet to know where is it.

If it does not have, then the alternative is using “sudo reboot forced-recovery” on serial console or terminal.

Then, connecting a micro USB cable between x86 ubutnu host and your production board, if it successfully entered recover mode, command “lsusb” on your host will show nvidia corp.

After that, you could use sdkmanager to flash your board.

Actually, this method is applicable to devkit to flash sdcard too.

john.roberts · May 30, 2020, 2:31pm

Wayne,

This seems to be a problem with the Device type, when I run the lsusb I get “Bus 001 Device 006: ID 0955:7118 NVidia Corp.”, printout of the terminal on the Ubuntu workstation is below think its looking for, 0955:7f21

=====================
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0c45:6d12 Microdia
Bus 001 Device 006: ID 0955:7118 NVidia Corp.
Bus 001 Device 004: ID 8087:0025 Intel Corp.
Bus 001 Device 003: ID 187c:0550 Alienware Corporation
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

In the SDK Manager it exits with an error that I’ve selected a wrong device with the following error log in the terminal.

========================================

10:08:06 DEBUG : running command < [ lsusb | grep -c "0955:" -ne 1 ] >
10:08:06 INFO : command finished successfully
10:08:06 DEBUG : running command < [ lsusb | grep -c "0955:" -gt 1 ] >
10:08:06 DEBUG : command terminated with error
10:08:06 ERROR : Could not detect NVIDIA Jetson device connected to USB. Verify that: 1. The device is connected to this host machine with a USB cable. 2. Jetson’s Ubuntu OS is up and running. 3. Ubuntu ‘System configuration wizard’ is completed on the device. This can be validated by running the ‘lsusb’ command on your host, and look for “0955:7f21” (NVIDIA Corp).
10:08:18 DEBUG : running command < [ lsusb | grep -c "0955:" -ne 1 ] >
10:08:18 DEBUG : command terminated with error
10:08:18 INFO : Only one NVIDIA device detected, as expected.
10:08:18 DEBUG : running command < lsusb | grep 0955:7020 >
10:08:18 DEBUG : command terminated with error
10:08:18 INFO : Jetson device is in recovery mode.
10:08:18 DEBUG : running command < lsusb | grep 0955:7f21 >
10:08:18 DEBUG : command terminated with error
10:08:18 DEBUG : running command < lsusb | grep 0955: >
10:08:18 INFO : Bus 001 Device 006: ID 0955:7118 NVidia Corp.
10:08:18 INFO : command finished successfully
10:08:18 ERROR : Wrong Jetson device is detected. Please connect the correct device to continue (or select a different device in STEP 01).
10:08:30 DEBUG : running command < [ lsusb | grep -c "0955:" -ne 1 ] >
10:08:30 DEBUG : command terminated with error
10:08:30 INFO : Only one NVIDIA device detected, as expected.
10:08:30 DEBUG : running command < lsusb | grep 0955:7020 >
10:08:30 DEBUG : command terminated with error
10:08:30 INFO : Jetson device is in recovery mode.
10:08:30 DEBUG : running command < lsusb | grep 0955:7f21 >
10:08:30 DEBUG : command terminated with error
10:08:30 DEBUG : running command < lsusb | grep 0955: >
10:08:30 INFO : Bus 001 Device 006: ID 0955:7118 NVidia Corp.
10:08:30 INFO : command finished successfully
10:08:30 ERROR : Wrong Jetson device is detected. Please connect the correct device to continue (or select a different device in STEP 01).
10:08:42 DEBUG : running command < [ lsusb | grep -c "0955:" -ne 1 ] >
10:08:42 DEBUG : command terminated with error
10:08:42 INFO : Only one NVIDIA device detected, as expected.
10:08:42 DEBUG : running command < lsusb | grep 0955:7020 >
10:08:42 DEBUG : command terminated with error
10:08:42 INFO : Jetson device is in recovery mode.
10:08:42 DEBUG : running command < lsusb | grep 0955:7f21 >
10:08:42 DEBUG : command terminated with error
10:08:42 DEBUG : running command < lsusb | grep 0955: >
10:08:42 INFO : Bus 001 Device 006: ID 0955:7118 NVidia Corp.
10:08:42 INFO : command finished successfully
10:08:42 ERROR : Wrong Jetson device is detected. Please connect the correct device to continue (or select a different device in STEP 01).
10:08:47 INFO : Device Mode Host Setup in Flash : Install ‘Device Mode Host Setup in Flash’ Skipped
10:08:47 INFO : Flash Jetson Nano : Install ‘Flash Jetson Nano’ Skipped
10:08:51 INFO : Device Mode Host Setup in Target SDK : Install ‘Device Mode Host Setup in Target SDK’ Skipped
10:08:51 INFO : DateTime Target Setup : Install ‘DateTime Target Setup’ Skipped
10:08:51 INFO : CUDA Toolkit for L4T : Install ‘CUDA Toolkit for L4T’ Skipped
10:08:51 INFO : cuDNN on Target : Install ‘cuDNN on Target’ Skipped
10:08:51 INFO : TensorRT on Target : Install ‘TensorRT on Target’ Skipped
10:08:51 INFO : OpenCV on Target : Install ‘OpenCV on Target’ Skipped
10:08:51 INFO : VisionWorks on Target : Install ‘VisionWorks on Target’ Skipped
10:08:51 INFO : VPI : Install ‘VPI’ Skipped
10:08:51 INFO : NVIDIA Container Runtime with Docker integration (Beta) : Install ‘NVIDIA Container Runtime with Docker integration (Beta)’ Skipped
10:08:51 INFO : Multimedia API : Install ‘Multimedia API’ Skipped
10:08:52 INFO : All done!

INSTALLATION FAILED
Please review the terminal tab for details. Resolve and RETRY.

Flash of target hardware was skipped.

EXPORT LOGS

RETRY

FAILED ITEMS

STOP TRYING

WayneWWW · June 1, 2020, 3:00am

Hi,

This error is kind of new. I don’t see this number in official document.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fquick_start.html

Could you try to use the “Linux_for_Tegra” folder downloaded by sdkmanager and use the flash.sh tool to flash the board directly?

https://elinux.org/Jetson/General_debug

john.roberts · June 2, 2020, 7:40pm

Wayne,

Do you by any chance send me the command? In the instructions you sent me the links are only for the Development Board not for Production Board with emmc, would appreciate the help.

Thanks,

WayneWWW · June 3, 2020, 2:20am

Please read the quick start guide on download center. All the documents are there.

Also, all the board config you can flash is under the Linux_for_Tegra folder. For example, jetson-tx2.conf implies you could flash with “sudo ./flash.sh jetson-tx2 mmcblk0p1”.

andyinyakima · June 17, 2021, 4:22pm

Hi John,

Did you resolve this problem. I just received a new emmc module and the SDK doesn’t seem to recognize it.
I had purchased another emmc module in Feb of 2020 and it was recognized. I paid $20 more dollars for it.
I also think it had a different vendor/product id. If you found the work around could you please let me know.

Thank you!

Andy in Yakima