[Xenomai-help] booting

[Xenomai-help] booting

[suresh reddy]

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

Dear Giles ,

here is the log . I have copied the modules namely modules.builtin and
Modules.symvers and  modules.order to ext3 partion as mentioned in previous
mail. but still the below log seems to be problem regarding modules.



Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 2.6.37.6 (root@domain.hid) (gcc version 4.5.1
(Sourcery G++ Lite 2010.09-50) ) #1 SMP PREEMP1
[    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] 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 @c09a1000 s12384 r8192 d16288
u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 130048
[    0.000000] Kernel command line: ro elevator=noop vram=32M
root=/dev/mmcblk0p2 console=ttyO2,115200n8 fixrtc earlyK
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)

[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144
bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072
bytes)
[    0.000000] Memory: 512MB = 512MB total

[    0.000000] Memory: 505940k/505940k available, 18348k 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 : 0xe0800000 - 0xf8000000   ( 376 MB)

[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)

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

[    0.000000]       .init : 0xc0008000 - 0xc002e000   ( 152 kB)

[    0.000000]       .text : 0xc002e000 - 0xc04f3000   (4884 kB)

[    0.000000]       .data : 0xc04f4000 - 0xc0526520   ( 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 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] [<c0037b90>] (dump_backtrace+0x0/0x110) from [<c041824c>]
(dump_stack+0x18/0x1c)
[    0.000000]  r6:c04a5441 r5:00000364 r4:c04f5f40 r3:00000000

[    0.000000] [<c0418234>] (dump_stack+0x0/0x1c) from [<c005c7e4>]
(warn_slowpath_common+0x54/0x6c)
[    0.000000] [<c005c790>] (warn_slowpath_common+0x0/0x6c) from
[<c005c8a0>] (warn_slowpath_fmt+0x38/0x40)
[    0.000000]  r8:80024930 r7:c05055bc r6:00000000 r5:c050602c r4:c0526a14

[    0.000000] r3:00000009

[    0.000000] [<c005c868>] (warn_slowpath_fmt+0x0/0x40) from [<c00453c4>]
(omap2_clkdm_deny_idle+0x58/0xc8)
[    0.000000]  r3:00000000 r2:c04a5463

[    0.000000] [<c004536c>] (omap2_clkdm_deny_idle+0x0/0xc8) from
[<c0045568>] (clkdm_init+0x134/0x170)
[    0.000000]  r5:c05055a4 r4:c050602c

[    0.000000] [<c0045434>] (clkdm_init+0x0/0x170) from [<c000d620>]
(omap2_init_common_hw+0x20/0x9c)
[    0.000000]  r7:c0504be4 r6:c099e0c0 r5:c0026118 r4:c0526520

[    0.000000] [<c000d600>] (omap2_init_common_hw+0x0/0x9c) from
[<c000f500>] (omap4_panda_init_irq+0x18/0x24)
[    0.000000] [<c000f4e8>] (omap4_panda_init_irq+0x0/0x24) from
[<c000a918>] (init_IRQ+0x18/0x20)
[    0.000000] [<c000a900>] (init_IRQ+0x0/0x20) from [<c0008b30>]
(start_kernel+0x17c/0x2e4)
[    0.000000] [<c00089b4>] (start_kernel+0x0/0x2e4) from [<80008034>]
(0x80008034)
[    0.000000]  r6:c0026114 r5:c05266d0 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.013244] bio: create slab <bio-0> at 0

[    0.015197] SCSI subsystem initialized

[    0.016845] usbcore: registered new interface driver usbfs

[    0.017028] usbcore: registered new interface driver hub

[    0.017242] usbcore: registered new device driver usb

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

[    0.049285] Skipping twl internal clock init and using bootloader value
(unknown osc rate)
[    0.050933] twl6030: PIH (irq 39) chaining IRQs 368..387

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

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

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

[    0.055145] regulator: VANA: 2100 mV normal standby

[    0.055877] regulator: VCXIO: 1800 mV normal standby

[    0.056640] regulator: VDAC: 1800 mV normal standby

[    0.057403] regulator: VUSB: 3300 mV normal standby

[    0.058654] regulator: VAUX1_6030: 1000 <--> 3000 mV at 1800 mV normal
standby
[    0.059875] regulator: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal
standby
[    0.061096] regulator: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal
standby
[    0.078643] i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz

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

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

[    0.120422] Switching to clocksource ipipe_tsc

[    0.136901] NET: Registered protocol family 2

[    0.137115] IP route cache hash table entries: 4096 (order: 2, 16384
bytes)
[    0.137695] TCP established hash table entries: 16384 (order: 5, 131072
bytes)
[    0.138000] TCP bind hash table entries: 16384 (order: 5, 196608 bytes)

[    0.138275] TCP: Hash tables configured (established 16384 bind 16384)

[    0.138305] TCP reno registered

[    0.138305] UDP hash table entries: 256 (order: 1, 8192 bytes)

[    0.138336] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)

[    0.138641] NET: Registered protocol family 1

[    0.139190] RPC: Registered udp transport module.

[    0.139190] RPC: Registered tcp transport module.

[    0.139221] RPC: Registered tcp NFSv4.1 backchannel transport module.

[    0.139434] Unpacking initramfs...

[    0.600128] Freeing initrd memory: 8016K

[    0.601287] ------------[ cut here ]------------

[    0.601318] WARNING: at arch/arm/mach-omap2/pm.c:64
_init_omap_device+0x8c/0xac()
[    0.601318] _init_omap_device: could not find omap_hwmod for iva

[    0.601348] Modules linked in:

[    0.601348] Backtrace:

[    0.601379] [<c0037b90>] (dump_backtrace+0x0/0x110) from [<c041824c>]
(dump_stack+0x18/0x1c)
[    0.601409]  r6:c04a4976 r5:00000040 r4:df82ff40 r3:00000000

[    0.601440] [<c0418234>] (dump_stack+0x0/0x1c) from [<c005c7e4>]
(warn_slowpath_common+0x54/0x6c)
[    0.601470] [<c005c790>] (warn_slowpath_common+0x0/0x6c) from
[<c005c8a0>] (warn_slowpath_fmt+0x38/0x40)
[    0.601470]  r8:00000000 r7:c000eb94 r6:c05269d0 r5:c04a49e1 r4:c0024ed4

[    0.601501] r3:00000009

[    0.601501] [<c005c868>] (warn_slowpath_fmt+0x0/0x40) from [<c00416d4>]
(_init_omap_device+0x8c/0xac)
[    0.601531]  r3:c041cb8b r2:c04a498f

[    0.601562] [<c0041648>] (_init_omap_device+0x0/0xac) from [<c000ebb8>]
(omap2_common_pm_init+0x24/0x88)
[    0.601562]  r6:c0567c00 r5:c0504578 r4:c0024ed4

[    0.601623] [<c000eb94>] (omap2_common_pm_init+0x0/0x88) from
[<c002e928>] (do_one_initcall+0xc0/0x194)
[    0.601623] [<c002e868>] (do_one_initcall+0x0/0x194) from [<c0008df0>]
(kernel_init+0x158/0x220)
[    0.601654]  r8:00000000 r7:00000013 r6:c0567c00 r5:c0504578 r4:c0024ed4

[    0.601684] [<c0008c98>] (kernel_init+0x0/0x220) from [<c005fc38>]
(do_exit+0x0/0x678)
[    0.601684]  r6:c005fc38 r5:c0008c98 r4:00000000 r3:00000000

[    0.601715] ---[ end trace 1b75b31a2719ed1d ]---

[    0.601928] ------------[ cut here ]------------

[    0.601959] WARNING: at arch/arm/mach-omap2/pm.c:64
_init_omap_device+0x8c/0xac()
[    0.601959] _init_omap_device: could not find omap_hwmod for dsp

[    0.601959] Modules linked in:

[    0.601989] Backtrace:

[    0.601989] [<c0037b90>] (dump_backtrace+0x0/0x110) from [<c041824c>]
(dump_stack+0x18/0x1c)
[    0.602020]  r6:c04a4976 r5:00000040 r4:df82ff40 r3:00000000

[    0.602050] [<c0418234>] (dump_stack+0x0/0x1c) from [<c005c7e4>]
(warn_slowpath_common+0x54/0x6c)
[    0.602081] [<c005c790>] (warn_slowpath_common+0x0/0x6c) from
[<c005c8a0>] (warn_slowpath_fmt+0x38/0x40)
[    0.602081]  r8:00000000 r7:c000eb94 r6:c05269d8 r5:c04a25fa r4:c0024ed4

[    0.602111] r3:00000009

[    0.602111] [<c005c868>] (warn_slowpath_fmt+0x0/0x40) from [<c00416d4>]
(_init_omap_device+0x8c/0xac)
[    0.602142]  r3:c041cb8b r2:c04a498f

[    0.602142] [<c0041648>] (_init_omap_device+0x0/0xac) from [<c000ebec>]
(omap2_common_pm_init+0x58/0x88)
[    0.602172]  r6:c0567c00 r5:c0504578 r4:c0024ed4

[    0.602203] [<c000eb94>] (omap2_common_pm_init+0x0/0x88) from
[<c002e928>] (do_one_initcall+0xc0/0x194)
[    0.602203] [<c002e868>] (do_one_initcall+0x0/0x194) from [<c0008df0>]
(kernel_init+0x158/0x220)
[    0.602233]  r8:00000000 r7:00000013 r6:c0567c00 r5:c0504578 r4:c0024ed4

[    0.602264] [<c0008c98>] (kernel_init+0x0/0x220) from [<c005fc38>]
(do_exit+0x0/0x678)
[    0.602264]  r6:c005fc38 r5:c0008c98 r4:00000000 r3:00000000

[    0.602294] ---[ end trace 1b75b31a2719ed1e ]---

[    0.603271] I-pipe: Domain Xenomai registered.

[    0.603332] Xenomai: hal/arm started.

[    0.603607] Xenomai: scheduling class idle registered.

[    0.603607] Xenomai: scheduling class rt registered.

[    0.611083] Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded.

[    0.611114] Xenomai: debug mode enabled.

[    0.616394] Xenomai: starting native API services.

[    0.616394] Xenomai: starting POSIX services.

[    0.616729] Xenomai: starting RTDM services.

[    0.616912] Xenomai: registered exported object RN#0 (regions)

[    0.616973] Xenomai: starting pSOS+ services.

[    0.617187] Xenomai: registered exported object heap0 (heaps)

[    0.617279] Xenomai: starting VRTX services.

[    0.617370] Xenomai: starting VxWorks services.

[    0.617431] Xenomai: starting uITRON services.

[    0.618652] VFS: Disk quotas dquot_6.5.2

[    0.618774] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    0.620056] msgmni has been set to 1003

[    0.620727] io scheduler noop registered (default)

[    0.620758] io scheduler deadline registered

[    0.620941] io scheduler cfq registered

[    0.621551] omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP
UART0
[    0.680603] omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP
UART1
[    0.810516] omap-hsuart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP
UART2
[    1.888671] console [ttyO2] enabled

[    2.040496] omap-hsuart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP
UART3
[    2.201293] usbcore: registered new interface driver smsc95xx

[    2.207336] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    2.214385] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

[    2.220397] ehci-omap ehci-omap.0: new USB bus registered, assigned bus
number 1
[    2.280578] ehci-omap ehci-omap.0: irq 109, io mem 0x4a064c00

[    2.300445] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00

[    2.306549] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

[    2.313629] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[    2.321228] usb usb1: Product: OMAP-EHCI Host Controller

[    2.326782] usb usb1: Manufacturer: Linux 2.6.37.6 ehci_hcd

[    2.332611] usb usb1: SerialNumber: ehci-omap.0

[    2.338012] hub 1-0:1.0: USB hub found

[    2.341979] hub 1-0:1.0: 3 ports detected

[    2.370605] Initializing USB Mass Storage driver...

[    2.375946] usbcore: registered new interface driver usb-storage

[    2.382263] USB Mass Storage support registered.

[    2.387268] usbcore: registered new interface driver libusual

[    2.393310] i2c /dev entries driver

[    2.405792] TCP cubic registered

[    2.409179] Initializing XFRM netlink socket

[    2.413818] NET: Registered protocol family 17

[    2.418579] NET: Registered protocol family 15

[    2.423309] Registering the dns_resolver key type

[    2.428375] VFP support v0.3: implementor 41 architecture 3 part 30
variant 9 rev 1
[    2.436737] ThumbEE CPU extension supported.

[    2.441284] Power Management for TI OMAP4.

[    2.445617] clock: disabling unused clocks to save power

[    2.452606] regulator_init_complete: incomplete constraints, leaving
VAUX3_6030 on
[    2.461242] regulator_init_complete: incomplete constraints, leaving
VAUX2_6030 on
[    2.469604] regulator_init_complete: incomplete constraints, leaving
VAUX1_6030 on
[    2.477996] regulator_init_complete: incomplete constraints, leaving VUSB
on
[    2.485900] regulator_init_complete: incomplete constraints, leaving VDAC
on
[    2.496795] regulator_init_complete: incomplete constraints, leaving
VCXIO on
[    2.504760] regulator_init_complete: incomplete constraints, leaving VANA
on
[    2.512664] regulator_init_complete: incomplete constraints, leaving
VUSIM on
[    2.520629] regulator_init_complete: incomplete constraints, leaving VPP
on
[    2.531433] Freeing init memory: 152K

Loading, please wait...

modprobe: FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such
file or directory
[    2.580718] mmc0: host does not support reading read-only switch.
assuming write-enable.

mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
[    2.610534] mmc0: new high speed SDHC card at address e624
[    2.616912] mmcblk0: mmc0:e624 SD04G 3.69 GiB
[    2.626800]  mmcblk0: p1 p2
Couldn't get a file descriptor referring to the console
[    2.660552] usb 1-1: new high speed USB device using ehci-omap and
address 2
[    2.820892] usb 1-1: New USB device found, idVendor=0424, idProduct=9514

[    2.827911] usb 1-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[    2.838165] hub 1-1:1.0: USB hub found

[    2.842864] hub 1-1:1.0: 5 ports detected

[    3.120941] usb 1-1.1: new high speed USB device using ehci-omap and
address 3
Begin: Loading essential drivers ... FATAL: Could not load /lib/modules/
2.6.37.6/modules.dep: No such file or directoy
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not[    3.251007] usb 1-1.1: New USB device found,
idVendor=0424, idProduct=ec00
 load /lib/modul[    3.259124] usb 1-1.1: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
es/2.6.37.6/modules.dep: No such file or directo[    3.272369] smsc95xx
v1.0.4
ry

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

Begin: Running /scripts/init-premount ... done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
[    3.334838] smsc95xx 1-1.1:1.0: usb0: register 'smsc95xx' at
usb-ehci-omap.0-1.1, smsc95xx USB 2.0 Ethernet, 0a:fa4
Begin: Running /scripts/local-premount ... FATAL: Could not load
/lib/modules/2.6.37.6/modules.dep: No such file or dy
done.

FATAL: Could not load /lib/modules/2.6.37[    3.414215] EXT3-fs (mmcblk0p2):
recovery required on readonly filesystem
No such file or [    3.423309] EXT3-fs (mmcblk0p2): directory

write access will be enabled during recovery

[    3.433197] usb 1-1.2: new low speed USB device using ehci-omap and
address 4
[    3.441650] EXT3-fs: barriers not enabled

[    3.546875] usb 1-1.2: New USB device found, idVendor=413c,
idProduct=3012
[    3.554077] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[    3.561859] usb 1-1.2: Product: Dell USB Optical Mouse

[    3.567230] usb 1-1.2: Manufacturer: Dell

[    3.643890] kjournald starting.  Commit interval 5 seconds

[    3.643951] EXT3-fs (mmcblk0p2): recovery complete

[    3.648071] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data
mode
Begin: Running /[    3.670776] usb 1-1.3: new low speed USB device using
ehci-omap and address 5
scripts/local-bottom ... done.

done.

Begin: Running /scripts/init-bottom ... done.

[    3.806610] usb 1-1.3: New USB device found, idVendor=413c,
idProduct=2105
[    3.814239] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[    3.822052] usb 1-1.3: Product: Dell USB Keyboard

[    3.826995] usb 1-1.3: Manufacturer: Dell
init: ureadahead main process (560) terminated with status 5
fsck from util-linux-ng 2.17.2
/dev/mmcblk0p2: clean, 117812/472352 files, 542738/949843 blocks
[ OK ]ting sensors limits
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * PulseAudio configured for per-user sessions
saned disabled; edit /etc/default/saned
[ OK ]bling additional executable binary formats binfmt-support
Begin: Loading essential drivers ... FATAL: Could not load /lib/modules/
2.6.37.6/modules.dep: No such file or directoy
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... FATAL: Could not load
/lib/modules/2.6.37.6/modules.dep: No such file or dy
done.
FATAL: Could not load /lib/modules/2.6.37.6/modules.dep: No such file or
directory
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
init: ureadahead main process (560) terminated with status 5
fsck from util-linux-ng 2.17.2
/dev/mmcblk0p2: clean, 117812/472352 files, 542738/949843 blocks
[ OK ]ting sensors limits
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * PulseAudio configured for per-user sessions
saned disabled; edit /etc/default/saned
[ OK ]bling additional executable binary formats binfmt-support


-- 

Suresh balijepalli
Rosenehim,Baveria.

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

Re: [Xenomai-help] booting

[Gilles Chanteperdrix]

On 06/24/2011 06:44 PM, suresh reddy wrote:
> Dear Giles ,
> 
> here is the log . I have copied the modules namely modules.builtin and
> Modules.symvers and  modules.order to ext3 partion as mentioned in previous
> mail. but still the below log seems to be problem regarding modules.

Xenomai is loaded on your system, our job is done. Now, you have to
learn how to use a Linux kernel before you can learn how to use Xenomai.
As I already told you, there is a lot of documentation on the web about
this, starting with the kernel newbies site:

http://kernelnewbies.org/

Teaching you all this is clearly not what this mailing list is for.

Good luck.

-- 
                                                                Gilles.

[Xenomai-help] more questions

[David Wiebe]

Hello,

I have kernel 2.6.35.9 patched with xenomai for arm(beagleboard xm).

#1. rt_dev_ioctl as replacement for ioctl. My test program compiles, 
runs but does not perform as it should. If I change rt_dev_ioctl back to 
ioctl, everything works fine. What might I be missing?

#2. rtnet. I wrote a test snippet of code to test the ethernet part. 
Prepended the appropriate functions with rt_dev_ and same results as in #1.

I assume that if something wasn't in the library I would get compiler 
errors and if the code running on the beagleboard  was bad, I would get 
run time errors. I have seen neither.

Are there any books or more learning materials out there for me to 
study? Any and all feedback appreciated.

David

Re: [Xenomai-help] more questions

[Gilles Chanteperdrix]

On 06/26/2011 05:17 AM, David Wiebe wrote:
> Hello,
> 
> I have kernel 2.6.35.9 patched with xenomai for arm(beagleboard xm).
> 
> #1. rt_dev_ioctl as replacement for ioctl. My test program compiles, 
> runs but does not perform as it should. If I change rt_dev_ioctl back to 
> ioctl, everything works fine. What might I be missing?

Hi,

We do not know
- which ioctl you are trying to use
- which driver you have written/loaded to implement this ioctl
- what you mean by "my program does not perform as it should", what is
the return value of this rt_dev_ioctl which is supposed to work?

> 
> #2. rtnet. I wrote a test snippet of code to test the ethernet part. 
> Prepended the appropriate functions with rt_dev_ and same results as in #1.
> 
> I assume that if something wasn't in the library I would get compiler 
> errors and if the code running on the beagleboard  was bad, I would get 
> run time errors. I have seen neither.

Again, what driver are you trying to use? What happens when you try and
configure it?

> 
> Are there any books or more learning materials out there for me to 
> study? Any and all feedback appreciated.

I would suggest starting with "Linux device drivers", it would give you
an idea of how things are divided between drivers and applications.
xenomai follows the same division. Then you can read the documents
listed here:
http://www.xenomai.org/index.php/Included_documentation_summary
and here:
http://www.xenomai.org/index.php/Publications

To have a better idea on how to work with xenomai.
> 
> David
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 
                                                                Gilles.

Re: [Xenomai-help] more questions

[David Wiebe]

On 11-06-26 08:17 AM, Gilles Chanteperdrix wrote:
> On 06/26/2011 05:17 AM, David Wiebe wrote:
>> Hello,
>>
>> I have kernel 2.6.35.9 patched with xenomai for arm(beagleboard xm).
>>
>> #1. rt_dev_ioctl as replacement for ioctl. My test program compiles,
>> runs but does not perform as it should. If I change rt_dev_ioctl back to
>> ioctl, everything works fine. What might I be missing?
> Hi,
>
> We do not know
> - which ioctl you are trying to use
I'm trying to get an spi port on the beagleboard to work in realtime.
I didn't know there were other ioctl's. I wrote a program with ioctl, 
tested it to make sure it worked, which it did, then changed ioctl's to 
rt_dev_ioctl's in hopes that doing so would enable real time behaviour. 
The program with rt_dev_ioctl's did not run as desired(no spi). I guess 
I can't simply change ioctl's with rt_dev_ioctl's to enable real time 
functionality? Do I have to patch xenomai to enable spi or something?
> - which driver you have written/loaded to implement this ioctl
I thought changing ioctl for rt_dev_ioctl was all that was required to 
implement this device in realtime mode. This device is an spi port.
> - what you mean by "my program does not perform as it should", what is
> the return value of this rt_dev_ioctl which is supposed to work?
>
I watch my oscilloscope for activity on the spi port. regular ioctl 
worked, rt_dev_ioctl did not. Both programs ran but only one worked.
>> #2. rtnet. I wrote a test snippet of code to test the ethernet part.
>> Prepended the appropriate functions with rt_dev_ and same results as in #1.
>>
>> I assume that if something wasn't in the library I would get compiler
>> errors and if the code running on the beagleboard  was bad, I would get
>> run time errors. I have seen neither.
> Again, what driver are you trying to use? What happens when you try and
> configure it?
>
So I have to patch the ethernet driver in order for it to work? I though 
that was taken care of when I patched the kernel with xenomai.
>> Are there any books or more learning materials out there for me to
>> study? Any and all feedback appreciated.
> I would suggest starting with "Linux device drivers", it would give you
> an idea of how things are divided between drivers and applications.
> xenomai follows the same division. Then you can read the documents
> listed here:
> http://www.xenomai.org/index.php/Included_documentation_summary
> and here:
> http://www.xenomai.org/index.php/Publications
>
> To have a better idea on how to work with xenomai.
>> David
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
Thanks!

Re: [Xenomai-help] more questions

[Gilles Chanteperdrix]

On 06/27/2011 03:39 AM, David Wiebe wrote:
> I'm trying to get an spi port on the beagleboard to work in realtime.
> I didn't know there were other ioctl's. I wrote a program with ioctl, 
> tested it to make sure it worked, which it did, then changed ioctl's to 
> rt_dev_ioctl's in hopes that doing so would enable real time behaviour. 
> The program with rt_dev_ioctl's did not run as desired(no spi). I guess 
> I can't simply change ioctl's with rt_dev_ioctl's to enable real time 
> functionality? Do I have to patch xenomai to enable spi or something?

Hi,

What you have to do is to write a driver for whatever SPI controller you
are using, using the RTDM API.

>> - which driver you have written/loaded to implement this ioctl
> I thought changing ioctl for rt_dev_ioctl was all that was required to 
> implement this device in realtime mode. This device is an spi port.

No.

>> - what you mean by "my program does not perform as it should", what is
>> the return value of this rt_dev_ioctl which is supposed to work?
>>
> I watch my oscilloscope for activity on the spi port. regular ioctl 
> worked, rt_dev_ioctl did not. Both programs ran but only one worked.

There are other ways to debug software than an oscilloscope. Looking at
the functions return values when they have one is a good start.

>>> #2. rtnet. I wrote a test snippet of code to test the ethernet part.
>>> Prepended the appropriate functions with rt_dev_ and same results as in #1.
>>>
>>> I assume that if something wasn't in the library I would get compiler
>>> errors and if the code running on the beagleboard  was bad, I would get
>>> run time errors. I have seen neither.
>> Again, what driver are you trying to use? What happens when you try and
>> configure it?
>>
> So I have to patch the ethernet driver in order for it to work? I though 
> that was taken care of when I patched the kernel with xenomai.

You do not have to patch anything. Again, what you lack is probably an
ethernet driver, or simply to load and configure the rtnet driver for
the hardware you have, exactly like you do with Linux.

If you are going to write drivers, I really suggest you read "Linux
device drivers", then read the RTDM skin documentation to understand the
RTDM API. Note that most of the time, you can "port" a Linux driver to
RTDM or Rtnet, there is even a guide on how to do so for network drivers
in rtnet sources.

-- 
                                                                Gilles.

Re: [Xenomai-help] more questions

[David Wiebe]

On 11-06-27 04:04 AM, Gilles Chanteperdrix wrote:
> On 06/27/2011 03:39 AM, David Wiebe wrote:
>> I'm trying to get an spi port on the beagleboard to work in realtime.
>> I didn't know there were other ioctl's. I wrote a program with ioctl,
>> tested it to make sure it worked, which it did, then changed ioctl's to
>> rt_dev_ioctl's in hopes that doing so would enable real time behaviour.
>> The program with rt_dev_ioctl's did not run as desired(no spi). I guess
>> I can't simply change ioctl's with rt_dev_ioctl's to enable real time
>> functionality? Do I have to patch xenomai to enable spi or something?
> Hi,
>
> What you have to do is to write a driver for whatever SPI controller you
> are using, using the RTDM API.
>
So, I've got to write a driver for the SPI controller using the RTDM API.
OK, thanks.

>>> - which driver you have written/loaded to implement this ioctl
>> I thought changing ioctl for rt_dev_ioctl was all that was required to
>> implement this device in realtime mode. This device is an spi port.
> No.
>
That would be too easy wouldn't it?
>>> - what you mean by "my program does not perform as it should", what is
>>> the return value of this rt_dev_ioctl which is supposed to work?
>>>
>> I watch my oscilloscope for activity on the spi port. regular ioctl
>> worked, rt_dev_ioctl did not. Both programs ran but only one worked.
> There are other ways to debug software than an oscilloscope. Looking at
> the functions return values when they have one is a good start.
>
Fair enough.
>>>> #2. rtnet. I wrote a test snippet of code to test the ethernet part.
>>>> Prepended the appropriate functions with rt_dev_ and same results as in #1.
>>>>
>>>> I assume that if something wasn't in the library I would get compiler
>>>> errors and if the code running on the beagleboard  was bad, I would get
>>>> run time errors. I have seen neither.
>>> Again, what driver are you trying to use? What happens when you try and
>>> configure it?
>>>
>> So I have to patch the ethernet driver in order for it to work? I though
>> that was taken care of when I patched the kernel with xenomai.
> You do not have to patch anything. Again, what you lack is probably an
> ethernet driver, or simply to load and configure the rtnet driver for
> the hardware you have, exactly like you do with Linux.
>
> If you are going to write drivers, I really suggest you read "Linux
> device drivers", then read the RTDM skin documentation to understand the
> RTDM API. Note that most of the time, you can "port" a Linux driver to
> RTDM or Rtnet, there is even a guide on how to do so for network drivers
> in rtnet sources.
>
I've got a copy of the book.

Thanks for the info.

[Xenomai-help] More questions - spi/ethernet

[David Wiebe]

Hello all,

I'm wondering if there would be anyone who would be interested in either 
collaborating with me on writing drivers for the spi port and getting 
ethernet to work in real time on the beagleboard xm.

In fact, I'd be willing to pay someone for their time to either guide me 
through this process or perform the tasks above with full documentation. 
The results of this exercise would be published and available for all as 
a learning tool/example and to use free of charge and to copy/modify etc 
etc.

Please contact me if you are interested so we can negotiate rates or 
collaborative efforts.

In writing this email, I hope it is not seen as undermining the purpose 
of open source or the mailing list. I apologise in advance if somehow I 
have disturbed the spirit of this group. I want to learn about this and 
understand it as efficiently as possible from someone with experience.

Sincerely,

David

Re: [Xenomai-help] More questions - spi/ethernet

[Gilles Chanteperdrix]

On 06/27/2011 11:37 PM, David Wiebe wrote:
> Hello all,
> 
> I'm wondering if there would be anyone who would be interested in either 
> collaborating with me on writing drivers for the spi port and getting 
> ethernet to work in real time on the beagleboard xm.

What is the ethernet chip used by the beagleboard xm?

-- 
                                                                Gilles.

Re: [Xenomai-help] More questions - spi/ethernet

[David Wiebe]

On 11-06-27 02:41 PM, Gilles Chanteperdrix wrote:
> On 06/27/2011 11:37 PM, David Wiebe wrote:
>> Hello all,
>>
>> I'm wondering if there would be anyone who would be interested in either
>> collaborating with me on writing drivers for the spi port and getting
>> ethernet to work in real time on the beagleboard xm.
> What is the ethernet chip used by the beagleboard xm?
>
LAN9514

Re: [Xenomai-help] More questions - spi/ethernet

[Gilles Chanteperdrix]

On 06/28/2011 06:42 AM, David Wiebe wrote:
> On 11-06-27 02:41 PM, Gilles Chanteperdrix wrote:
>> On 06/27/2011 11:37 PM, David Wiebe wrote:
>>> Hello all,
>>>
>>> I'm wondering if there would be anyone who would be interested in either
>>> collaborating with me on writing drivers for the spi port and getting
>>> ethernet to work in real time on the beagleboard xm.
>> What is the ethernet chip used by the beagleboard xm?
>>
> LAN9514
> 

That is where we should have started... This is an usb-ethernet adapter,
getting it to work with rtdm will not be easy, as you will need to write
a driver for the usb host controller, in addition to the ethernet driver
itself. There is an usb stack for RTDM (usb4rt), but I am not sure in
what state it is currently.

-- 
					    Gilles.