DRIVE OS Version: 7.0.3
Issue Description:
Platform: NVIDIA Drive AGX Thor / DRIVE OS 7.0.3
Hardware: P3584 10G Dongle, firmware 7.1.8
3584 2.7>pinfo
88Q4364: Register Reads
Reg 1.0 Val:0x2041
Reg 1.1 Val:0x2
R:0x1E300 V:0x6
Base-T1 Mode:Master
Speed:10G
Link Down
FW Version:7.1.8
candidateRevision:0x0
AQR113C: Register Reads
Reg 1E.C842 Val:0x3311
Reg 1E.C885 Val:0x74
Reg 1E.20 Val:0x506
ADC Vals:300,290
PWM val:84
Background
The P3584 10G dongle defaults to Primary mode for the 88Q4364 Base-T1 PHY after every power cycle. As documented, connecting it to the Drive AGX Thor’s Base-T1 port requires
setting it to Secondary mode via sm 0 in the UART console. This works correctly — after sm 0 (without a PHY reset via rphy), the 88Q4364 re-negotiates as Slave and the T1 link
comes up.
ref: P3960 Network Topology — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide
Problem
The dongle reverts to Primary mode on every power cycle, requiring a manual sm 0 command to restore Secondary mode. This is a blocking issue in setups where:
- The board undergoes regular power resets (not just software reboots)
- The dongle is not always connected via USB to a host machine, making serial console access unreliable (besides, it requires CDC kernel modules)
A host-side startup script is not a viable general solution for these reasons.
Questions
- Is there a way to persist the Secondary role setting to the dongle’s NVRAM or OTP so that it boots in Secondary mode by default without requiring
sm 0after every power cycle? - If not currently supported, is a firmware update planned that would expose a persistent configuration command (e.g., something like
sm 0 saveor a dedicatedsaveconfigcommand)? - Alternatively, is there an undocumented command in the current 7.1.8 firmware that writes the T1 role to non-volatile storage?
Thanks in advance for any guidance on the topic