Hi,
We are evaluating the Orin Nano with two NVMe drives connected to PCIe0 (x4) and PCIe2 (x2).
Is this possible?
Thx
Yen
Hi,
We are evaluating the Orin Nano with two NVMe drives connected to PCIe0 (x4) and PCIe2 (x2).
Is this possible?
Thx
Yen
*** Please note that this reply is generated by LLM automatically ***
The Jetson Orin Nano supports multiple PCIe interfaces, and connecting two NVMe drives to PCIe0 x4 and PCIe2 x2 is possible, but there are some limitations and considerations to keep in mind.
According to the Jetson Orin NX Series and Jetson Orin Nano Series Product Design Guide (DG-10931-001_v1.4), the Jetson Orin Nano has multiple PCIe controllers, including PCIe C1, PCIe C4, and PCIe C5. The PCIe C4 controller supports up to x4 link width, and the PCIe C5 controller supports up to x8 link width.
The Jetson AGX Orin Devkit Default PCIe Configuration table shows that the M.2 Key M slot (PCIe C4) supports up to x4 link width, and the PCIe slot (PCIe C5) supports up to x8 link width. However, the table does not explicitly mention the PCIe2 interface.
To determine if the Jetson Orin Nano supports connecting two NVMe drives to PCIe0 x4 and PCIe2 x2, we need to refer to the Jetson Orin Nano’s technical documentation and the PCIe configuration table.
Assuming that PCIe0 x4 refers to the M.2 Key M slot (PCIe C4) and PCIe2 x2 refers to another PCIe interface, it is possible to connect two NVMe drives to these interfaces. However, the actual performance and functionality may depend on the specific NVMe drives, the PCIe configuration, and the system’s power and thermal management.
In comparison, the Jetson AGX Orin has a more comprehensive PCIe configuration table, which shows that the M.2 Key M slot (PCIe C4) supports up to x4 link width, and the PCIe slot (PCIe C5) supports up to x8 link width. The Jetson AGX Orin also has a more detailed description of the PCIe configuration and the supported link widths.
In summary, connecting two NVMe drives to PCIe0 x4 and PCIe2 x2 on the Jetson Orin Nano is possible, but the actual performance and functionality may depend on the specific NVMe drives, the PCIe configuration, and the system’s power and thermal management. It is recommended to refer to the Jetson Orin Nano’s technical documentation and the PCIe configuration table for more detailed information.
Additionally, you may want to consider the following:
It is recommended to consult the Jetson Orin Nano’s technical documentation and the PCIe configuration table for more detailed information and to ensure that your specific use case is supported.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
I can positively confirm that 2 nvme ssd can be connected to the Orin Nano dev kit
I have one Lexar NM790 m.2 2280 as /root and /boot drive.
In addition, I have one extra Raspberry Pi nvme m.2 2230 as extra data drive.
Both ssd’s run perfectly. It’s convenient that data remains on the smaller ssd, while the other drive sometimes must be re-flashed during experimenting.
Hi wolthuis,
Thanks for your information.
How did you configure which ssd to flash the OS to?
Thx
Yen
Good question 🙂. I did the following a few times:
I have a SD card with the latest JetPack 6.2.1 (ca. 10 GB zipped) (using Balena etcher and any Linux or Windows laptop)
I start the Orin Nano from the SD card
Then I install Balena Etcher on the running Orin Nano
I download again the zipped JetPack 6.2.1 for SD card on my running Orin Nano
I use Balena Etcher, running on the Orin Nano to burn the JetPack 6.2.1 sd card image that’s on my Orin Nano on the nvme (you can simply choose the right one from Balena)
Then, I use this trick : Go to /boot/extlinux/extlinux.conf find the following part under bootargs and change accordinly: root=/dev/mmcblk0p1 → root=/dev/nvme0n1p1
It is advised to do a reset in the bios, after a restart. Now, the Orin Nano starts with the fully loaded JetPack 6.2.1 system but now from the nvme. Take out the sd card.
I did this a few times and it sounds difficult but it is really easy and fast. No SDK Manager is needed.