[Armadillo:09159] Armadillo-460のbluetooth通信
email@hidden
2013年 8月 30日 (金) 19:29:52 JST
お世話になります。
磯間と申します。
現在、Armadillo-460のUSBポートにBluetoothドングルを接続して、タブレット端末と
Bluetooth通信を行っていますが、タブレット側からデバイスを認識できません。
Bluetoothドングルの挿抜を行うと下記メッセージが出力されます。
usb 2-1: new full speed USB device using fsl-ehci and address 2 usb 2-1: configuration #1 chosen from 1 choice
また、/sys/class/Bluetooth/hcioのディレクトリも生成されます。
カーネルコンフィグの設定等に問題があるのでしょうか？
Bluetooth関連の設定など、詳しい方がいましたら、ご教授お願いします。
コンフィグ設定と起動メッセージは以下の通りです。
＜menuconfigでの設定＞
Networking --->
<*> Bluetooth subsystem support
Bluetooth subsystem support
<*> L2CAP protocol support
<*> SCO links support
<*> RFCOMM protocol support
[*] RFCOMM TTY support
<*> BNEP protocol support
[*] Multicast filter support
[*] Protocol filter support
<*> HIDP protocol support
Bluetooth device drivers --->
<*> HCI USB driver
[*] SCO (voice) support
<*> HCI SDIO driver
<*> HCI UART driver
[*] UART (H4) protocol support
[*] BCSP protocol support
[*] HCILL protocol support
<*> HCI BCM203x USB driver
<*> HCI BPA10x USB driver
<*> HCI BlueFRITZ! USB driver
<*> HCI VHCI (Virtual HCI device) driver
＜電源投入時のarmadilloのログ＞
Hermit-At v2.1.3-1 (armadillo4x0) compiled at 16:39:56, Aug 24 2011 Uncompressing kernel............................................................................................................done.
Uncompressing ramdisk...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................done.
Linux version 2.6.26-at17 (2.6.26) (email@hidden) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #24 PREEMPT Thu Aug 29 17:36:35 JST 2013
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
Machine: Armadillo-460
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: console=ttymxc1,115200 MXC IRQ initialized PID hash table entries: 512 (order: 9, 2048 bytes) MXC GPT timer initialized, rate = 133000000
Console: colour dummy device 80x30
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: 110128KB available (3164K code, 225K data, 132K init) Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 480 bytes
NET: Registered protocol family 16
MXC WDOG1 Enabled
CPU is i.MX25 Revision 1.1
Clock input source is 24000000
MXC GPIO hardware
GPIO-56 autorequested
GPIO-6 autorequested
Initializing CPLD: v2
Using SDMA I.API
MXC DMA API initialized
Registered MXC PWM device: CON9_25
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb MXC I2C driver MXC I2C driver
MC34704 regulator successfully probed
mc34704 0-0054: Loaded
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
regulator: Unable to get requested regulator: SDHC2 failed to parent regulator: SDHC2
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
NET: Registered protocol family 1
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 16207K
usb: Host 2 host (serial) registered
usb: DR host (utmi) registered
msgmni has been set to 246
io scheduler noop registered
io scheduler cfq registered (default)
pwm-backlight pwm-backlight: unable to request PWM for backlight
pwm-backlight: probe of pwm-backlight failed with error -2
mx2fb: Unable to set clock to 0
Console: switching to colour frame buffer device 60x17 mxc_sdc_fb mxc_sdc_fb.0: fb0: DISP0 BG fb device registered successfully.
mxc_sdc_fb mxc_sdc_fb.0: fb1: DISP0 FG fb device registered successfully.
Serial: MXC Internal UART driver
mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC console [ttymxc1] enabled
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 18) is a Freescale MXC
mxcintuart.4: ttymxc4 at MMIO 0x5002c000 (irq = 40) is a Freescale MXC
brd: module loaded
loop: module loaded
Freescale FlexCAN Driver
FEC Ethernet Driver
PPP generic driver version 2.4.2
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0) Driver 'sd' needs updating - please use bus_type methods
armadillo-nor: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method Using auto-unlock on power-up/resume
cfi_cmdset_0001: Erase suspend on write enabled
armadillo-nor: use default partitions(4) Creating 4 MTD partitions on "armadillo-nor":
0x00000000-0x00020000 : "nor.bootloader"
0x00020000-0x00220000 : "nor.kernel"
0x00220000-0x01fe0000 : "nor.userland"
0x01fe0000-0x02000000 : "nor.config"
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 fsl-ehci fsl-ehci.0: irq 35, io mem 0x53ff4400 fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 fsl-ehci fsl-ehci.1: irq 37, io mem 0x53ff4000 fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage USB Mass Storage support registered.
input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
i2c /dev entries driver
rtc-s35390a 3-0030: rtc core: registered rtc-s35390a as rtc0 i2c-gpio i2c-gpio.3: using pins 128 (SDA) and 129 (SCL, no clock stretching)
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
Bluetooth: Virtual HCI driver ver 1.2
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
Bluetooth: Broadcom Blutonium firmware driver ver 1.1
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.9
usbcore: registered new interface driver bpa10x
Bluetooth: BlueFRITZ! USB driver ver 1.1
usbcore: registered new interface driver bfusb
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 159 irq 9 INTERNAL DMA
mxsdhci: MXC SDHCI Controller Driver.
regulator: Unable to get requested regulator: SDHC2
mxsdhci: probe of mxsdhci.1 failed with error -2 Registered led device: red Registered led device: green Registered led device: yellow
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
i.MX ADC at 0x50030000 irq 46
ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20071116 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20071116)
can: broadcast manager protocol (rev 20080415)
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Static Power Management for Freescale i.MX25
input: imx_adc_ts as /devices/virtual/input/input1 i.MX ADC input touchscreen loaded.
rtc-s35390a 3-0030: setting system clock to 2000-01-01 02:45:23 UTC (946694723)
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 16207KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 132K
init started: BusyBox v1.00 (2013.06.27-10:03+0000) multi-call binary Starting fsck for root filesystem.
fsck 1.25 (20-Sep-2001)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/ram0 is mounted.
/devusb 2-1: new full speed USB device using fsl-ehci and address 2
/ram0: clean, 964/1152 files, 14718/16207 blocks
Checking root filesystem: done
Remounting root rw: done
Mounting proc: usb 2-1: configuration #1 chosen from 1 choice
done
Mounting usbfs: done
Mounting sysfs: done
Cleaning up system: done
Running local start scripts.
Starting udevd: done
Loading /etc/config: done
Changing file permissions: done
Configure /home/ftp: done
Starting syslogd: done
Starting klogd: done
Loading kernel module: awl13_sdio
awl13: Version 3.0.2 Load.
Starting basic firewall: done
Setting hostname: done
Configuring network interfaces: fec: PHY @ 0x0, ID 0x0007c0f1 -- LAN8720
eth0: link down
done
Starting inetd: done
Setting at-cgi: done
Starting lighttpd: eth0: link up, 100Mbps, full-duplex
done
Creating avahi.services: done
Starting avahi.daemon: done
Mounting ramfs /home/ftp/pub: done
以上宜しくお願いします。
armadillo メーリングリストの案内