• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 411 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LS0914: Code runs into _dabort when running several interrupts with interrupt lock configured in MCAL

Rayna Wang
Expert 3680 points
Part Number: TMS570LS0914
Other Parts Discussed in Thread: HALCOGEN

Hi Expert,

There's an urgent customer case that their code always rush into _dabort when run several ISRs after interrupt lock enabled in MCAL.

The MCAL version is AUTOSAR_MCAL_TMS570LSx-05.40.00EA-installer.

The ISRs could be SPI2 ISR, Timer1 ISR, ICU ISR. And SPI3 slave receives the interrupts.

Could you help with the issue debugging?

Thanks!

 -Rayna

  • 0
    Prodigy 170 points

    Hi Expert,

    I am the urgent customer.

    In order to find the problem, we have tested a simple demo, transplanted MCAL (05.40.00), and added interrupt lock(SPI、Gpt), SPI2 is configured as DMA mode (IRQ), and uses timer 1 (100us) ( IRQ).


    Then use the SPI2 module to run normally. Timer 1 is used normally, but it will enter _underEntry when both are used at the same time. If change the timer 1 to 1s,  will enter _dabort.

    The interrupt lock is configured as follows:(SPI and Gpt)

    #define SchM_Enter_Spi_SPI_EXCLUSIVE_AREA_0()   _disable_interrupt_()
    #define SchM_Exit_Spi_SPI_EXCLUSIVE_AREA_0()     _enable_interrupt_()

    #define SchM_Enter_Gpt_SPI_EXCLUSIVE_AREA_0()   _disable_interrupt_()
    #define SchM_Exit_Gpt_SPI_EXCLUSIVE_AREA_0()     _enable_interrupt_()

    Note:_disable_interrupt_() and _enable_interrupt_() are the code generated by HALCoGen, in sys_core.asm

  • 0 in reply to user5792549
    TI__Prodigy 360 points

    Hello,

    Thanks for the details.

    1. The setup is using SPI2 (with DMA) and Timer-1 (100uS) with ISRs enabled. Running separately, they are fine. But using both at same time, the execution enters '_underEntry'. Please confirm if you mean undefEntry when you say '_underEntry'.

    2. The setup is using SPI2 (with DMA) and Timer-1 (1S) with ISRs enabled. Running separately, they are fine. But using both at same time, the execution enters '_dabort'.

    We need to analyse this and if possible reproduce on our setup. We will reply back once we have an update.

  • 0 in reply to Chetan Sanga
    Prodigy 170 points

    1.Yes，it is ‘_undefEntry’

    2.Hope to reply as soon as possible

    The latest phenomenon: when only timer 0 (1s) and timer 1 (100us) are used in demo, it will also enter "_undefEntry"

  • 0 in reply to user5792549
    TI__Expert 3680 points

    Hi Chetan,

    Is there any updates from you side? Do you need any other information to deal with this issue?

    Could you tell us your schedule about this case, if it's necessary to needs long time to debug?

    This case is very important and urgent for customer. Really appreciate for your help!

    Best Regards/Rayna