Hello li liu,

I have a relevant thread on this https://e2e.ti.com/e2eprivate/valeo/valeo-ep-automotive/f/valeo-jacinto-forum/1199720/tda4vl-q1-emid-adc_mcal-issue-in-src_file-adc-c-os_-interrupt-disabled-issue

Please check this and if you have questions let me know.

Regards

Tarun Mukesh

sorry  The page not  found

Sorry my bad, 

SchM_Enter_Adc_ADC_EXCLUSIVE_AREA_0 and  SchM_Exit_Adc_ADC_EXCLUSIVE_AREA_0  are used to protect the accesses to the ADC driver data structures ,ensuring  one only task can access the data structures.

In mcusw/mcal_drv/mcal/Bsw_Stubs/Rte/src/SchM_Adc.c file all the CPU interrupts are disabled but ADC interrupts disabling would be suffice(which need to be takes care in BSW).

Regards

Tarun Mukesh

Hello Tarun Mukesh ，

We now use autosar to set the adc interrupt function type to ADC_ISR_CAT1, and the test program uses the test demo provided by Ti. The execution of the program will enter the errorhook, may I ask whether this is caused by the interrupt type set to CAT1?

Regards

Li Liu

Hello,

No i don't think so.I believe we have configured the same in our example, as i said above you need to develop your own BSW layer which meets the AUTOSAR ADC driver standards.

Tarun Mukesh Puvvada said:

In mcusw/mcal_drv/mcal/Bsw_Stubs/Rte/src/SchM_Adc.c file all the CPU interrupts are disabled but ADC interrupts disabling would be suffice(which need to be takes care in BSW).

Have you disabled only ADC related interrupts rather than all ?

Regards

Tarun Mukesh

Hello,

We still have the following questions to ask:
Q1,How to turn off only ADC interrupts?
Q2,The ADC is set in one shot mode, the interrupt is cat1, the interface of TI mcal is called, and only ADC_0 is enabled. When executed AdcApp_PowerAndClkSrc(); AdcApp_Startup(); AdcApp_PlatformInit(); AdcApp_Test(); After these functions, the ADC_0 interrupt is triggered to call the callback function, but after the callback is completed, other interrupts entering the ADC result in entering OS_Hal_Corefreeze(). Why is that?

Regards

Li Liu