Please provide the following info (tick the boxes after creating this topic):
DRIVE OS 220.127.116.11
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
SDK Manager Version
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
It is documented in Network Configuration | NVIDIA Docs that port roles for Switch 2 (88Q6113) are set to “secondary” but it is expected for various sensors/Lidars for the switch ports to be in Primary role.
Could you share/provide a way to configure/update the roles from Secondary to Primary?
Some additional context on discussing port configuration are Network Switches Port Roles Appear Incorrect - #16 by dharmateja.kadem .
Currently, the capability to configure or modify the port roles is not supported. Could you please provide more insights or practical use cases that necessitate this change? As far as I’m aware, you have already made inquiries through your NVIDIA representative regarding this matter. Has this been tracked or addressed in any ongoing discussions?
VickNV, the use case is to be able to connect sensors that expect the switch to be in primary role (and is not configurable to be set otherwise). This otherwise renders these connections unusable for anything that doesn’t match the role.
Could you confirm which sensor listed as supported in the following pages fall into this category?
Please note that reconfiguring the port role might necessitate firmware rebuilding, which is not currently supported.
Vick, yes, we are looking at Luminar Iris that is listed in the Hyperion sensor list as well as the ecosystem with “Coming later” comment. It is not possible to set this LIDAR in primary mode.
As per the current information, the mentioned LiDAR is not compatible with the current release. I’d recommend choosing a LiDAR listed as compatible on those pages.
Is the reason for “not compatibility” just the lack of network port role configuration, or you see other concerns?
Would you consider checking with your team possibility to enable setting the port role - I would imagine this would be something generally useful for various or users and other use-cases to have this flexibility.
Briefly looking at Marvell switch docs for (88Q6113) and platforms build on this switch - this looks like part of their supported features.
‘Not compatible’ means the development and testing have not been finalized for use. Currently, adjusting the port role requires firmware rebuilding, which is beyond the scope of SDK and forum support.
It would be beneficial to contact your NVIDIA representative to discuss the possibility of using the upcoming LIDAR.
I’ll give it a last try on clarifying “reconfiguring the port role might necessitate firmware rebuilding” as you used wording “might” in previous message when asking for the use case. Would you able to confirm “might” as “must” before we close this topic.
Otherwise we can conclude and thank you for your time and support!
Indeed, reconfiguring the port role mandates modifying and building the firmware. I apologize for any ambiguity in my earlier response.