sCheck Test CMU_FM, ISR problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

sCheck Test CMU_FM, ISR problem

5,163 Views
Marekp
Contributor I

Hi, I have an issue with the CMU_FM_1 and CMU_FM_2 tests.
The test has been configured in sCheck as a StartUp test.

Additionally, when the test starts, the CMU_FC test is executed as well.

  1. The CMU_FC test is enabled.

  2. An interrupt is installed for CMU_FC with Interrupt ID = 84.

  3. The interrupt for the CMU_FC test is triggered. The ISR(Mcu_Cmu_ClockFail_IRQHandler) from Clock_Ip_Irq.c is executed, which calls the callback function CMU_ClockFailureNotification.

  4. The CMU_FC test finishes successfully.

  5. The test for CMU_FM starts with Interrupt ID = 85.

  6. No interrupt occurs, and the microcontroller resets according to the configuration.

    "Software must ensure that CMU1 interrupt is serviced within POR_WDG timeout. In absence of CMU1 interrupt servicing, the POR_WDG detects this as an FIRC failure and initiates a POR recovery. -  Chapter 57 Clock Monitoring Unit – Frequency Meter (CMU_FM)"

    How should the interrupt for CMU_FM be handled?
    I cannot find the name of the ISR corresponding to CMU_FM_1 or CMU_FM_2 in the codebase.

     

0 Kudos
Reply
24 Replies

1,007 Views
Marekp
Contributor I

Hello  

"This is strange, didn't you modify the generated sCheck configuration file?"– No, the sCheck_Cfg.c files have not been modified.

The generated signature for the FCCU_NCF test is: 0xDF2F0000UL

For the purpose of this test, only the FCCU_NCF test is executed.

Marekp_0-1746005949316.png

 

Marekp_1-1746006116315.png

 

As an example, I enabled only the following startup tests:CMU_FC_0,CMU_FC_3,CMU_FC_4,CMU_FM_1,CMU_FM_2

The generated signature was: 0x27C00000UL
And the tests completed successfully.

Marekp_2-1746006820956.png


So, does Tresos generate incorrect cfg files for the FCCU test?

 

 

0 Kudos
Reply

1,291 Views
Marekp
Contributor I

Thank you for your guidance. The CMU_FM1 test is now working correctly in both runtime and shutdown phases.
However, I still have an issue with the CMU_FM2 test — it cannot complete during runtime and shutdown.
The interrupt associated with this test (InterruptID = 86) is being continuously triggered,
and the test cannot finish because pContext != NULL_PTR.
As a result, the watchdog cannot be refreshed and a system reset occurs.
Should CMU_FM2 perform any specific action after the test is completed?
This does not seem entirely possible, since the InstallIsr function installed sCheck_CmuFm_TestIsr as the handler,
and the interrupt continues to be triggered indefinitely.

 

could You help ?

 

 

Marekp_0-1744978382616.png

Marekp_0-1744979007408.png

Marekp_1-1744979037176.png

Marekp_2-1744979056659.png

 

 

 

 

 

0 Kudos
Reply

1,199 Views
RadoslavB
NXP Employee
NXP Employee

Hi Marek,

can you do screenshot again from sCheck General Tab to see FXOSC clk and STM clk and then screenshot from RTD how exactly is configured STM instance used by sCheck? These settings must be equal.

And please try to set breakpoint into function sCheck_CmuFm_RunTest() to this line:
pArgs->u32Signature = SCHECK_INTERNAL_ERROR;
and confirm if this line is reached.

Also screenshot how CMU_FM2 registers looks like before the test is executed.

 

Kind Regards,
Radoslav

0 Kudos
Reply

1,314 Views
Marekp
Contributor I

Parameters:

FXOSC Frequency- 2.4E7

Marekp_0-1744893059319.png

FIRC Frequency- 4.8E7

Marekp_1-1744893085456.png

 

Clock Mux0 Divider2 Frequency (AIPS_SLOW_CLK) (dynamic range) - 4.0E7

Marekp_2-1744893138437.png

 

 

0 Kudos
Reply