[okl4-developer] [okl4-developer ] Problem with the configuration of a shared memory segment....

Hugues Balp hugues.balp at thalesgroup.com
Wed Dec 10 03:49:01 EST 2008


                               Dear all,

just a first word to say that I have solved the compilations problems of 
my preceding post.

Now I wonder how to configure correctly a shared memory segment.

In order to better understand the cross-cell-demo example, I have cloned 
and renamed the

example "decrypt" into "mydecrypt" in the okl4_3.0/examples repository.

In order to enable the build of this copy example, I have also edited 
the file okl4_3.0/projects/examples/SConstruct.

A patch of okl4_3.0.tar.gz including the resulting modifications is 
joined to this mail.

The build command I use to compile the test is the following:

./tools/build.py machine=versatile project=examples pyfreeze=false 
EXAMPLE=oklinux,mydecrypt LINUX_APPS=cross-cell-demo kdb_serial=True 
TOOLCHAIN=gnu_arm_eabi_toolchain pistachio.TOOLCHAIN=gnu_arm_toolchain

The system boot properly but the following assertion is raised when I 
run the executable "cross-cell-demo":

    Assertion failed: shmem != NULL, function cross_cell_open, file
    
/home/hugues/tools/okl4/okl4_3.0/linux/kernel-2.6.24-v2/arch/l4/drivers/cross_cell_demo.c, 
line 102.

The related source code is:

    shmem = okl4_env_get_segment("MAIN_SHMEM");
    assert(shmem != NULL);

This problem occurs only when I use the "mydecrypt" example and not when 
I use the original one.

So I suppose that the SHMEM segment is well configured when I use the 
"decrypt" example and not when

I use its copy, but I wonder why. There is some kind of  hidden 
dependency that I don't understand....

When I search for the strings  "MAIN_SHMEM" and "SHMEM" I just see them 
in SConscript files

or in source code within a call like "okl4_env_get_segment()"....

The only differences in the file weaver.xml are the name of the 
directory used for the shmem ( decrypt on one

side and mydecrypt on the other )....

 I would appreciate any help on this subject.

        Best regards,

                    Hugues Balp.
      





-------------- next part --------------
A non-text attachment was scrubbed...
Name: mydecrypt_okl4_3.0.patch
Type: text/x-patch
Size: 4328 bytes
Desc: not available
Url : http://lists.okl4.org/pipermail/developer/attachments/20081209/be323c8e/attachment.bin 


More information about the Developer mailing list