[Xenomai-help] Regarding booting

[Xenomai-help] Regarding booting

[suresh reddy]

[-- Attachment #1: Type: text/plain, Size: 11210 bytes --]

Hi all,

my booting process getting freezed after the message

uncompressing the kernel.

the modules i moved on to the sd card are  modules.builtin , modules.order,
Module.symvers.

I used printk to display booting messages on console .

here is my printk messages

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 2.6.37.6 (root@domain.hid) (gcc version 4.3.3
(Sourcery G++ Lite 2009q1-203) ) #5 SMP PREEMPT Fri Jun 24 09:31:28 CEST
2011
[    0.000000] CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7),
cr=10c53c7f

[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction
cache
[    0.000000] Machine: OMAP4 Panda board

[    0.000000] bootconsole [earlycon0] enabled

[    0.000000] Memory policy: ECC disabled, Data cache writealloc

[    0.000000] OMAP4430 ES2.0

[    0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xe000

[    0.000000] FIXME: omap44xx_sram_init not implemented

[    0.000000] PERCPU: Embedded 9 pages/cpu @c0bc3000 s12384 r8192 d16288
u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 181760
[    0.000000] Kernel command line: ro elevator=noop vram=32M
mem=460M@0x80000000 mem=256M@0xA0000000 root=/dev/mmcblk0p2
console=ttyO2,115200n8 fixrtc earlyprintk bootm 0x80000000
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)


[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)

[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)

[    0.000000] Memory: 460MB 256MB = 716MB total


[    0.000000] Memory: 720696k/720696k available, 12488k reserved, 0K
highmem

[    0.000000] Virtual kernel memory layout:


[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)


[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)


[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)


[    0.000000]     vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)


[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)


[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)


[    0.000000]       .init : 0xc0008000 - 0xc002f000   ( 156 kB)


[    0.000000]       .text : 0xc002f000 - 0xc0514000   (5012 kB)


[    0.000000]       .data : 0xc0514000 - 0xc0546600   ( 202 kB)


[    0.000000] Preemptable hierarchical RCU implementation.


[    0.000000]  RCU-based detection of stalled CPUs is disabled.


[    0.000000]  Verbose stalled-CPUs detection is disabled.


[    0.000000] NR_IRQS:402


[    0.000000] ------------[ cut here ]------------


[    0.000000] WARNING: at
/home/balijepalli/omap4/ipipe-gch/arch/arm/mach-omap2/clockdomain.c:868
omap2_clkdm_deny_idle+0x58/0xc8()

[    0.000000] clockdomain: OMAP4 wakeup/sleep dependency support is not yet
implemented

[    0.000000] Modules linked in:


[    0.000000] Backtrace:


[    0.000000] [<c0038f3c>] (dump_backtrace+0x0/0x110) from [<c04353e8>]
(dump_stack+0x18/0x1c)

[    0.000000]  r7:c0515f40 r6:c004663c r5:c04c193b r4:00000364


[    0.000000] [<c04353d0>] (dump_stack+0x0/0x1c) from [<c005df0c>]
(warn_slowpath_common+0x54/0x6c)

[    0.000000] [<c005deb8>] (warn_slowpath_common+0x0/0x6c) from
[<c005dfc8>] (warn_slowpath_fmt+0x38/0x40)

[    0.000000]  r9:411fc092 r8:c0525540 r7:c05255a4 r6:00000060 r5:c052602c


[    0.000000] r4:c0546af4


[    0.000000] [<c005df90>] (warn_slowpath_fmt+0x0/0x40) from [<c004663c>]
(omap2_clkdm_deny_idle+0x58/0xc8)

[    0.000000]  r3:00000000 r2:c04c197f


[    0.000000] [<c00465e4>] (omap2_clkdm_deny_idle+0x0/0xc8) from
[<c00469a8>] (clkdm_init+0x140/0x17c)

[    0.000000]  r5:c05255bc r4:c052602c


[    0.000000] [<c0046868>] (clkdm_init+0x0/0x17c) from [<c000d764>]
(omap2_init_common_hw+0x20/0x9c)

[    0.000000]  r9:411fc092 r8:800252e8 r7:c0524be4 r6:c0026ad4 r5:c0546600


[    0.000000] r4:c0026ad8


[    0.000000] [<c000d744>] (omap2_init_common_hw+0x0/0x9c) from
[<c000f874>] (omap4_panda_init_irq+0x18/0x24)

[    0.000000] [<c000f85c>] (omap4_panda_init_irq+0x0/0x24) from
[<c000a9b8>] (init_IRQ+0x18/0x20)

[    0.000000] [<c000a9a0>] (init_IRQ+0x0/0x20) from [<c0008cb8>]
(start_kernel+0x178/0x2e0)

[    0.000000] [<c0008b40>] (start_kernel+0x0/0x2e0) from [<80008034>]
(0x80008034)

[    0.000000]  r5:c05467b0 r4:10c53c7d


[    0.000000] ---[ end trace 1b75b31a2719ed1c ]---


[    0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for
dpll_mpu_m2_ck.

[    0.000000] GPMC revision 6.0


[    0.000000] OMAP GPIO hardware version 0.1


[    0.000000] OMAP clockevent source: GPTIMER1 at 38400000 Hz


[    0.000000] I-pipe 1.18-03: pipeline enabled.


[    0.000000] Console: colour dummy device 80x30


[    0.000000] Calibrating delay loop... 2011.95 BogoMIPS (lpj=10059776)


[    0.000000] pid_max: default: 32768 minimum: 301


[    0.000000] Mount-cache hash table entries: 512


[    0.000000] CPU: Testing write buffer coherency: ok


[    0.000000] local timer: 504.00MHz.


[    0.000000] I-pipe, 504.000 MHz timer


[    0.000000] I-pipe, 504.000 MHz clocksource


[    0.000000] L310 cache controller enabled


[    0.000000] l2x0: 16 ways, CACHE_ID 0x410000c4, AUX_CTRL 0x0e070000,
Cache size: 1048576 B

[    0.000000] CPU1: Booted secondary processor


[    0.000000] local timer: 504.00MHz.


[    0.000000] I-pipe, 504.000 MHz timer


[    0.000000] Brought up 2 CPUs


[    0.000000] SMP: Total of 2 processors activated (4023.91 BogoMIPS).


[    0.000000] regulator: core version 0.5


[    0.000000] regulator: dummy:


[    0.000000] NET: Registered protocol family 16


[    0.000000] OMAP DMA hardware revision 0.0


[    0.013519] bio: create slab <bio-0> at 0


[    0.019714] SCSI subsystem initialized


[    0.025329] usbcore: registered new interface driver usbfs


[    0.031372] usbcore: registered new interface driver hub


[    0.037109] usbcore: registered new device driver usb


[    0.060607] i2c_omap i2c_omap.1: bus 1 rev4.0 at 400 kHz


[    0.081237] Skipping twl internal clock init and using bootloader value
(unknown osc rate)

[    0.091430] twl6030: PIH (irq 39) chaining IRQs 368..387


[    0.097930] regulator: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby


[    0.106109] regulator: VPP: 1800 <--> 2500 mV at 1900 mV normal standby


[    0.114227] regulator: VUSIM: 1200 <--> 2900 mV at 1800 mV normal standby


[    0.122070] regulator: VANA: 2100 mV normal standby


[    0.127899] regulator: VCXIO: 1800 mV normal standby


[    0.133850] regulator: VDAC: 1800 mV normal standby


[    0.139678] regulator: VUSB: 3300 mV normal standby


[    0.146026] regulator: VAUX1_6030: 1000 <--> 3000 mV at 1800 mV normal
standby

[    0.154754] regulator: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal
standby

[    0.163482] regulator: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal
standby

[    0.190612] i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz


[    0.210601] i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz


[    0.230621] i2c_omap i2c_omap.4: bus 4 rev4.0 at 400 kHz


[    0.237792] Switching to clocksource ipipe_tsc


[    0.259124] NET: Registered protocol family 2


[    0.263946] IP route cache hash table entries: 32768 (order: 5, 131072
bytes)

[    0.272094] TCP established hash table entries: 131072 (order: 8, 1048576
bytes)

[    0.281860] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)


[    0.289825] TCP: Hash tables configured (established 131072 bind 65536)
[    0.296691] TCP reno registered
[    0.300018] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.306213] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.313171] NET: Registered protocol family 1
[    0.318298] RPC: Registered udp transport module.
[    0.323242] RPC: Registered tcp transport module.
[    0.328155] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.336059] ------------[ cut here ]------------
[    0.340911] WARNING: at
/home/balijepalli/omap4/ipipe-gch/arch/arm/mach-omap2/pm.c:64
_init_omap_device+0x90/0xb0()
[    0.351715] _init_omap_device: could not find omap_hwmod for iva
[    0.357971] Modules linked in:
[    0.361206] Backtrace:
[    0.363861] [<c0038f3c>] (dump_backtrace+0x0/0x110) from [<c04353e8>]
(dump_stack+0x18/0x1c)
[    0.372619]  r7:ef82ff40 r6:c0042a6c r5:c04c0d3e r4:00000040
[    0.378540] [<c04353d0>] (dump_stack+0x0/0x1c) from [<c005df0c>]
(warn_slowpath_common+0x54/0x6c)
[    0.387756] [<c005deb8>] (warn_slowpath_common+0x0/0x6c) from
[<c005dfc8>] (warn_slowpath_fmt+0x38/0x40)
[    0.397583]  r9:00000000 r8:c000ed44 r7:c0587cd4 r6:c0546ab0 r5:c04c0dcb
[    0.404327] r4:c0025894
[    0.407196] [<c005df90>] (warn_slowpath_fmt+0x0/0x40) from [<c0042a6c>]
(_init_omap_device+0x90/0xb0)
[    0.416748]  r3:c0439ccb r2:c04c0d79
[    0.420532] [<c00429dc>] (_init_omap_device+0x0/0xb0) from [<c000ed68>]
(omap2_common_pm_init+0x24/0x88)
[    0.430358]  r6:c0524578 r5:c0587cdc r4:c0025894
[    0.435241] [<c000ed44>] (omap2_common_pm_init+0x0/0x88) from
[<c002f848>] (do_one_initcall+0xd0/0x1a4)
[    0.444976] [<c002f778>] (do_one_initcall+0x0/0x1a4) from [<c0008818>]
(kernel_init+0x158/0x220)
[    0.454101] [<c00086c0>] (kernel_init+0x0/0x220) from [<c0061940>]
(do_exit+0x0/0x6a4)
[    0.462310]  r7:00000013 r6:c0061940 r5:c00086c0 r4:00000000
[    0.468261] ---[ end trace 1b75b31a2719ed1d ]---
[    0.473297] ------------[ cut here ]------------
[    0.478149] WARNING: at
/home/balijepalli/omap4/ipipe-gch/arch/arm/mach-omap2/pm.c:64
_init_omap_device+0x90/0xb0()
[    0.488952] _init_omap_device: could not find omap_hwmod for dsp
[    0.495208] Modules linked in:
[    0.498443] Backtrace:
[    0.501037] [<c0038f3c>] (dump_backtrace+0x0/0x110) from [<c04353e8>]
(dump_stack+0x18/0x1c)
[    0.509796]  r7:ef82ff40 r6:c0042a6c r5:c04c0d3e r4:00000040
[    0.515716] [<c04353d0>] (dump_stack+0x0/0x1c) from [<c005df0c>]
(warn_slowpath_common+0x54/0x6c)
[    0.524932] [<c005deb8>] (warn_slowpath_common+0x0/0x6c) from
[<c005dfc8>] (warn_slowpath_fmt+0x38/0x40)
[    0.534790]  r9:00000000 r8:c000ed44 r7:c0587cd4 r6:c0546ab8 r5:c04be780
[    0.541503] r4:c0025894
[    0.544372] [<c005df90>] (warn_slowpath_fmt+0x0/0x40) from [<c0042a6c>]
(_init_omap_device+0x90/0xb0)
[    0.553924]  r3:c0439ccb r2:c04c0d79
[    0.557708] [<c00429dc>] (_init_omap_device+0x0/0xb0) from [<c000ed9c>]
(omap2_common_pm_init+0x58/0x88)
[    0.567535]  r6:c0524578 r5:c0587cdc r4:c0025894
[    0.572387] [<c000ed44>] (omap2_common_pm_init+0x0/0x88) from
[<c002f848>] (do_one_initcall+0xd0/0x1a4)
[    0.582122] [<c002f778>] (do_one_initcall+0x0/0x1a4) from [<c0008818>]
(kernel_init+0x158/0x220)
[    0.591247] [<c00086c0>] (kernel_init+0x0/0x220) from [<c0061940>]
(do_exit+0x0/0x6a4)
[    0.599487]  r7:00000013 r6:c0061940 r5:c00086c0 r4:00000000
[    0.605407] ---[ end trace 1b75b31a2719ed1e ]---
[    0.611175] I-pipe: Domain Xenomai registered.
[    0.615875] Xenomai: hal/arm started.
[    0.619995] Xenomai: scheduling class idle registered.
[    0.625366] Xenomai: scheduling class rt registered.
[    0.638031] Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded.
[    0.645019] Xenomai: debug mode enabled.


-- 

Suresh balijepalli
Rosenehim,Baveria.

[-- Attachment #2: Type: text/html, Size: 25062 bytes --]

Re: [Xenomai-help] Regarding booting

[Gilles Chanteperdrix]

On 06/24/2011 11:57 AM, suresh reddy wrote:
> Hi all,
> 
> my booting process getting freezed after the message
> 
> uncompressing the kernel.
> 
> the modules i moved on to the sd card are  modules.builtin , modules.order,
> Module.symvers.
> 
> I used printk to display booting messages on console .

According to these logs, this kernel boots fine. So, we do not have
enough information to help you.

-- 
                                                                Gilles.

Re: [Xenomai-help] Regarding booting

[Gilles Chanteperdrix]

On 06/24/2011 11:57 AM, suresh reddy wrote:
> Hi all,
> 
> my booting process getting freezed after the message
> 
> uncompressing the kernel.

Ah, you mean it freezes right after the message:
 "[    0.645019] Xenomai: debug mode enabled."

Ok. Let us start from the beginning. Please try to follow exactly this 
procedure, and tell me if you get a working uImage:

mkdir /tmp/xeno
cd /tmp/xeno
wget http://www.codesourcery.com/sgpp/lite/arm/portal/package7851/public/arm-none-linux-gnueabi/arm-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
tar -xvjf arm-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
export PATH=/tmp/xeno/arm-2010.09/bin:$PATH
git clone --depth 1 git://git.xenomai.org/xenomai-2.5.git
git clone --depth 1 --branch for-ipipe-2.6.37-arm git://git.xenomai.org/ipipe-gch.git
cd ipipe-gch
../xenomai-2.5/scripts/prepare-kernel.sh --arch=arm --linux=.
wget -O .config http://sisyphus.hd.free.fr/~gilles/omap4_panda_config
yes "" | make ARCH=arm oldconfig
make -j 8 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

The uImage will be found in /tmp/xeno/ipipe-gch/arch/arm/boot/uImage
The result of this compilation works for me. If it does not work for
you, please download it here:
http://sisyphus.hd.free.fr/~gilles/uImage-panda

And tell me if it still does not work.

> (Sourcery G++ Lite 2009q1-203)

I thought we found out that you could not compile with this version? 

> [    0.000000] Kernel command line: ro elevator=noop vram=32M
> mem=460M@0x80000000 mem=256M@0xA0000000 root=/dev/mmcblk0p2
> console=ttyO2,115200n8 fixrtc earlyprintk bootm 0x80000000

You have some problem here: bootm is a u-boot command it should not
end up on the kernel command line. Also, in a first step, please remove
the "mem" arguments.

-- 
                                                                Gilles.

[Xenomai-help] Fwd: Regarding booting

[suresh reddy]

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Hi all ,

i have followed  through the below mentioned procedure  and i have strucked
in the final step of boot process.

modprobe: FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such
file or directory

wget
http://www.codesourcery.com/sgpp/lite/arm/portal/package7851/public/arm-none-linux-gnueabi/arm-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
tar -xvjf arm-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
export PATH=/tmp/xeno/arm-2010.09/bin:$PATH
git clone --depth 1 git://git.xenomai.org/xenomai-2.5.git
git clone --depth 1 --branch for-ipipe-2.6.37-arm git://
git.xenomai.org/ipipe-gch.git
cd ipipe-gch
../xenomai-2.5/scripts/prepare-kernel.sh --arch=arm --linux=.
wget -O .config http://sisyphus.hd.free.fr/~gilles/omap4_panda_config
yes "" | make ARCH=arm oldconfig
make -j 8 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install
INSTALL_MOD_PATH=<replace with your SD card fs path>

and in my sdcard in /lib/modules  I have 2.6.37.6 directory

I have the mentioned file modules.dep in my sd card  /lib/modules/2.6.37.6/

i have tried some mentioned in web
 update-initramfs
editing the initramfs.confg (mod=replacing MOST with DEP)
and all but the error remain unchanged . If someone passthrough this problem
plase let me know.








Thanks
Suresh balijepalli
Rosenehim,Baveria.

[-- Attachment #2: Type: text/html, Size: 3077 bytes --]

Re: [Xenomai-help] Fwd: Regarding booting

[Gilles Chanteperdrix]

On 06/28/2011 03:08 PM, suresh reddy wrote:
> Hi all ,
> 
> i have followed  through the below mentioned procedure  and i have strucked
> in the final step of boot process.
> 
> modprobe: FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such
> file or directory

The below mentioned procedure was to test whether xenomai worked on your
panda board, and by no means a complete installation of Xenomai. The
conclusion is: Xenomai works on your board.

Now, if you want a complete installation, refer to Xenomai installation
instructions, and for the linux kernel installation, refer to any
website you want explaining how to install a Linux kernel with its
modules. Like I already told you, teaching you how to install a Linux
kernel is clearly not what the xenomai-help mailing list is for.

-- 
					    Gilles.

Re: [Xenomai-help] Fwd: Regarding booting

[suresh reddy]

[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]

On 28 June 2011 15:53, Gilles Chanteperdrix <
gilles.chanteperdrix@xenomai.org> wrote:

> On 06/28/2011 03:08 PM, suresh reddy wrote:
> > Hi all ,
> >
> > i have followed  through the below mentioned procedure  and i have
> strucked
> > in the final step of boot process.
> >
> > modprobe: FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No
> such
> > file or directory
>
> The below mentioned procedure was to test whether xenomai worked on your
> panda board, and by no means a complete installation of Xenomai. The
> conclusion is: Xenomai works on your board.
>
> Now, if you want a complete installation, refer to Xenomai installation
> instructions,

Do you mean  complete instructions as below on my host machine  as mentioned
in 2.1 of xenomai document and

$ $xenomai_root/scripts/prepare-kernel.sh --arch=x86 \
  --adeos=$xenomai_root/ksrc/arch/x86/patches/adeos-ipipe-2.6.29.4-x86-X.Y-ZZ.patch
\
  --linux=$linux_tree
$ cd $linux_tree
$ make [ARCH=i386] xconfig/gconfig/menuconfig # select the kernel and
Xenomai options
$ make [ARCH=i386] bzImage modules # then install as needed
$ mkdir $build_root && cd $build_root
$ $xenomai_root/configure --enable-x86-sep (*) \
  [--host=i686-linux CFLAGS="-m32 -O2" LDFLAGS="-m32"]

$ make install

preparing and building the target kernel as mentioned in 1.1 of the document
which i have done until now.

$ $xenomai_root/scripts/prepare-kernel.sh --arch=arm \
  --adeos=$xenomai_root/ksrc/arch/arm/patches/adeos-ipipe-2.6.20-arm-* \
  --linux=$linux_tree
$ cd $linux_tree
$ make ARCH=arm CROSS_COMPILE=arm-linux- O=$build_root csb637_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-linux- O=$build_root bzImage modules
# [manually install the kernel image, system map and modules to the
proper location]
$ cd $build_root
$ $xenomai_root/configure --build=i686-pc-linux-gnu --host=arm-linux
--enable-arm-mach=at91rm9200 --enable-arm-tsc
$ make DESTDIR=$staging_dir install



Is this completes the complete installation process ?











and for the linux kernel installation, refer to any
> website you want explaining how to install a Linux kernel with its
> modules. Like I already told you, teaching you how to install a Linux
> kernel is clearly not what the xenomai-help mailing list is for.
>
> --
>                                             Gilles.
>



-- 

Suresh balijepalli
Rosenehim,Baveria.

[-- Attachment #2: Type: text/html, Size: 4313 bytes --]

Re: [Xenomai-help] Fwd: Regarding booting

[Gilles Chanteperdrix]

On 06/28/2011 05:06 PM, suresh reddy wrote:
> On 28 June 2011 15:53, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
> 
>> On 06/28/2011 03:08 PM, suresh reddy wrote:
>>> Hi all ,
>>>
>>> i have followed  through the below mentioned procedure  and i have
>> strucked
>>> in the final step of boot process.
>>>
>>> modprobe: FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No
>> such
>>> file or directory
>>
>> The below mentioned procedure was to test whether xenomai worked on your
>> panda board, and by no means a complete installation of Xenomai. The
>> conclusion is: Xenomai works on your board.
>>
>> Now, if you want a complete installation, refer to Xenomai installation
>> instructions,
> 
> Do you mean  complete instructions as below on my host machine  as mentioned
> in 2.1 of xenomai document and
> 
> $ $xenomai_root/scripts/prepare-kernel.sh --arch=x86 \
>   --adeos=$xenomai_root/ksrc/arch/x86/patches/adeos-ipipe-2.6.29.4-x86-X.Y-ZZ.patch
> \
>   --linux=$linux_tree
> $ cd $linux_tree
> $ make [ARCH=i386] xconfig/gconfig/menuconfig # select the kernel and
> Xenomai options
> $ make [ARCH=i386] bzImage modules # then install as needed
> $ mkdir $build_root && cd $build_root
> $ $xenomai_root/configure --enable-x86-sep (*) \
>   [--host=i686-linux CFLAGS="-m32 -O2" LDFLAGS="-m32"]
> 
> $ make install
> 
> preparing and building the target kernel as mentioned in 1.1 of the document
> which i have done until now.
> 
> $ $xenomai_root/scripts/prepare-kernel.sh --arch=arm \
>   --adeos=$xenomai_root/ksrc/arch/arm/patches/adeos-ipipe-2.6.20-arm-* \
>   --linux=$linux_tree
> $ cd $linux_tree
> $ make ARCH=arm CROSS_COMPILE=arm-linux- O=$build_root csb637_defconfig
> $ make ARCH=arm CROSS_COMPILE=arm-linux- O=$build_root bzImage modules
> # [manually install the kernel image, system map and modules to the
> proper location]
> $ cd $build_root
> $ $xenomai_root/configure --build=i686-pc-linux-gnu --host=arm-linux
> --enable-arm-mach=at91rm9200 --enable-arm-tsc
> $ make DESTDIR=$staging_dir install
> 
> 
> 
> Is this completes the complete installation process ?
> 

No, the complete installation instructions of xenomai are in the file
"README.INSTALL" in Xenomai sources, here you are citing only one part
of it. But they assume you already know how to install Linux, which is
why the module installation is not detailed and we tell you "manually
install the kernel image, system map and modules to the proper location".

So, you should learn how to compile a custom version of the kernel for
your board, and when you know how to do that, following xenomai
installations will be easy.

Using google 5 minutes, I found:
http://www.omappedia.com/wiki/Building_Linux_OMAP_Kernel
http://labs.igep.es/index.php/The_Linux_kernel
http://www.cyberciti.biz/tips/compiling-linux-kernel-26.html
http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
http://www.tuxradar.com/content/how-compile-linux-kernel

-- 
					    Gilles.