Re: [Gumstix-users] Bluetooth Module (Marvel chip 8688) not working with omap3530

[Goks <go...@gm...>]

Hi all,
When we run hciattach command,
we got the  following message .

[root@OMAP3EVM btmodules]#hciattach ttyS1 any
hci_register_dev: c6c0e400 name  type 3 owner bf03bb00
h4_recv: Unknown HCI packet type 00
hci_sock_dev_event: hdev hci0 event 1
hci_send_to_sock: hdev (null) len 8

[root@OMAP3EVM btmodules]# hciattach ttyS1 bcsp
BCSP initialization timed out

[root@OMAP3EVM btmodules]# hciconfig
hci_sock_create: sock c6811ce0
hci_sock_ioctl: cmd 800448d2 arg 2a01a008
hci_sock_ioctl: cmd 800448d3 arg 2a01922c
hci_dev_get: 0
hci0:   Type: UART
       BD Address: 00:00:hci_sock_release: sock c6811ce0 sk c70c5400
00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
       DOWN
       RX bytes:1 acl:0 sco:0 events:0 errors:1
       TX bytes:0 acl:0 sco:0 commands:0 errors:0



[root@OMAP3EVM btmodules]#hciattach ttyS1 any 115200 noflow
hci_register_dev: c1ff6800 name  type 3 owner bf03bb00
hci_sock_dev_event: hdev hci0 event 1
hci_send_to_sock: hdev (null) len 8
[root@OMAP3EVM btmodules]# hciconfig
hci_sock_create: sock c68111e0
hci_sock_ioctl: cmd 800448d2 arg 2a01a008
hci_sock_ioctl: cmd 800448d3 arg 2a01922c
hci_dev_get: 0
hci0:   Type: UART
       BD Address: 00:00:hci_sock_release: sock c68111e0 sk c70c5400
00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
       DOWN
       RX bytes:0 acl:0 sco:0 events:0 errors:0
       TX bytes:0 acl:0 sco:0 commands:0 erro

Please share your ideas to proceed further debugging.

Regards
Gokul




Søren Steen Christensen wrote:
> 
> Hi Gokul,
> 
> This is really much more of a WM-BG-MR-03- than an OMAP3-question, but two
> things pops up in my mind:
> 
> 1) I/O voltage – OMAP runs 1V8 – Looking at the datasheet for WM-BG-MR-03
> it
> seems to support either 1V8 or 3V3 – Is it supplies with 1V8 for I/Os?
> 
> 2) Hardware Flow control? I don’t know if this is active on power up for
> this device, but I have previously worked with BT chips, which required
> Flow
> Control during initial communication. In given case it might be the BT
> modules doesn’t output any data since it thinks the Flow Control Pin is
> asserted in case you haven’t taken any special care about this on the
> Overo?
> 
> Good luck – Please let us know what fixed the problem when you have found
> the bug :-)
>   Søren
> 
> ---
> SSC Solutions ApS - Denmark - www.ssc-solutions.dk 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day 
> trial. Simplify your report design, integration and deployment - and focus
> on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> 
> 

-- 
View this message in context: http://old.nabble.com/Bluetooth-Module-%28Marvel-chip-8688%29-not-working-with-omap3530-tp26373073p26573448.html
Sent from the Gumstix mailing list archive at Nabble.com.