From: Ho Ming Shun <cyph@cyph.ath.cx>
To: Bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] BCM2035 over UART on the E680I
Date: Sun, 18 Sep 2005 21:44:41 +0800 [thread overview]
Message-ID: <432D6F49.80304@cyph.ath.cx> (raw)
Hi,
I'm part of a community of linux enthusiasts trying to hack the Motorola
E680I phone. Its a based on an Intel PXA270 running MontaVista Linux on
their 2.4.20 kernel. I've been trying to get BlueZ running on it.
The original Bluetooth stack implemented in the firmware is in one
userspace-only app, which talks to ttyS1. So no way to extend
functionality, which badly needs extending. The phone only publishes one
service: Object Push. No way to browse or be browsed, no HID, nothing.
From strace output, it seems to load some kind of firmware into the
phone using a vendor-specific HCI command:
write(3, "\x01\x2e\xfc\x00", 4) = 4
read(3, "\x04\x0e\x04\x01\x2e\xfc\x00", 8) = 7
read(3, "41", 8) = 2
write(3, ":03000000028EB0BD", 17) = 17
read(3, ".", 8) = 1
write(3, ":0B1109008FE18DE2E4F5E375E30122C"..., 33) = 33
.
.
.
Then it programs the Bluetooth address in using another vendor-specific
command (address is 00:12:8a:2d:3d:3e)
write(3, "\x01\x01\xfc\x06\x3e\x3d\x2d\x8a\x12\x00", 10) = 10
read(3, "\x04\x0e\x04\x01\x01\xfc\x00", 8) = 7
I've managed to duplicate this whole process, and get the hci_uart
driver attached to ttyS1. By default when first initialised, the
Bluetooth name is "Broadcom BCM2035".
However, the problem comes when BlueZ requests the Bluetooth address
back from the chip: it will reply with 00:00:00:00:00:00. Seems like its
not a problem unheard of:
http://www.linuxquestions.org/questions/history/341892
l2ping and hcitool scan works despite BlueZ not knowing the correct
local address.
Will this cause any problems BlueZ functionality or other applications?
Is this a sign that the chip is somehow configured wrongly?
Is this a common problem for this chip?
What are the known pitfalls and bugs (besides this one) for BCM2035?
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-09-18 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 13:44 Ho Ming Shun [this message]
2005-09-19 9:25 ` [Bluez-devel] BCM2035 over UART on the E680I Oliver
2005-09-19 10:22 ` Ho Ming Shun
2005-09-19 14:50 ` Oliver
2005-09-20 11:53 ` Marcel Holtmann
2005-09-23 11:41 ` Ho Ming Shun
2005-09-23 13:53 ` Marcel Holtmann
2005-09-23 13:07 ` Ho Ming Shun
2005-09-23 14:28 ` Marcel Holtmann
2005-09-24 0:22 ` Ho Ming Shun
2005-09-24 7:28 ` Ho Ming Shun
2005-10-03 8:47 ` [Bluez-devel] [SOLVED] " Ho Ming Shun
2005-10-03 11:36 ` Marcel Holtmann
2005-10-03 11:15 ` Ho Ming Shun
2005-10-03 12:42 ` Marcel Holtmann
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=432D6F49.80304@cyph.ath.cx \
--to=cyph@cyph.ath.cx \
--cc=Bluez-devel@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;
as well as URLs for NNTP newsgroup(s).