[SC58x] About software interrupts


I have a question about software interrupts on the ADSP-SC58x.

There is "Software Interrupt 1-7" in the interrupt list in Table 7-3 on page 250 of SC58x-2158x-hrm.pdf.

There is also a TRU software interrupt in the "Trigger List Masters" in Table 8-3 on page 357.

Are these SEC and TRU software interrupts the same?

Could you tell us about the relationship?

Best regards.

  • Hi,

    Could anyone please reply?

    Please let me know if you have any questions about my question.

    Best regards.

  • 0
    •  Analog Employees 
    on Nov 1, 2021 1:24 PM in reply to tatsuya_sato


    Regarding, "Are these SEC and TRU software interrupts the same?"

    >> Please note that SEC and TRU interrupts are different.

    The SEC supports the following features:

    • Comprehensive system event source management including interrupt enable, fault enable, priority, core mapping, and source grouping.
    • Fault management including fault action configuration, timeout, external indication, and system reset.
    • Determinism where all system events have the same propagation delay and provide unique identification of a specific system event source.
    • Distributed programming model where each system event source control and all status fields are independent of all others.
    • Slave control port which provides access to all SEC registers for configuration, status, and interrupt or fault service model.
    • Global locking supports a register level protection model to prevent writes to “locked” registers.

    The TRU supports the following features:

    • Automatically triggering the start of a DMA sequence after a sequence from another DMA channel completes. Once a DMA channel completes data transfer, it can act as a Trigger Master and signal an internal trigger pulse to the programmed Trigger Slave which can also be another DMA channel. The Slave Trigger connected to the DMA channel kicks off the DMA transfer automatically. None of this requires core intervention once the initialization is done.
    • Software triggers. The best use of triggers is to minimize core intervention. It is also possible to initiate a trigger pulse to a Trigger Slave, in the software.
    • Synchronization of concurrent activities. A single Trigger Master can initiate a trigger pulse to multiple Trigger Slaves so that several system level activities can be synchronized on an internally or externally generated event.
    • Configuration protection through register-level lock bits and global lock indication

    Anand Selvaraj.