• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6548: Interruption notification method from PRU to R5F

Tsurumoto
Genius 15354 points
Part Number: AM6548

IEP will be used to capture the external signal.

To send the interrupt signal to R5 core by this external signal, IPC mechanism from PRU to R5F should be used.

Is it correct?

Best regards,

HaTa.

  • 0
    TI__Mastermind 27355 points

    Hello HaTa,

    EDIT: I believe PRU to R5F flows through a network low-level driver instead of IPC. I will loop in the correct expert. Please mark this as unresolved.


    Regards,

  • 0
    TI__Mastermind 43296 points
    HaTa,

    The IPC queued mailbox-interrupt mechanism can only be used for communication between: MPU, PRU-ICSS1, PRU-ICSS2, and PRU-ICSS3 subsystems, see TRM - 7.1.1 Mailbox Overview.

    The external signal connected to latch pin of IEP generates interrupt to PRU INTC, see Figure 6-145. IEP Functional Block Diagram in TRM. The interrupt can be mapped to the Host Interrupts 2 through 9 from PRU_ICSSG INTC, see Figure 6-134. PRU_ICSSG Interrupt Controller Block Diagram, and then mapped to device level interrupt controllers which is VIM in R5F core, see Figure 6-17. MCU_ARMSS Block Diagram, and 6.3.3.6.1 VIM Overview.

    Regards,
    Garrett