Autosar_os runs for a while and then stops. What happened

[lubo_NEW]

Following the reference example, in the sample example of AUTOSAR_OS,
a task was added that required the LED light to be reversed once per second
The configuration of EB is shown in the figure
The configuration of EB is shown in the figure,
following the example of TASK1 given by LAB2

[lubo_NEW]

You are right, OSShutdownos is called in the OSCheckStack function

[lubo_NEW]

I'm just going to add task A, task B doesn't write anything
At first the task should be able to run, and after a while it should enter the OS_SHUTDOWN functionThe stop task scheduling in shielding stop task can be run all the time

[namnguyenviet]

So it means task A can work correctly by commenting out the StopScheduleTable? That would not make sense cause after this, TerminateTask() is called. 

Is there any SW stack perform which function has called TASKSTOP()?

[lubo_NEW]

Thanks for your reply, I did not define the switch stack as the TASKSTOP function.
This is the sample project of the official MPC574xG_AUTOSAR_OS_4_0_92_RTM_1_0_3 routine
I did not make any changes, except to configure more TaskA and TaskB in the EB configuration, and to add controlled LED inversion tests.
No other changes are being made,

[lubo_NEW]

The code for the task is as follows, and it stops shortly after it runs

The simulation stopped at the task close function as shown in the figure

What is the reason for this

[lubo_NEW]

When I block the sentence "stop in schedule table" in the Task (TaskStop) TASK,
I can continue running as shown in the figure.Task (TASKRCV1) can be restarted.
Task (TASKRCV1) can be restarted.

Task (TaskRcv1) is a working process, can you explain it in detail