OSEKturbo for hcs12 kernel awareness

cancel
Showing results for 
Search instead for 
Did you mean: 

OSEKturbo for hcs12 kernel awareness

Jump to solution
2,673 Views
Contributor I
Hi all,
Does anyone know how to active the CodeWarrior (for hcs12) debugger OSEKturbo kernel awareness?
I don't know exactly what to do with my application generated ORTI file (cfg.ort).
Thanks,
Javier
Labels (1)
Tags (1)
0 Kudos
1 Solution
22 Views
Specialist III

Hello

As far as I know you need to have the .ort file (containing description of the application according to ORTI standard) located at the same location as your executable (.abs) file.

Also the  need to use the same base name for your executable file and the corresponding .ort file.

For example if your executable is called MyAppli.abs, the ORTI file must be called MyAppli.ort and must be located in the same directory on the disk.

If this does not help, you will have to submit a service request on the web around that.

CrasyCat

View solution in original post

0 Kudos
4 Replies
22 Views
Contributor I

yep...the file renaming did the trick!

Thanks a lot CrasyCat

Javier

0 Kudos
22 Views
Contributor I

Thanks CrasyCat for your promtly reply.

I know that about the OSEK inspector and its RTK tree, the problem I have is that no object appear under the RTK tree when I load the application.
It´s obviuos that when I load my application the debugger is completely unable to gather information about the OSEK objects because it doesn´t know that the code being loaded was actually linked with the OSEK library, so is there a way to let it know that it is an OSEK application?
How automatic is that "Kernel awareness" and how does it work?
According to what I know, the objects information is contained in the ORTI file (in my case cfg.ort in the {project}\bin subdirectory together with the application binary) So here the questions:
How does the debugger know that it has to load that file? Can I tell it where it is, forcing in some way that "kernel awareness"? if so, how?

Thanks.

Javier

0 Kudos
23 Views
Specialist III

Hello

As far as I know you need to have the .ort file (containing description of the application according to ORTI standard) located at the same location as your executable (.abs) file.

Also the  need to use the same base name for your executable file and the corresponding .ort file.

For example if your executable is called MyAppli.abs, the ORTI file must be called MyAppli.ort and must be located in the same directory on the disk.

If this does not help, you will have to submit a service request on the web around that.

CrasyCat

View solution in original post

0 Kudos
22 Views
Specialist III

Hello

You can see OSEK objects (task, resources, stack, ...) in the Inspector component.

To open the Inspector component:
 - In the debugger select Component -> Open
 - Double click on "Inspect"

The Inspector component is opened. There is a tree called "TRK" there.
Expand it to see your OSEK objects.

Note that you need a dedicated license to see OSEK objects. If you do not have the appropriate license you will only see 4 objects in the tree and "Demo Limitation" will be written below.

I hope this helps.

CrasyCat

0 Kudos