Gordon, thanks, that's great, detailed info...
> I am forwarding the best summary we have seen yet, from Tomas
> Targownik in Australia.
I took those steps and my bluetooth subsystem did not start working.
Going to a Verdex XM4 (non-pro, non-BT, early 2008 vintage, silk
PF270-R1511), I found that GPIO12 is routed to BT pin A3, the reset pin!
I can't check this on a newer non-BT board, but that seems wrong. All
the docs say GPIO7 is the reset, so I expected GPIO7 to come up on A3
(#reset) or maybe one of the wakeup pins B1 or B2. I could not find
GPIO7 anywhere on my R1511 board but did find GPIO12 on the BT module
In all the relevant posts, GPIO12 is set to AF1. I now understand the
AFn thing, but my old Intel PXA27x book (pre-Marvell) says that GPIO12
AF1 is a timer output. Based on that, I sorta expected GPIO12 to come
up on BT's A8, the 32khz clock. Imagine my surprise...
_Can anyone shed light on these observations, within limits of respect
for proprietary information?_ All I want to do is make my Bluetooth
work in buildroot.
These are the commands I used to manipulate GPIO7 and GPIO12:
echo "GPIO out set" > /proc/gpio/GPIO7
echo "GPIO out set" > /proc/gpio/GPIO12
echo "GPIO out clear" > /proc/gpio/GPIO7
echo "GPIO out clear" > /proc/gpio/GPIO12
These are my references:
UART page from Tomas' post: http://docwiki.gumstix.org/Gumstix_UARTs
I went ahead and added GPIO 44/45 to that page
based on my Intel PXA book
PBA 31308 Product Overview, linked from buildroot Bluetooth FAQ:
Verdex 60-pin connector chart:
PXA270 Processor Developer's Manual [280000-002].pdf, 2004 Intel,
linked from openwrt.org (I think). This version of the PXA
book does not mention HWUART and says GPIO7 is reserved for
power control. AFAIK, you can't get a newer manual without
going NDA with Marvell.
I took my stack apart and verified that the BTUART jumpers are off. I
also verified that all the BTUART signals go to the Infineon BT module
pads as well as to the Hirose-60, so it _is_ important to take those
jumpers off on ConsoleVX.
I booted my other board of the same model and vintage, with OE version
200805121046 (per /etc/version), and a ConsoleVX with BT jumpers off,
and it showed interesting behavior:
Starting 32kHz clock...Settled
Starting Bluetooth subsystem:
Trying baud rate 921600...
No response after reset
Got Startup Event -- retrying once
Detected bluetooth module at 921600 baud
Got: status=0x00, hci_ver=0x03, hci_rev=0x62b9, lmp_ver=0x03,
that is, failing at first but then recovering. This is with Bluetooth
Core ver 2.11. I don't know if my "Bluetooth Core" boot-time version
message corresponds to the "BlueZ utilities version" (v2.24, v3.24)
cited in Tomas' message.