ciaa / firmware.modules.rtos Goto Github PK

Index 84 is repeated in Interrupt sources definition for MK60F12, in Os_Internal_Arch_Cfg.c.php for cortexM4.

An AUTOSTART Alarm with 2 appmodes only declares One Appmode into the AutoStartAlarm generated array.

Example:

OIL:
` APPMODE = AppMode1;
APPMODE = AppMode2;

ALARM ActivatePeriodicTask {
COUNTER = HardwareCounter;
ACTION = ACTIVATETASK {
TASK = PeriodicTask;
}
AUTOSTART = TRUE {
APPMODE = AppMode1;
APPMODE = AppMode2;
ALARMTIME = 0;
CYCLETIME = 100;
}
}`

generates (into os_internal_cfg.c):

const AutoStartAlarmType AutoStartAlarm[ALARM_AUTOSTART_COUNT] = { { AppMode1, /* Application Mode */ ActivatePeriodicTask2, /* Alarms */ 0, /* Alarm Time */ 200 /* Alarm Time */ } };

so this portion of StartOS:

for ( loopi = 0; loopi < ALARM_AUTOSTART_COUNT; loopi++ ) { if ( AutoStartAlarm[loopi].Mode == Mode ) { ( void )SetRelAlarm( AutoStartAlarm[loopi].Alarm, AutoStartAlarm[loopi].AlarmTime, AutoStartAlarm[loopi].AlarmCycleTime ); } }

will never start the alarm, for the second AppMode.

The file https://github.com/ciaa/firmware.modules.rtos/blob/master/tst/ctest/etc/ctest_tm_01.oil has 2 tasks with 2560 bytes each, against the rest of the test cases, where they have 256.

https://github.com/ciaa/firmware.modules.rtos/blob/master/generator/tests/ftest/fixtures/gen/src/cortexM4/Os_Internal_Arch_Cfg.c.php#L216

and

https://github.com/ciaa/firmware.modules.rtos/blob/master/gen/src/cortexM4/Os_Internal_Arch_Cfg.c.php#L222

has different indexes for the irq handler definitions.

The implementation of the FreeOSEK do not support the usage of resources within ISR CAT2 handlers.

GetResource / ReleaseResoulce only takes into account Task Level execution.

In order to refactor and complete the OIL parser add unit testing

The TICKSPERBASE attribute specifies the number of ticks required to reach a counter-specific unit. The interpretation is implementation-specific.
(OIL: OSEK Implementation Language Version 2.5. 3.2.5.2)