public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Wurmsdobler <peter@wurmsdobler.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] CSR bluecore initial problem
Date: Sat, 24 May 2008 12:04:23 +0100	[thread overview]
Message-ID: <4837F637.9060904@wurmsdobler.org> (raw)
In-Reply-To: <20844183.487421211530034467.JavaMail.coremail@bj163app76.163.com>

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

Hello,

a few months back I encountered a similar problem. hciattach did not 
(and still does not) always succeed, and bccmd seems to have a problem 
using the BlueCore serial protocol (bcsp), possibly a race condition. 
That's why I have to use:

      /usr/sbin/hciattach /dev/ttymxc2 bcsp 57600 flow
      /usr/sbin/hciconfig hci0 up
      /usr/sbin/bccmd -t hci psload -r /usr/etc/bluetooth/apm6628BT-UART.psr
      killall hciattach
      /usr/sbin/hciattach /dev/ttymxc2 bcsp 115200 flow
      /usr/sbin/hciconfig hci0 up

Notice the bccmd -t hci, so you have to attach first using bcsp, then 
use bccmd with this hci in order to download the psr file (which will 
reset the BlueCore), then kill the hci and re-attach.

Hope this helps,
peter



[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2008-05-24 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23  8:07 [Bluez-users] CSR bluecore initial problem attaboyu
2008-05-23  8:24 ` attaboyu
2008-05-24 11:04 ` Peter Wurmsdobler [this message]
2008-05-26  7:34   ` attaboyu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4837F637.9060904@wurmsdobler.org \
    --to=peter@wurmsdobler.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox