From: "Osted Software Development" <info@osted.dk>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bdaddr for CSR chipset - porting dificulties
Date: Fri, 29 Dec 2006 11:07:20 +0100 (CET) [thread overview]
Message-ID: <54530.80.165.155.106.1167386840.squirrel@webmail10.pair.com> (raw)
In-Reply-To: <544bb7070612280942n6907d4e2u107654fd71310df4@mail.gmail.com>
>>
>> Hi,
>>
>> > > I've been working on porting bluez's bdaddr utility to mac, and I
>> > > think I'm making pretty good progress. After digging around the
>> > > internals of IOBluetooth.framework, I've managed to, I think,
>> > > replicate the behavior of bdaddr's csr_write_bd_addr and
>> > > csr_reset_device.
>> > >
>> > > as far as I can tell, the command sent matches exactly what
>> > > csr_write_bd_addr would have sent with transient=false and addr =
>> > > 00-16-cb-1b-7e-ad. Anyone see what I'm doing wrong? Or even any
>> clue
>> > > what status 0x0009 is?
>> >
>> >
>> > Status 0x0009 = PERMISSION_DENIED
>> >
>> > I dont think you can change the bd_addr in the CSR chipset
>> > via UART/USB HCI commmands, only via SPI.
>> > Normally you only want to set the bd_addr during production.
>> >
>>
>> You can change it over the UART by using the bccmd util provided with
>> bluez utils. However, in the default configuration this will only change
>> the
>> address in RAM, not permanently in flash. This is by intention because
>> normaly you're not expected to do this unless you own a block of OUI
>> numbers where you can take a valid address from.
>>
>> So, as Susanne already mentioned normaly only in production.
>>
>> Ciao,
>>
>> Peter
>> |
>> | Gustav-Meyer-Allee 25, Geb. 12 Email: pewi@gw-instruments.de
>>
>>
> But only UART, not USB? I tried again with transient = true (word 7 =
> 0x0008) and I still get a response with status 0x0009.
>
> And yeah, I understand changing your BT address is generally a bad
> idea. This is just for research purposes. I'm trying to get a Wii to
> connect to a MacBook as if it were a Wii Remote and so far just
> matching the device name/class has proved insufficient. Current
> theory is it will only connect to devices in Nintendo's OUI ranges.
>
You could check the pskey 509 Security_active, some manufactures
enables this, and you can only disable it via SPI. If it is enabled,
I assume [ not tested :-) ] this will prevent you from changing the bd_addr.
-Susanne
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-29 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 7:38 [Bluez-devel] bdaddr for CSR chipset - porting dificulties Ian Rickard
2006-12-28 10:14 ` Osted Software Development
2006-12-28 11:18 ` Peter Wippich
2006-12-28 17:42 ` Ian Rickard
2006-12-29 10:07 ` Osted Software Development [this message]
2006-12-30 16:50 ` Peter Wippich
2006-12-30 20:32 ` Ian Rickard
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=54530.80.165.155.106.1167386840.squirrel@webmail10.pair.com \
--to=info@osted.dk \
--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