Commit 04fef307 authored by Christian Dietrich's avatar Christian Dietrich

coptermock: fix timing for osek-v

The maxallowedvalue of the watchdog timer was too small for the actual
usage of the timer. This regression was introduced in 243a06f0. So it
has no influence of already published research, since it only appears in
the osek-v branch.

Change-Id: I074d5b757e03bf8632e838a9f5cbd9e25ba2182e
parent 43b261bd
......@@ -129,7 +129,7 @@ TASK(CopterControlTask) {
if (round < 5) {
CancelAlarm(CopterControlWatchdogAlarm);
test_trace(0x94);
SetRelAlarm(CopterControlWatchdogAlarm, 100, 100);
SetRelAlarm(CopterControlWatchdogAlarm, 110, 100);
}
test_trace(0x95);
......@@ -137,9 +137,14 @@ TASK(CopterControlTask) {
}
ISR2(MavlinkRecvHandler) {
#ifndef CONFIG_ARCH_OSEK_V
test_trace(0xA1);
#endif
ActivateTask(CopterControlTask);
#ifndef CONFIG_ARCH_OSEK_V
test_trace(0xA2);
#endif
}
TASK(CopterControlWatchdogTask) {
......
......@@ -164,7 +164,7 @@ CPU CopterMock {
};
COUNTER C100 {
MAXALLOWEDVALUE = 20;
MAXALLOWEDVALUE = 1000;
TICKSPERBASE = 10;
MINCYCLE = 1;
};
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment