Linux control path for FSI_CANx_STBY control on AGX Thor

Robotics & Edge Computing Jetson Systems Jetson Thor
,
1

Hi NVIDIA team,

I am working on Jetson AGX Thor with a custom carrier board.

From the Jetson Thor Developer Kit Carrier Board Design Files, it appears that the CAN transceiver standby signals are connected to FSI GPIO pins, specifically FSI_GPIO00 and FSI_GPIO05. However, the pinmux spreadsheet does not appear to allow configuration of these two GPIOs.

I would like to clarify the intended usage and software control model for these pins.

My questions are:

  1. On the Thor P4071 reference carrier, are FSI_GPIO00 and FSI_GPIO05 intended to control the CAN transceiver STBY signals?
  2. If so, what is the expected software control path for these signals?
  • Linux GPIO framework / gpiochip?
  • MB1/MB2 BCT configuration?
  • FSI firmware / safety island?
  • Another BSP interface?
  1. Are FSI_GPIO00 and FSI_GPIO05 accessible for Linux-side control at all?
    If they are owned by FSI firmware or the safety island, please clarify whether Linux is expected to control them directly or whether they should be treated as unavailable from the Linux side.

Thanks.

3

Hi conan7963,

Are you using the devkit or custom board for Thor?
What’s the Jetpack version in use?

For AGX Thor devkit, CAN0/CAN1 from FSI are enabled by default.

May I know you use case and the requirement to configure the STBY singal?
In the pinmux spreadsheet, they are hidden so it means that we don’t expect customer using them.