From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] I have a question about the bdaddr utility
Date: Thu, 08 Sep 2005 02:28:37 +0200 [thread overview]
Message-ID: <1126139317.14636.15.camel@blade> (raw)
In-Reply-To: <20050907101308.027e8482.pws@csr.com>
Hi Peter,
> > > > > My question is, is this change permanently written to the chip, or is it
> > > > > merely a volatile change as far as the running kernel is concerned?
> > > > the change is permanent.
> > >
> > > Would it be possible to make it volatile?
> >
> > in case of CSR chips the BD_ADDR is a PSKEY. I don't know if it can be
> > made volatile. This is a question for the CSR gurus ;)
>
> It's possible to have volatile PSKEYs. You need to use the CSR BCCMD
> command set to make this work, but that's the same set you'd be using to
> write the PSKEY to flash. The command is BCCMDVARID_PS. You write the
> PSKEY to temporary (actually, it says here "transient") store (code 8)
> instead of the default (code 0) or implementation (usually meaning flash,
> code 1). Then you have to perform a warm reset by setting
> BCCMDVARID_WARM_RESET --- this resets pretty much everything except the
> persistent store, including resetting the host transport. There's no way
> around the warm reset; the new address won't take effect otherwise. Note
> the temporary store overrides any address in flash.
this is great. I added a "-t" switch to the bdaddr utility to make the
change of the address volatile and a "-r" switch to perform the needed
cold or warm reset.
> If you don't already have access to the BCCMD command set this is likely to
> be Greek, unfortunately. (Unless you speak Greek.)
Some people of us speak Greek ;)
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-09-08 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 16:22 [Bluez-users] I have a question about the bdaddr utility Ben Tullis
2005-09-06 17:03 ` Marcel Holtmann
2005-09-06 20:15 ` Andreas Beck
2005-09-06 20:53 ` Marcel Holtmann
2005-09-07 9:13 ` Peter Stephenson
2005-09-08 0:28 ` Marcel Holtmann [this message]
2005-09-07 9:13 ` Ronny L Nilsson
2005-09-07 10:10 ` Ben Tullis
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=1126139317.14636.15.camel@blade \
--to=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).