reComputer J4012 | J401 | Seeed Studio Wiki #105
giscus
bot
-
reComputer J4012 | J401 | Seeed Studio WikiFlash JetPack to reComputer J4012 (J401 carrier board) https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/ |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 32 replies
-
|
It's no working, I ask this question in Nvdia Jetson nano orin forum. I’m running to “Step 3: Start the flashing process” stop the flash. Waiting for target to boot-up… I had using lsusb to check ID 0955:7323 NVidia Corp., why Jetson Nano Orin boot-up fail? but got this reply from WayneWWW => Orin Nano is not supported in the BSP yet. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, the above message concerns me a bit. I don't have an Orin nano but I do have an recomputer Orin NX 16GB. Is it confirmed that the above method will correctly flash the Orin NX on the recomputer carrier board? A related question, I started my Orin NX and let it use all of the available space. Now I want the main parition to be smaller. However, this is not straight forward implying that I may need to reflash it, but then I'm concerned about what Corry Weng experienced. But then it occurred to me that the nvme card is removable. I could in principle simply re-write all of the partitions to a starting state. Are the partition images for the recomputer J4012 Orin NX 16GB downloadable from some place ? Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
I also have the Orin NX 16GB and this does not seem to work. I am getting the following error |
Beta Was this translation helpful? Give feedback.
-
|
wow, interesting:D |
Beta Was this translation helpful? Give feedback.
-
|
Hello @hcfman @coryweng @sy-cobot , According to NVIDIA official, the flashing process of the wiki will only work for Orin NX at the moment. This is BSP related. NVIDIA has not yet released the support for Orin Nano production-grade version. Is that the production-grade version without SD-card slot you are trying to flash? @coryweng As for the errors, do not keep the recovery jumper connected all the time during flashing process. Just jumper it, turn on the device and remove the jumper after that. Because when it says "Waiting for target to boot-up...", the recovery jumper should not be connected that time. |
Beta Was this translation helpful? Give feedback.
-
|
@lakshanthad thank you for your help. I was able to successfully flash the Orin NX in the J4012. I was using JetPack 5.1 with NVIDIA L4T 35.2.1 but I was trying to flash using a native Ubuntu 22.04 machine. I tried a native Ubuntu 20.04 machine and the flashing worked without issues. I know the Nvidia SdkManager only runs on Ubuntu 20.04 but I was previously able to use the flash.sh script on Ubuntu 22.04 to flash the AGX Orin. It seems the initrd flashing only works on Ubuntu 20.04. I did not have to format the drive or anything, it worked as is. I can also confirm that flashing with the RT patches is working Thanks again for all the help! |
Beta Was this translation helpful? Give feedback.
-
|
It is great to hear that it is working now for you @sy-cobot . These are very important findings. I will add them to the J4012 wiki in order to help others as well. |
Beta Was this translation helpful? Give feedback.
-
|
Today I bought a Jetson Nano Developer Kit A02 for clean Ubuntu system it’s Jetpack 4.4.1 [L4T 32.4.4]. same as before
this time stop at Step 1: Generate flash packages… sorry I don't know what does RT patches and how to work and step. |
Beta Was this translation helpful? Give feedback.
-
|
@lakshanthad I did some more digging into the error I was getting and not being able to flash from Ubuntu 22.04. It turns out the actual problem causing the mount.nfs: Connection timed out error was not the fact I was using Ubuntu 22.04, but rather just that the firewall was enabled and seems to be blocking the mounting of NFS needed for flashing. I disabled the firewall and the flashing worked from an Ubuntu 22.04 machine. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for sharing your findings @sy-cobot . This will definitely help others who will face similar problems :) |
Beta Was this translation helpful? Give feedback.
-
|
I saw this message in Nvdia forum. It seen seeedstudio need to fix this bug, no thing about Nvdia. https://forums.developer.nvidia.com/t/timeout-while-flashing-orin-nx/247365/2 |
Beta Was this translation helpful? Give feedback.
-
|
I've not tred this but it should be a work-around for people having problems with flashing. But it relies on having a pristine/not yet turned on J4012 to prepare. I don't have that anymore because I turned mine and and it personlized it for me. But Seeed Studios could do this. Essentially, if Seeed Studios were to copy the contents of partition #1 the nvme disk to a file and make this available for download, then other users should be able to download this and reverse the process to fixing their installation likely without requiring a reflash. This could be done with: dd if=/dev/nvme0n1p1 of=some-file-name bs=512 and then in reverse dd if=some-file-name of=/dev/nvme0n1p1 bs=512 This makes the assumption that other parts of the nvme disk still okay and it's just the Linux installation that requires restoring. I have ordered one of these devices from aliexpress to make it easier. It turns an nvme disk to a USB disk to allow one to modify the disk contents from another disk, preferably another LInux: ORICO M2 SSD Enclosure NVMe 10Gbps PCIe SSD Box for M.2 NVMe NGFF SATA SSD
PS. When my nano devices arrive, I'm going to take some precautions and change the partitioning to create a restore partition for the pristine OS before I first turn it on. I'll create the backup partition at the end of the disk so that when I'm done with it I can grow the main partition to fill that space. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and be sure to choose the nvme m.2 version, they also have SATA versions there if you are going to get one of these things. Alternatively you could stick it into another computer that supports nvme m.2 but this often involves undoing a lot of screws |
Beta Was this translation helpful? Give feedback.
-
|
I installed “Jetson Linux 35.3.1” to reComputer J4012. |
Beta Was this translation helpful? Give feedback.
-
Your understanding of that is correct. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. I will recreate all the above scenarios tomorrow on my J4012 when I get back to the office and then feedback to you. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @atinfinity, I have recreated all your scenarios using reComputer J4012 and the device powered off as normal. Can you try to use SDK Manager to flash the device with JetPack along with SDK components? The latest version of SDK manager supports Orin NX flashing to JP5.1.1. The board might not be detected on SDK manager, but you can just select Orin NX module and then choose NVMe when it asks about the storage medium for flashing. Then it will flash to the connected SSD. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your suggestion. I tried this installation. |
Beta Was this translation helpful? Give feedback.
-
|
That is great to hear! |
Beta Was this translation helpful? Give feedback.
-
|
I'm able to flash correctly a reComputer J4012-Edge AI Device with NVIDIA Jetson Orin™ NX 16GB module with the command: cd ${L4T_DIR} Now I'm try to flash the same device with an encrypted disk with the command: echo "...omitted...." > ekb.key but it fails with : Some one have any idea ? |
Beta Was this translation helpful? Give feedback.
-
|
For Jetson Orin Nano 8GB, do these instructions (but switch to |
Beta Was this translation helpful? Give feedback.
-
|
I am trying to install a new M.2 SSD drive, but the flashing is falling at -> [ 0.0204 ] ERROR: failed to read rcm_state sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal /home/tupapi/Downloads/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 internal
Create folder to store images to flash ############################################################################### L4T BSP Information:R35 , REVISION: 2.1User release: 0.0############################################################################### [ 0.0185 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet [ 0.0548 ] Parsing partition layout |
Beta Was this translation helpful? Give feedback.
-
|
Just attempted to flash my Orin NX and received the following (after about two hours of runtime): Any advice? |
Beta Was this translation helpful? Give feedback.
Hello @hcfman @coryweng @sy-cobot ,
According to NVIDIA official, the flashing process of the wiki will only work for Orin NX at the moment. This is BSP related. NVIDIA has not yet released the support for Orin Nano production-grade version. Is that the production-grade version without SD-card slot you are trying to flash? @coryweng
As for the errors, do not keep the recovery jumper connected all the time during flashing process. Just jumper it, turn on the device and remove the jumper after that.
Because when it says "Waiting for target to boot-up...", the recovery jumper should not be connected that time.