I have a custom carrier for the Jetson Orin NX. I want to add a second ethernet port. Presently I have it wired to the PCIE port using a PCIE to Ethernet controller. I’m wondering if anyone has experience using a second ethernet port such as that on the Waveshare Jetson development kit that has 2 ethernet ports. I’m also wondering if I’m going to hit a snag not using a Realtek part or if maybe I should consider Ethernet-to-USB and utilize the SODIMM pins 57, 59, 51, 53, etc for USBSS-to-ethernet.
That way I could use this second port for GbE communication and the first GbE port could be used for either ethernet comms or some other protocol over ethernet like EtherCAT (which should be supported with a SOEM library change).
*** Please note that this reply is generated by LLM automatically ***
To add a second Ethernet port to your custom carrier for the Jetson Orin NX, you have a few options to consider. I’ll outline the pros and cons of each approach to help you decide.
Option 1: Using a PCIe to Ethernet controller (your current setup)
- Pros:
- You’ve already implemented this solution, so you have a working setup.
- PCIe to Ethernet controllers are widely available and relatively inexpensive.
- Cons:
- You’re using a PCIe port, which might limit your flexibility if you need to use that port for other purposes.
- You might encounter compatibility issues or performance limitations with certain controllers.
Option 2: Adding a second Ethernet port using a Realtek part (like the Waveshare Jetson development kit)
- Pros:
- Realtek Ethernet controllers are widely used and well-supported in the Linux kernel.
- You can leverage the existing driver support and avoid potential compatibility issues.
- Cons:
- You’ll need to ensure that the Realtek part is compatible with your custom carrier and the Jetson Orin NX module.
- You might need to modify your carrier design to accommodate the new Ethernet port.
Option 3: Using Ethernet-to-USB and utilizing the SODIMM pins (57, 59, 51, 53, etc.) for USB-to-Ethernet
- Pros:
- This approach allows you to use the existing USB ports on the Jetson Orin NX module, eliminating the need for a new Ethernet port.
- You can use the SODIMM pins for USB-to-Ethernet communication, which might be more convenient than adding a new Ethernet port.
- Cons:
- You’ll need to ensure that the USB-to-Ethernet solution is compatible with your custom carrier and the Jetson Orin NX module.
- You might encounter performance limitations or increased latency compared to a dedicated Ethernet port.
Comparison and Recommendations
All three options have their pros and cons. If you’re looking for a straightforward solution, using a Realtek part (Option 2) might be the most convenient choice, as it leverages existing driver support and is widely used in the industry.
However, if you’re concerned about compatibility or want to explore alternative solutions, using Ethernet-to-USB (Option 3) could be a viable alternative. This approach allows you to utilize the existing USB ports on the Jetson Orin NX module, which might be more convenient than adding a new Ethernet port.
If you’re already invested in your current PCIe to Ethernet controller setup (Option 1), you might want to stick with it, as it’s already working for you.
In terms of EtherCAT support, you can use the SOEM library with any of the above options, as it’s a software-based solution that doesn’t rely on specific hardware.
Ultimately, the choice depends on your specific requirements, design constraints, and preferences. I recommend evaluating each option carefully and considering factors like compatibility, performance, and cost before making a decision.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Is this still an issue to support? Any result can be shared?
I still do not know if my proposed solution will work.
Presently, I have a Microchip LAN7430T-I/Y9X installed going from RJ-45 to Jetson PCIE1 port pins on Jetson Orin NX (pins 169, 167, etcetera).
I would welcome any supporting information on this.
Since you are using PCIe #1 already with a x1 device, you could have a second instance of the same device on the PCIe #2 lane 0 or 1 for another x1 interface (Option #2 in Table 7-4 of the Jetson Orin NX Series and Orin Nano Series Design Guide).
