| [pok-devel] POK installation problem |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/pok-devel Archives
]
Hello,
I am currently installing POK on my system and I followed the first installation
steps from the POK User Guide (Chapter 3), which led me to the
"./examples/partitions-threads/" directory.
However, when I reach the step where I need to launch POK on QEMU using the
command "make -C generated-code run", I receive the following message:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Booting 'PolyORB Kernel'
root (hd0, 0)
Filesystem type is fat, partition type 0x6
kernel /pok.elf
[Multiboot-elf, <0xff000:0xb4:0x0>
Error 28: Selected item cannot fit into memory
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I wondered if this was a common problem among POK beginners?
Do you have any clue?
I am using running a Ubuntu distribution with kernel 3.0.7 patched with
PREEMPT-RT patch from Ingo Molnar (version rt20).
I got the following outputs from the "make configure" command:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
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 ... yes
Architecture x86 was configured
checking for OBJCOPY for ppc architecture ... yes
checking for CC for ppc architecture ... yes
checking for CC Ada support for ppc architecture ... yes
checking for OBJDUMP for ppc architecture ... yes
checking for LD for ppc architecture ... yes
checking for QEMU for ppc architecture ... yes
checking for RANLIB for ppc architecture ... yes
checking for AR for ppc architecture ... yes
Architecture ppc was 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
checking system ... ok
Ocarina version and revision are good
DONE !
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
And the following from the "make" command:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
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
Backends: warning : cpu already exists
Backends: warning : kernel already exists
Backends: warning : part1 already exists
Backends: warning : part2 already exists
Backends: warning : generated-code already exists
Compile node cpu (generated-code/cpu)
activity.c: In function ?thr1_job?:
activity.c:19:3: attention : implicit declaration of function
?user_thread_starting? [-Wimplicit-function-declaration]
activity.c:18:13: attention : unused variable ?ret? [-Wunused-variable]
activity.c: In function ?thr2_job?:
activity.c:18:13: attention : unused variable ?ret? [-Wunused-variable]
4+0 enregistrements lus
4+0 enregistrements écrits
4 octets (4 B) copiés, 5,5594e-05 s, 72,0 kB/s
4+0 enregistrements lus
4+0 enregistrements écrits
4 octets (4 B) copiés, 5,0425e-05 s, 79,3 kB/s
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Thank you very much for your time!
Julien Savard
Computer engineering
Ecole Polytechnique de Montreal