Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: "Alexandre Jousset@NL" <mid@gtmp.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Belkin F8T002 PC Card problem with Bluez
Date: 01 Sep 2003 16:16:41 +0200	[thread overview]
Message-ID: <1062425807.13729.162.camel@pegasus> (raw)
In-Reply-To: <3F50803C.607@gtmp.org>

Hi Alexandre,

> 	I tried with setserial to set ttyS4 to irq 3 (it gave me this value
> once when doing setserial autoconfig) -> hang.
> 
> 	I tried with setserial to set port to 0x4010 (as listed as second I/O
> ports region with lspci), no error but hciconfig hci0 up fails with timeout.
> 
> 	With the original setup (irq 11 and ports at 0x4000, as the serial
> module set them and the config that put the lines h4_recv: Unknown HCI
> packet type xx), I wrote a small C program to read ttyS4 and print the
> numbers on stdout. I noticed some reccurrent value so I told the program
> to put a newline before each value 18. The output is :
> 
> -----------------------------------------------------------
> 18 20 e8 36 be f0
> 18 20 e8 36 be f8
> 18 20 e8 36 be f8
> 18 20 e8 36 ef 0f
> 18 24 e8 36 ef f0
> 18 24 e8 36 ef f0
> 18 20 e8 9b be f8
> 18 20 e8 36 ef 0f ff
> 18 20 e8 36 ef 0f ff
> 18 20 e8 9b be f8
> 18 24 e8 36 ef f0
> 18 20 e8 36 ef 0f
> 18 24 e8 36 ef d0
> 18 20 e8 36 ef d0
> 18 20 e8 9b be f8
> 18 20 e8 9b be f8
> 18 20 e8 9b be f8
> 18 20 e8 36 ef 0f
> 18 20 e8 36 ef 0f
> 18 20 e8 36 ef 0f
> 18 20 e8 9b be f8
> 18 20 e8 36 ef 0f ff
> 18 20 e8 9b be f8
> 18 20 e8 36 ef 41
> 18 20 e8 36 ef 0f
> 18 20 e8 36 ef 0f
> -----------------------------------------------------------
> 
> 	So that must mean something but I don't know what. The first octet is
> always 18, the second is either 20 or 24, the third always e8, the
> fourth either 36 or 9b, the fifth either be or ef, the sixth either 0f
> or d0 or f8 and when it is 0f it is sometimes followed by ff...

I think this is the BCSP protocol, but with wrong terminal settings or a
wrong baud rate. Try to attach your device with BCSP and different baud
rate settings and replug it every time to have a clean state.

Regards

Marcel




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-09-01 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 15:06 [Bluez-users] Belkin F8T002 PC Card problem with Bluez Alexandre Jousset@NL
2003-08-29 15:17 ` Marcel Holtmann
2003-08-29 15:26   ` Alexandre Jousset@NL
2003-08-30 10:45     ` Alexandre Jousset@NL
2003-09-01 14:16       ` Marcel Holtmann [this message]
2003-12-17 11:59         ` [Bluez-users] " Will Partain
2004-02-05 17:38           ` Alexandre Jousset

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=1062425807.13729.162.camel@pegasus \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=mid@gtmp.org \
    /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