Q1, if you cannot get those kernel messages which might mean you didn’t connect 2 P3710s correctly. Could you describe how you connect your P3710s? What cable are you using ? Where did you get the miniSAS cable? Thanks.
Q2. If you are sure about your connection is correct. Then please try to update the retimer FW to see if that works.
Q4. Please make sure 2 P3710s connect correctly first, then set up those commands again.
We didn’t hit your issue before.
According to your reply, the kernel messages didn’t show any information when EP was connected to RP which means your HWs didn’t connect two P3710 correctly.
Please help to check the following items:
Could you please help to check your bind command?
( The board name should be based on your devices)
./bind_partitions -b p3710-10-a01-f1 linux -s 1
./bind_partitions -b p3710-10-a01-f1 linux -s 2
Please help to check your mini-SAS cable:
If you are sure about you connect two P3710s correctly through mini-SAS cable, you may need to check if your mini-SAS cable is functional and in good condition. (We have no way to check your cable, you might need to do it on your own).
One thing I can think of is to check your P3710 each by each. If you can confirm your cable is good, then plug the cable from port-A to port-B on the same P3710.
3-a, try to rebind (drop the option “-s 1” or “-s 2” at binding) & flash the image.
3-b, insert kernel modules at on same P3710:
sudo modprobe nvscic2c-pcie-epc
sudo modprobe nvscic2c-pcie-epf
3-c, execute the rest commands as your test before as below to check it again.
echo 0x10DE > functions/nvscic2c_epf_22CC/func/vendorid
echo 0x22CC > functions/nvscic2c_epf_22CC/func/deviceid
ln -s functions/nvscic2c_epf_22CC/func controllers/141c0000.pcie_ep
echo 0 > controllers/141c0000.pcie_ep/start
echo 1 > controllers/141c0000.pcie_ep/start
3-d, it this P3710 is not working then check another P3710. By doing this, we should be able to know if one of them is broken. Two P3710s are broken at the same time doesn’t make sense to me.
Do you have the pdk 220.127.116.11 ?
If yes, then try to go the the following folder (previous command needs to be corrected as below)
(If you use SDK manager to download the image, the path should be DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/make)
By any chance, do I need to run the bind command on the host PC??
I think the answer is YES.
Also, why do I need to re-flash?
Can I use SDKManager for re-flushing?
I think the default image on P3710 didn’t set the correct soc_id by default.
Furthermore, If I remember correctly, the SDK manager doesn’t support option “-s”.
As per your instructions, I connected the mini SAS cable to ports A and B of the same P3710 and checked, but unfortunately the kernel message(dmesg) was not output.
I checked it on other P3710 and the results were the same on both.
I also prepared and checked another brand new mini SAS cable and unfortunately the results were unchanged.
Please provide information on the mini SAS cable you used.
If there is anything else I should check, please let me know.
The cable used on the devkit follows the Open Compute Facebook version of the Mini-SAS spec. Standard Mini-SAS cable would not work as it does not carry some of the sideband signals. Here are the cables from Amphenol which are compatible with the Orin devkit.
CABLE Assy miniSAS-HD x4 GEN4 500MM Black Male 0° PCI Express to Male 0° PCI Express wire 100ohm UL VW-1
CABLE Assy miniSAS-HD x4 GEN4 1000MM Black Male 0° PCI Express to Male 0° PCI Express wire 100ohm UL VW-1
CABLE Assy miniSAS-HD x4 GEN4 3000MM Black Male 0° PCI Express to Male 0° PCI Express wire 100ohm UL VW-1
This cable was designed for the devkit so it may not be advertised as a standard cable on their website. You should reach out to their local Amphenol contact directly to inquire and purchase the cable. Thanks.