[pok] Trouble executing a first POK example?

Hello,

I am just getting started with POK and Ocarina. Using Ocarina 2.0 I have been able to build some simple examples that run on the Linux system. Is there an ocarina mailing list for questions about how to use the tool?

So now I am attempting to build and execute POK examples. I have attempted to run the partitions-threads example on two different versions of POK one from Dec. 5 2011 and one from Feb. 2, 2011. Here is what I am doing:

First to show you what I am running on:

>> uname -a

>> Linux dogmatix.jpl.nasa.gov 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

Next I go to the POK install and execute:

dogmatix:/home/reder/src/pok-20111205$gmake configure

checking for ECHO... yes

checking for MV... yes

checking for GZIP... yes

checking for MKDIR... yes

checking for GREP.... yes

checking for PERL... yes

checking for COPY... yes

checking for KILL... yes

checking for CAT... yes

checking for AWK... yes

checking for CP... yes

checking for TOUCH... yes

checking for RM... yes

checking for SED... yes

checking for SLEEP... yes

checking for CC for x86 architecture ... yes

checking for CC Ada support for x86 architecture ... yes

checking for OBJDUMP for x86 architecture ... yes

checking for RANLIB for x86 architecture ... yes

checking for AR for x86 architecture ... yes

checking for OBJCOPY for x86 architecture ... yes

checking for CXX for x86 architecture ... yes

checking for LD for x86 architecture ... yes

checking for QEMU for x86 architecture ... no

Architecture x86 was NOT configured

checking for OBJCOPY for ppc architecture ... no

checking for CC for ppc architecture ... no

checking for CC Ada support for ppc architecture ... no

checking for OBJDUMP for ppc architecture ... no

checking for LD for ppc architecture ... no

checking for QEMU for ppc architecture ... yes

checking for RANLIB for ppc architecture ... no

checking for AR for ppc architecture ... no

Architecture ppc was NOT configured

checking for CC for sparc architecture ... no

checking for CC Ada support for sparc architecture ... no

checking for TSIM for sparc architecture ... no

checking for OBJDUMP for sparc architecture ... no

checking for RANLIB for sparc architecture .... no

checking for AR for sparc architecture ... no

checking for OBJCOPY for sparc architecture ... no

checking for LD for sparc architecture ... no

checking for QEMU for sparc architecture ... yes

Architecture sparc was NOT configured

No architecture was configured, will exiting.

checking system ... ok

Ocarina version and revision are good

DONE !

Next in the partition-thread example I attempt to build it:

dogmatix:/home/reder/src/pok-20111205/examples/partitions-threads$gmake

Check Biba security policy............................................ validated

Check that AADL model contain memory components........................ NOT validated

Your model does not contain any memory component. It means that y

ou didn't specify the memory requirements of your partitions and

thus, have not set partition memory settings.

Check Bell-Lapadula security policy................................... validated

Check Major Time Frame compliance..................................... validated

Check compliance of Health Monitoring service for modules............. NOT validated

You must define ARINC653::HM_Errors and ARINC653::HM_Actions on A

ADL processor components to specify the health monitoring policy.

If you did it, some values are not allowed on processors

Check for transient errors between partitions......................... validated

Check Partitions Memory requirements................................... NOT validated

Specified memory requirements are not correct. The size of partit

ion memory is wrong regarding the requirements of its tasks (Sour

ce_Code_Size property and so on)

Check that each virtual bus provides protection mechanisms............ validated

Check that partitions declare their criticality level................. NOT validated

You didn't associate a Criticality in your partitions. You must d

efine the property ARINC653::Criticality or POK::Criticality_Leve

l with your virtual processor component

Check error coverage................................................... NOT validated

Some errors are not recovered during the execution of your system

. A thread, a processor or a virtual processor may miss to catch

an error while the system is executing

Check that virtual processors contain virtual buses................... NOT validated

Virtual processors (partitions runtime) must provide information

about their security levels. Your virtual processors should provi

de this information through the Provided_Virtual_Bus_Class proper

ty. In addition, virtual buses must declare their security levels

with the POK::Security_Level property.

Check that each partition is executed at least one time by the module. NOT validated

Check that each virtual processor of each processor is listed in

the partitions slots allocation.

Check that partition component share the same memory level............. validated

Check that each virtual bus with a different security level has a different cipher key validated

Check Threads Memory requirements..................................... validated

Check that connections support appropriate security levels (MILS)..... validated

Check for permanent errors between partitions......................... validated

Check compliance of Health Monitoring service for partitions.......... NOT validated

You must define ARINC653::HM_Errors and ARINC653::HM_Actions on A

ADL virtual processor components to specify the health monitoring

policy of your partitions. If you did it, some values are not al

lowed on virtual processors

Check compliance of Health Monitoring service for partitions processes NOT validated

You must define ARINC653::HM_Errors and ARINC653::HM_Actions on A

ADL threads components to specify the health monitoring policy. I

f you did it, some values are not allowed on threads

Check that buses provides virtual buses............................... validated

Will execute ocarina -aadlv2 -f -g pok_c model.aadl $POK_PATH/misc/aadl-library.aadl

Backends: warning : generated-code already exists

Compile node cpu (generated-code/cpu)

activity.c: In function ‘thr1_job’:

activity.c:19: warning: implicit declaration of function ‘user_thread_starting’

activity.c:18: warning: unused variable ‘ret’

activity.c: In function ‘thr2_job’:

activity.c:18: warning: unused variable ‘ret’

Finally to run the example I execute:

dogmatix:/home/reder/src/pok-20111205/examples/partitions-threads$gmake -C generated-code run

gmake: Entering directory `/home/reder/src/pok-20111205/examples/partitions-threads/generated-code'

gmake -C cpu run&

gmake: Leaving directory `/home/reder/src/pok-20111205/examples/partitions-threads/generated-code'

dogmatix:/home/reder/src/pok-20111205/examples/partitions-threads$gmake[1]: Entering directory `/home/reder/src/pok-20111205/examples/partitions-threads/generated-code/cpu'

[QEMU] Start

/bin/sh: fda: command not found

gmake[1]: Leaving directory `/home/reder/src/pok-20111205/examples/partitions-threads/generated-code/cpu'

So the question is it apparently needs something called fda to run. What is that and how can I install it.

Also is there a simple way to turn of the colored text output from your makefiles and scripts since sometimes it is very are hard to see.

Finally, does POK include any sort of shell that I can run to more conventionally execute demonstration codes?

Has anyone run POK on a PPC750 PCI Board?

Thanks for any responses to this message,

Len

-----------------------------------------

Leonard J. Reder

Jet Propulsion Laboratory

Flight Software Applications

Email: reder@xxxxxxxxxxxx

Phone: 818-354-3639

-----------------------------------------