MPC5xx: CodeWarrior Debug: OSEK Tasks State is "*invalid expression*"

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

MPC5xx: CodeWarrior Debug: OSEK Tasks State is "*invalid expression*"

1,719 Views
ThomasKintzel
Contributor I
Hello!

I'm using
CodeWarrior 8.1
OSEK 2.2.1
MPC563

I debug my application and want to watch the OSEK Tasks objects

In that window the debugger displays in the columns "Task State" and "Wait Events" the text *invalid expression* (see attached pic).

I do something wrong. But what? Can anybody help me to see correct values?

Thank you

regards
Thomas

Message Edited by CrasyCat on 2007-04-13 02:28 PM

Labels (1)
0 Kudos
3 Replies

451 Views
J2MEJediMaster
Specialist I
Again, keep in mind that basic OSEK tasks--of which you've got quite a number--are either running or not. Put another way, their context exists only while their code executes, and it utterly disappears when the task terminates. The task context is only preserved for extended tasks. Unless you've hacked at the OSEK source code files (those in the ..\osts12\src\ directory), things should be functioning as they should.

---Tom
0 Kudos

451 Views
J2MEJediMaster
Specialist I
Is this a screen shot before OSEK runs? The task state variables might be filled with random numbers that fall outside of the range of what's considered a valid task state. Hence the "invalid expression" result. The same explanation applies to those event variables. As OSEK runs and tasks start and stop, valid values should start to appear. Note that task states are only valid for extended tasks.

---Tom
0 Kudos

451 Views
ThomasKintzel
Contributor I
Tom, thanks for your reply
 
>> Is this a screen shot before OSEK runs?
 
No, the application was started. I have set a breakpoint in one of the extended tasks.
 
This is my very beginning of that project and with OSEK in general. Some of the tasks consists only of a TerminateTask() so that they are already terminated at this time. Maybe this is a problem?
 
Thomas
 
 
0 Kudos