Hi

when i start latency, i get the error:
Xenomai: /dev/rtheap is missing
(chardev, major=10 minor=254)

dmesg | grep Xeno shows:
[Xenomai] scheduling class idle registered.
[Xenomai] scheduling class rt registered.
I-pipe: head domain Xenomai registered.
[Xenomai] Cobalt v3.0-rc4 (Exact Zero)

cat /sys/module/xenomai/parameters/state
enabled

Always looks good, ore can I check more?

I have made this:

First I read the document: Installing Xenomai 3.x, because it is my first Xeno3 
touch.

Than git clone  https://git.xenomai.org/ipipe-gch.git -b 
for-ipipe-3.18<https://git.xenomai.org/ipipe-gch.git%20-b%20for-ipipe-3.18>
Call /scripts/ipipe/genpatches
It generates the ipipe-core-3.18-arm-1.patches without any messages.

Get the vanilla 3.18 kernel
Prepare the kernel:
cd /platform-sm-arm/build-target/xenomai-"3.0-rc4" && \
                               scripts/prepare-kernel.sh --linux 
/platform-sm-arm/build-target/linux-3.18 \
                               --ipipe 
/platform-sm-arm/build-target/xenomai-"3.0-rc4"/kernel/cobalt/arch/arm/patches/ipipe-core-3.18-arm-1.patch
 \
                               --arch=arm

Make imx_v6_v7_defconfig (for the i.mx6 sabresd board)
Call kernel menuconfig and check the settings.
Make the kernel.
Make dtb for imx6q-sabresd board.

Than configure the Xenomai-lib with:

      CFLAGS="-march=armv7-a -mfpu=vfp3" \
      --host=arm-v7a-linux-gnueabi \
       --build=i686-host-linux-gnu  \
       --enable-shared \
       --with-core=cobalt \
       --enable-smp  \
       --disable-doc-install

make and install it.

Put all on the target, boot and try latency...
Xenomai: /dev/rtheap is missing

I don't know what is my mistake.

There is a message in dmesg:
=================================
[ INFO: inconsistent lock state ]
3.18.0 #1 Not tainted
---------------------------------
It is important about my problem?



With best regards,
Alexander

_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
http://www.xenomai.org/mailman/listinfo/xenomai

Reply via email to