SNOAA89 December   2022 AM2431 , AM2432 , AM2434

 

  1.   Abstract
  2.   Trademarks
  3. 1Introduction
  4. 2Implementation
    1. 2.1 FSI TX module
    2. 2.2 FSI RX Module
    3. 2.3 Verification
  5. 3Summary
  6. 4References

FSI RX Module

Use the following example in the FSI RX module to setup and run FSI from Arm with interrupt:

fsi_loopback_interrupt (ti.com)

The receiving flag is sent to the PRU_INTC module by an external event when the FSI RX buffer is written.

Use the interrupt controller (INTC), data processing accelerator (task manager) and data movement accelerator (XFR2VBUS) on PRU for the receive path.

Figure 2-3 shows the design process of the FSI RX module.

GUID-20221129-SS0I-BVF4-CDRZ-FX9TGH2KMGQZ-low.jpg Figure 2-3 FSI RX Module Design Process

Figure 2-4 shows the specific steps for the external event trigger INTC and hit task manager.

GUID-20221129-SS0I-1D2R-6JG8-MCK5HSLMVGVN-low.jpg Figure 2-4 INTC_TASK Manager Configuration Programming
Note: Make sure the event raw status bit is SET then the interrupt generates after INTC and Task Manager configuration is done.

The specific steps for system interrupt generate are as follows and the FSI receive data path is shown in Figure 2-5.

  • Generate System Events (pulse) and mapping to R31
  • Internal event 16 to 19 maps to host 2–5 (channel 2–5) which exported from PRU_ICSSG and mapped to device level-interrupt controllers
  • PRU Interrupt requests to Arm
HOST 2 (Level) → R5FSS0_Core0_INTR_IN_122
…
HOST 5 (Level) → R5FSS0_Core0_INTR_IN_125
GUID-20221129-SS0I-QDVQ-HTJC-XMKNCM00SKWF-low.jpg Figure 2-5 FSI Receive Data Path