IST

Key In-System Test (Key-IST or KIST) is provided in the NVIDIA DRIVE AGX™ Platform to achieve 90%+ coverage for Automotive Safety Integrity Level B (ASIL) certification for the chip. The IST:

• Detects faults on the chip.

• Runs Memory built-in self-tests (MBIST) and logic built-in self-tests (LBIST) in the silicon.

• KIST execution takes place during Key-ON of the drive cycle

• The MCU triggers the IST during a cold-boot, using the GPIO line IST_REQ.

When the IST controller is triggered, it takes full control of the entire SoC and executes the required tests. The controller is capable of fetching the test vectors from the eMMC and storing the results of the tests back to the eMMC without software interaction. Upon completion, the IST controller signals completion to the MCU via the IST_DONE_N GPIO.

Stage	SoC with MCU
IST Trigger	The IST is triggered by the MCU by raising a GPIO during a cold-boot. The trigger is initiated during Key-ON. Execution context: active GPIO and a cold-boot
IST Execution	If IST is enabled, during a cold-boot MB1 polls the GPIO from the MCU for IST mode. Execution context: cold-boot, Bootflow IST mode
RPL Processing and Reporting	After IST execution and a reboot to normal mode, the RPL is executed by IST_Client to validate the test results. The results are sent to the MCU. The user application on the MCU decides the further course of action. Execution context: functional mode
IST Configuration	Modifying the IST configuration parameters is performed by IST_Client based on input from MCU. The implementation uses UDP over Ethernet. Execution context: functional mode

• Software Components
• Partition Requirements
  • Orin
  • Thor
• Selecting the Platform Configuration
• Interaction Between the MCU and SoC
  • MCU and SoC Interfaces
  • MCU and SoC Interactions Flow
• TestApp Sample
  • TestApp Overview
  • TestApp Commands
  • TestApp Example Usage Flow
  • TestApp Usage Requirements
• Key-IST Usage Requirements