Hardware Used:
Seeed reComputer industrial J4012 (Custom Carrier Board + Orin NX 16GB)
Issue Description:
During testing of a customer’s device, the following problem was observed:
In JP5.1.1, when eth0 is connected to an IP camera, there is intermittent disconnection of the network port, making it impossible to ping the IP address and use it normally. The same issue occurs when connected to a switch.
As shown in the video
Then we conducted cross-experiments using both the customer’s device and our own device (with the same carrier board + Orin NX) as follows:
①With the problematic carrier board sent by the customer, running the JP5 system on our core board and SSD reproduced the issue. However, after flashing the core board and SSD to Jetpack 6 and testing for an afternoon, the problem no longer occurred, and the IP camera started working normally.
②When the customer’s machine, after removing the core board and SSD, was installed on our own carrier board, the issue was easily reproducible. After flashing this core board and SSD to Jetpack 6 and testing for an afternoon, the problem did not recur, and the IP camera could function normally.
③With the customer’s machine, after flashing the core board and SSD to JP5, the issue has not recurred, and the IP camera is functioning normally. (This suggests that this issue might be probabilistic in nature.)
Given the similarity of our situation to the one mentioned in the link, we tentatively conclude that there may be a probabilistic issue with ETH0 connectivity on JP5:
Link to similar issue: L4T R35.2.1 Ethernet (eth0) not working - Xavier NX
Through the aforementioned cross-validation, we can confirm that there are no hardware issues with the custom carrier board; furthermore, we have successfully tested and verified on the new JP5. We are deeply puzzled by this situation and can only recommend customers to use JP6 for now.
Any advice you can provide would be greatly appreciated!