This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I am using OMAP3530 board. I have an issue with modprobe which I am using to setup the pand service for the bluetooth device on the board.
root@omap3evm:~# modprobe bnep
FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory
root@omap3evm:~#
The problem is with the directory it is referring to. modules.dep fo rmy board is @ /lib/modules/2.6.29-rc3-omap1 but it is trying to refer '/lib/modules/2.6.32'. How can I fix this?
Thanks, Raj
It sounds likes you have 2.6.29 installed on your file system but are using a 2.6.32 kernel. You should install the 2.6.32 kernel modules onto your file system. If you are sure that bnep does not depend on other modules. you can use "insmod bnep.ko" instead.
Hi,
I'm able to reproduce this problem exeactly as Raj describes.
I followed the directions in the ECS Getting Started Guide http://processors.wiki.ti.com/index.php/OMAP35x_Wireless_Connectivity_Getting_Started_Guide
The first set of steps is the Build Environment Guide http://processors.wiki.ti.com/index.php/OMAP3530x_Build_enviroment_guide_beta_3_release.
The build environment guide has a link to this PSP http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/OMAP_03_00/03_00_01_06//exports/AM35x-OMAP35x-PSP-SDK-03.00.01.06.tgz and that's the one I used.
After untaring the PSP, I used the prepackaged rootfs.jffs2 file located here... AM35x-OMAP35x-PSP-SDK-03.00.01.06/images/fs/omap3530/rootfs.jffs2
I followed the inmstructions from the getting started guide to burn the filesystem to flash, i double checked my tftpboot folder on my host machine to ensure it's the one from the PSP and it is...
Perform the following commands at the u-boot prompt; Flashing the rootfs File Sytem
mw.b 0x81600000 0xff 0x6050000
nand erase 780000 f870000
nand erase clean 780000 f870000
tftpboot 0x81600000 rootfs.jffs2
nandecc sw
nand write.i 0x81600000 780000 6050000
root@omap3evm:~/demo/bluetooth# cat /proc/version
Linux version 2.6.32 (x-Ubuntu-10) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Jun 1 10:56:53 CDT 2011
However, when I look at the /lib/modules directory, it shows the following
root@omap3evm:/lib/modules# ls -al
drwxr-xr-x 3 root root 0 Jan 1 1970 .
drwxr-xr-x 5 root root 0 Dec 2 19:24 ..
drwxr-xr-x 3 root root 0 Jan 1 1970 2.6.29-rc3-omap1
Here's what's in that folder
root@omap3evm:/lib/modules/2.6.29-rc3-omap1# ls -al
drwxr-xr-x 3 root root 0 Jan 1 1970 .
drwxr-xr-x 3 root root 0 Jan 1 1970 ..
drwxr-xr-x 4 root root 0 Jan 1 1970 kernel
-rw-r--r-- 1 root root 45 Jan 1 1970 modules.alias
-rw-r--r-- 1 root root 69 Jan 1 1970 modules.ccwmap
-rw-r--r-- 1 root root 446 Jan 1 1970 modules.dep
-rw-r--r-- 1 root root 73 Jan 1 1970 modules.ieee1394map
-rw-r--r-- 1 root root 141 Jan 1 1970 modules.inputmap
-rw-r--r-- 1 root root 81 Jan 1 1970 modules.isapnpmap
-rw-r--r-- 1 root root 74 Jan 1 1970 modules.ofmap
-rw-r--r-- 1 root root 99 Jan 1 1970 modules.pcimap
-rw-r--r-- 1 root root 43 Jan 1 1970 modules.seriomap
-rw-r--r-- 1 root root 536 Jan 1 1970 modules.symbols
-rw-r--r-- 1 root root 189 Jan 1 1970 modules.usbmap
I'm by no means a Linux expert so maybe it's normal to have a /lib/modules directory that doesn't seem to match the kernel version but my gut tells me this is wrong. It's almost as if the PSP prepackaged filesystem rootfs.jffs2 form the OMAP3530 directory is not the one for 2.6.32 but rather 2.6.29. I checked the manifest files but no mention of the jffs2.
Just for reference, I decided to look at the target filesystem from the DVSDK on my host machine (ti-dvsdk_omap3530-evm_4_01_00_09). It would appear it uses the same version of the PSP, 03.00.01.06. In the /lib/modules directory, it has 2.6.32.
x-Ubuntu-10:~/targetfs/lib/modules$ ls -al
total 12
drwxr-xr-x 3 root root 4096 2011-01-13 00:30 .
drwxr-xr-x 4 root root 4096 2011-01-13 00:30 ..
drwxr-xr-x 3 root root 4096 2011-05-19 12:12 2.6.32
Upon closer attention, I noticed a lot of filesystem related errors while the EVM is booting (I can provide a dump if needed). Here are my bootargs and bootcmd from uboot
bootcmd=nand read.i 0x80000000 280000 300000; bootm 0x80000000
bootargs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2
It's very possible human error is involved here so I plan to go through the whole process again this afternoon to see if I get the same results.
My setup is
Mistral OMAP3530 EVM Main Board RevG
WL1271 Daughter Card Rev C
Host - VirtualBox with Ubuntu 10.04 LTS
I went through the whole process again on a fresh EVM and from a different host machine. Same results as before. Here's my Linux boot dump...
Texas Instruments X-Loader 1.46 (May 27 2011 - 15:06:37)
Starting OS Bootloader...
U-Boot 2009.11 (May 06 2010 - 23:47:47)
OMAP3430/3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
I2C: ready
DRAM: 128 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Read back SMSC id 0x92200000
Die ID #7b2c00040000000004032d460d009007
Net: smc911x-0
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x280000, size 0x300000
3145728 bytes read: OK
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2535148 Bytes = 2.4 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux................................................................................................................................................................ done, booting the kernel.
Linux version 2.6.32 (sinoj@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Dec 22 15:27:08 GMT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 EVM
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp 720m )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw
rootfstype=jffs2
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 120560KB available (4436K code, 386K data, 180K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
omap3evmdc: Driver registration complete
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VAUX2_4030: 2800 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
omap-iommu omap-iommu.0: isp registered
OMAP35x Linux PSP version 03.00.01.06 (OMAP3EVM)
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 235
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
WL1271: BT_EN GPIO initialized
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
console [ttyS0] enabled
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader-nand"
0x000000080000-0x000000240000 : "uboot-nand"
0x000000240000-0x000000280000 : "params-nand"
0x000000280000-0x000000780000 : "linux-nand"
0x000000780000-0x000010000000 : "jffs2-nand"
OneNAND driver initializing
omap2-onenand omap2-onenand: Cannot request GPMC CS
omap2-onenand: probe of omap2-onenand failed with error -16
smsc911x: Driver version 2008-10-21.
smsc911x-mdio: probed
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
net eth0: MAC Address: 00:50:c2:7e:8d:86
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 52:16:98:a3:fe:4b
usb0: HOST MAC --:--:--:--:--:--
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.32 musb-hcd
usb usb2: SerialNumber: musb_hdrc
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input0
ads7846 spi1.0: touchscreen, irq 335
input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input1
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
tvp514x 3-005c: Registered to v4l2 master omap34xxcam!!
omap-iommu omap-iommu.0: isp: version 1.1
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
No device for DAI wl1271bt
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3 EVM SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
asoc: wl1271bt <-> omap-mcbsp-dai-1 mapping ok
ALSA device list:
#0: omap3evm (twl4030)
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1886 buckets, 7544 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Power Management for TI OMAP3.
SmartReflex driver initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
twl_rtc twl_rtc: setting system clock to 2011-01-13 00:56:03 UTC (1294880163)
tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 2
VFS: Mounted root (jffs2 filesystem) on device 31:4.
Freeing init memory: 180K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 141
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
Remounting root file system...
WARNING: Couldn't open directory /lib/modules/2.6.32: No such file or directory
FATAL: Could not open /lib/modules/2.6.32/modules.dep.temp for writing: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory
root: mount: mounting rootfs on / failed: No such file or directory
root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... net eth0: SMSC911x/921x identified at 0xc8860000, IRQ: 336
udhcpc (v1.13.2) started
Sending discover...
Sending select for 192.168.111.171...
Lease of 192.168.111.171 obtained, lease time 86400
adding dns 192.168.111.1
done.
INIT: Entering runlevel: 5
Starting telnet daemon.
modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory
Starting syslogd/klogd: done
Starting thttpd.
Starting OMAP Demo application.
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|
Arago Project http://arago-project.org omap3evm ttyS0
Arago 2009.11 omap3evm ttyS0
omap3evm login: root
root@omap3evm:~# cd /lib/modules
root@omap3evm:/lib/modules# ls -al
drwxr-xr-x 3 root root 0 Jan 1 1970 .
drwxr-xr-x 4 root root 0 Jan 1 1970 ..
drwxr-xr-x 3 root root 0 Jan 1 1970 2.6.29-rc3-omap1
root@omap3evm:/lib/modules#
I think that whoever packaged up "AM35x-OMAP35x-PSP-SDK-03.00.01.06" mismatched the pre-built kernel and fs. The "/lib/modules/2.6.32" directory is created as part of the kernel build. Short of rebuilding the kernel, you'll have to track down the modules directory that matches your uImage kernel file. In theory, you could copy over the 2.6.32 directory from "ti-dvsdk_omap3530-evm_4_01_00_09" on your host. Assumes the same architecture and cross-compiler.
There are some pre-build FS on Arago that are close but not quite. Something like 2.6.32-rc2.
I assume that the issue reported by Raj is a failure to bring up the BNEP profile on the EVM and he is working with OMAP35x GA release http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/ecs/WL1271_Linux_SDK/3_00_01_06/exports/V3.00.01.06-WL6.1.6.0.3-Linux-x86-Install. Please correct me if my assumption is wrong.
If you are facing issues with BNEP profiles, please note that the BNEP profile is not supported (ie. not tested completely on the omap35x EVM) as per the release notes (Release Notes for RN-0006 --- WL1271 GA Drivers Release notes for OMAP3530 http://processors.wiki.ti.com/index.php OMAP35x_Wireless_Connectivity_Release_Notes_beta_3_release).
However, if you follow the instructions given in the build instruction guide (http://processors.wiki.ti.com/index.php/OMAP3530x_Build_enviroment_guide_beta_3_release.) the BNEP feature will be statically available as part of the kernel image (uImage). You need not insert run-time loadable bnep module.(Please check the kernel boot logs; Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast)
Regarding the errors "FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory" , The code base for the GA release is the Linux PSP "AM35x-OMAP35x-PSP-SDK-03.00.01.06" and it refers to http://processors.wiki.ti.com/index.php/AM35x-OMAP35x-PSP_03.00.00.05_UserGuide. The package does not contain any pre-built run-time modules and the FS does not have directory called /lib/modules/2.6.32. Unfortunately, the user guide does not describe how to build kernel modules and how to install modules to target file system. Many of the kernel features can be built as run-time loadable modules so that they are not part of the kernel image, but can be inserted into the kernel at run-time.
Since all supported BT features (L2CAP, RFCOMM, and so on) are statically available in the kernel image, we don't use modprobe command.
However, If you have modules (configured as modules (M) in the kernel config); to build all features, perform the following command after kernel build:
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
To install the compiled modules into the target root file system, issue the following command:
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=<root fs path>
where the <root fs path> is either the path of your target root file system on the host machine (/opt/filesys for example) or a temporary directory from where copy the contents to the /lib directory of your root file system. After kernel boot-up use command modprobe command to load the module.
If you are facing different issues with the OMAP35x+WL1271 EVM, please post logs on the forum.
Vijay,
Thanks for the response.
Your assumption is correct, we are using http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/ecs/WL1271_Linux_SDK/3_00_01_06/exports/V3.00.01.06-WL6.1.6.0.3-Linux-x86-Install.
Thanks for sharing the fact that BNEP is statically compiled into the kernel, I saw no mention of this in the release notes.
I have a couple follow-up questions:
1. Why is there a /lib/modules/2.6.29-rc3-omap1 directory in the target filesystem?
2. Any idea what is causing the filesystemn errors when the kernel boots as described and highlighted in red in my previous post?
Thanks,
-Brad
I really think you have to check with one of your TI peers. Someone at TI put 2.6.29-rc3-omap1 modules into the pre-built file system instead of 2.6.32 modules. I would even go as far as saying this is bug.
Brad,
Thanks for the reply. I am taking over for Vijay here. He meant to say that the BNEP profile is not formally supported in the GA release for the omap35x EVM; we know that the required component for its support is statically complied into the kernel. However, you may need to install/enable more user space bluez applications separately.
1. Why is there a /lib/modules/2.6.29-rc3-omap1 directory in the target filesystem?
Ans. As Norman Wong said, this could be a bug in the AM35x-OMAP35x-PSP-SDK-03.00.01.06 PSP release.
2. Any idea what is causing the filesystemn errors when the kernel boots as described and highlighted in red in my previous post?
Ans : Those errors exist in the AM35x-OMAP35x-PSP-SDK-03.00.01.06 PSP release. Issues like "modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory" can be fixed by doing the steps given in Vijay's post;
# make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
# make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=<root fs path>
Regards
Sinoj
The "make modules" option is a solution but the "AM35x-OMAP35x-PSP-SDK-03.00.01.06 PSP" release should contain the pre-built binaries that was used to program supported TI EVMs. Without having to build or make anything. Implies that the file system image used on the EVM is not the file system image in the PSP. I believe the PSP is shipped with the EVMs on a DVD. I thought the binaries on this DVD can be used to restore a EVM to factory condition. Again, without making or building anything.
Brad,
As discussed we need to carry out the following steps as part of the WL1271 build procedure to fix the errors/warnings on the file system;
Building kernel Modules :
Assume that we just built the WL1271 project, on successful compilation of the build (http://processors.wiki.ti.com/index.php/OMAP3530x_Build_enviroment_guide_beta_3_release#Built_binaries_setup), the contents of the directory would be as shown below;
Ex. [arago@localhost Sources]$ ls
bluetooth buildlog common image kernel README set_wl1271_build_env.sh wireless WL1271Build.sh
1. Change the directory to the kernel source directory
cd kernel/linux-03.00.01.06/
Ex. [arago@localhost Sources]$ cd kernel/linux-03.00.01.06/
2. Export the tool chain path
export PATH=<ARM_TOOLCHAIN_PATH>/bin:$PATH ---- where the <ARM_TOOLCHAIN_PATH> is the path of the toolchain installed on the host machine;
Ex: [arago@localhost Sources]$ export PATH=/opt/crosstools/codesourcery/arm-2009q1/bin:$PATH
3. Build the modules;
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
Ex. [arago@localhost Sources]$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules
4. Install the modules into a directory on the host
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=<root fs path> ----- where the <root fs path> is a temporary directory on the host machine
Ex. [arago@localhost Sources]$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=~/omap_rootfs_modules
5. Change the directory to the <root fs path>
cd <root fs path>
Ex. [arago@localhost Sources]$ cd ~/omap_rootfs_modules/
6. Compress the modules;
tar -czf libmodules.tar.gz lib/
7. Copy the "libmodules.tar.gz" to the TFTP server as in case of uImage and v03.00.01.06-WL6.1.6.0.3.tar.bz2
Installing Linux Kernel Modules:
After loading the WLAN and the Bluetooth images
(http://processors.wiki.ti.com/index.php/OMAP35x_Wireless_Connectivity_Getting_Started_Guide#Loading_the_WLAN_and_the_Bluetooth_images)
Perform the following commands on the EVM Linux shell to download the new kernel modules;
root@omap3evm:~# cd /
root@omap3evm:~/demo# tftp -g -r libmodules.tar.gz <IP address of the tftp server>
root@omap3evm:/# ls
root@omap3evm:/# tar -xf libmodules.tar.gz
Hope this helps.
Regards
Sinoj
Sinoj,
Thanks for the updated procedure.I have a couple follow-on comments:
1. In your last steps where we untar the libmodules.tar.gz on the target, shouldn't that be done in / and not ~/demo? I did it in ~/demo but realized that the modules need to go into / so I copied the tar file to / then untared it and i now have the following below... If this is the correct way to do it, can you make sure to correct it in the wiki?
root@omap3evm:/lib/modules# ls -al
drwxr-xr-x 4 1000 1000 0 Dec 2 19:19 .
drwxr-xr-x 5 1000 1000 0 Aug 19 2011 ..
drwxr-xr-x 3 root root 0 Jan 1 1970 2.6.29-rc3-omap1
drwxr-xr-x 3 1000 1000 0 Dec 2 19:22 2.6.32
Now after booting, I don't have the errors about not finding /lib/modules/2.6.32/
2. The second thing I'd like to point out is, in my previous forum post above, in my kernel bootup log there were a handful of errors like the following:
udevd[554]: inotify_add_watch(3, (null), 10) failed: Bad address
I'm not quite sure what these errors mean so I did some googling and it would appear to be somehow related to memory allocation. So what I did was comapred the bootargs from the DVSDK instructions to the bootargs of the ECS instructions.
ECS Wiki says to use these bootargs
bootargs 'mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2'
The bootargs from the DVSDK are (after running setup.sh)...
setenv bootargs console=ttyS0,115200n8 rw mem=99M@0x80000000 mpurate=720 mem=128@0x88000000 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M root=/dev/nfs nfsroot=192.168.111.170:/home/a0322xxx/targetfs ip=dhcp
Below are the bootargs I ended up using, I took the mem definitions from the DVSDK and added them to the ECS bootargs, now the inotify_add_watch errors are gone.
bootargs 'mem=99M@0x80000000 mem=128@0x88000000 console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2'
The issue I have with this is, it was just a guess and I'm wondering if you could provide what the bootargs should really be.
Thanks
Brad
Thanks for pointing out the error; The "libmodules.tar.gz" must be extracted under "/". So updated the wiki accordingly. Also, i have tried the new bootargs and found no "inotify_add_watch" errors.
Thanks
Sinoj
