topic Re: Autosar_os runs for a while and then stops. What happened in MPC5xxx

Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 15 Mar 2021 05:41:09 GMT

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

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 15 Mar 2021 05:50:19 GMT

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

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 15 Mar 2021 07:22:31 GMT

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

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Mon, 15 Mar 2021 09:09:07 GMT

Hello,

Has your added task (OsTaskA, OsTaskB) are executed during runtime? Could you provide the SW call stack before entering Os_Shutdown?

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 15 Mar 2021 09:28:48 GMT

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

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Mon, 15 Mar 2021 11:02:44 GMT

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()?

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Tue, 16 Mar 2021 01:37:24 GMT

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,

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Tue, 16 Mar 2021 07:45:07 GMT

You are right, OSShutdownos is called in the OSCheckStack function

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Tue, 16 Mar 2021 11:03:21 GMT

The call of Os_Shutdown indicates that your application has run into a critical error, and OS needs to shutdown. Please check whether you have done incorrectly with the code/configuration.

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Tue, 16 Mar 2021 13:56:04 GMT

The code in the project looks like this, task A does reverse task B does nothing, right

The attachment is my EB configuration OS project. Could you please help me to see the reason? Thank you

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Wed, 17 Mar 2021 09:39:03 GMT

Or can you configure a simple extended task routine on EB? There are always errors in the configuration on EB just now.
The file configuration has been compiled, and there is no right or wrong mark
Thank you very much

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Fri, 19 Mar 2021 10:25:13 GMT

For scheduling a routine task you can do it by add this task to schedule table (like TASKCNT in the sample application) and specify the expire point:

I would recommend to implement just a simple process for a task, maybe a counter increase, instead of integrating MCAL configuration into it.

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 22 Mar 2021 06:17:03 GMT

I have configured EB and project according to your general idea of configuring and adding tasks. However, it was entered once in TASK C, and never entered into my project in the future. Why is there any problem?
The task is the same, keep entering, change the pin of the mpc5748g thank you

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Mon, 22 Mar 2021 06:45:26 GMT

I see in your project:

- OsScheduleTableExpiryPoint3 is setup every 7500 ticks based on the counter of the Schedule Table:

- TaskCnt is setup in this expired point, so it should be called every 7500 ticks

- The OsAlarm_C is setting up incorrectly:

It's because Os_AlarmC is assigned to both TRUSTED_APP and TASK_APP, and only one application should be chosen:

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Mon, 22 Mar 2021 07:00:06 GMT

Sorry, the error is that the project was not saved well. Now upload it again

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Mon, 22 Mar 2021 12:00:31 GMT

In the project, Task_C hasn't been added in Schedule Table/ activate in any alarm. I only see the OSCnt. Are you referring to the OSCnt?

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Tue, 23 Mar 2021 01:17:02 GMT

Add task C to the project to activate the alarm, as shown in the figure.
The way you want to achieve this is to extend the activation event waiting for task C to trigger.
Now write the code, can use OsAlarm_C to activate.

But what you said about activation in the schedule table, I have added EB successfully and always got an error in configuration.
Extended task that activate the activated by scheduling table? In the scheduling OsScheduleTableExpiryPoint.

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Tue, 23 Mar 2021 02:37:17 GMT

Which error you're getting with? Please describe your expectation also. I'm completely lost about what you're saying.

Re: Autosar_os runs for a while and then stops. What happened

lubo_NEW — Tue, 23 Mar 2021 03:05:36 GMT

My final goal is to create an extended task C with the code "Status = WaitEvent(osEvent_c)" in the task;
Wait for an event to occur to activate task C. Simulation will find that it can enter task C at startup,
and then it will hang forever.I don't enter task C anymore,
and then I find that the previous code was incorrectly written as "Status = WaitEvent(OSTASK_C)", so the task hangs forever
.
Then you said that an extended task requires a schedule table or an event to be activated.
I understand event activation, but I don't understand schedule activation

Re: Autosar_os runs for a while and then stops. What happened

namnguyenviet — Tue, 23 Mar 2021 03:18:23 GMT

Task activation by schedule table is like how you do with the TaskCnt. Is there any problem with TaskCnt function call?