[EXT_EP-11265] Inside Can_IntISR_Function API, SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0 is called twice which is affecting interrupt handling behviour Created: 20/Jul/23  Updated: 20/Jul/23  Resolved: 20/Jul/23

Status: Fixed
Project: Embedded Software & Tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: TI User Assignee: TI User
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Product: MCAL
Internal ID: MCAL-10744
Forum URL: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210614/inside-can_intisr_function-api-schm_enter_can_can_exclusive_area_0-is-called-twice-which-is-affecting-interrupt-handling-behviour?tisearch=e2e-sitesearch&keymatch=SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0#
Found In Release: MCUSW_J7_03.00.00
Fix In Release: MCUSW_J7_09.00.00
Affected Platform/Device: j7200-evm
j721e-evm

 Description   

Hello Team,

In Can_Irq.c,

  
         SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0();
        Can_IntISR_Fun(CanInstanceID);
        SchM_Exit_Can_CAN_EXCLUSIVE_AREA_0();

Entering Exclusive area in IRQ handling is creating interrupt handling problems to the customer.The similar bug was earlier fixed but on modifications in driver source code the bug got reverted .

Please refer https://jira.itg.ti.com/browse/MCAL-5405

Current E2E
------------------

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210614/inside-can_intisr_function-api-schm_enter_can_can_exclusive_area_0-is-called-twice-which-is-affecting-interrupt-handling-behviour?tisearch=e2e-sitesearch&keymatch=SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0#

Older E2E
---------------

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1042307/exclusive-area-should-not-be-used-inside-irq-handling-for-ti-processor-sdk-rtos-j721e-evm-07_03_00_07?tisearch=e2e-sitesearch&keymatch=SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0#

Kindly request to fix this.

Regards
Tarun Mukesh


Generated at Mon Apr 14 05:43:09 CDT 2025 using Jira 9.12.17#9120017-sha1:aba4002bcd633f188b6a4bb5dd8a0e1f20b79ee4.