From: Pavel Ruzicka <pavouk@pavouk.org>
To: bluez-users@lists.sourceforge.net
Cc: Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [Bluez-users] DBT-120 firmware upgrade
Date: Sat, 27 Nov 2004 21:30:44 +0100 [thread overview]
Message-ID: <200411272130.44783.pavouk@pavouk.org> (raw)
In-Reply-To: <1101579731.27074.8.camel@pegasus>
Hello,
thanks for perfect explaining.
I have good news. I flashed my dongle, and she is not dead ;-)
Dongle now starts in HID mode. I must switch her to HCI with hid2hci.
hid2hci says something, that it fails, but it works. I have probably old
version of this utility.
Dongle in HID mode lights with power LED, but in HCI is power LED off.
Second LED blinks in both modes.
There are informations from hciconfig:
---------------------------------
# hciconfig hci0 version
hci0: Type: USB
BD Address: 00:0D:88:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
HCI Ver: 1.2 (0x2) HCI Rev: 0x632 LMP Ver: 1.2 (0x2) LMP Subver: 0x632
Manufacturer: Cambridge Silicon Radio (10)
# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0D:88:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
Build 1586
Chip version: BlueCore02
Max key size: 128 bit
SCO mapping: HCI
[root@home network-scripts]# hciconfig hci0 features
hci0: Type: USB
BD Address: 00:0D:88:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <broadcast encrypt>
<enhanced iscan> <interlaced iscan> <interlaced pscan>
<inquiry with RSSI> <AFH cap. slave> <AFH class. slave>
<AFH cap. master> <AFH class. master> <extended features>
-------------------------------
Thank you very much one more time for everything ;-)
Best regards,
Pavel Ruzicka
> > Can somebody explain me, what does it means and if it is not problem
> > for flashing?
>
> but if you upload a firmware you will get the latest type and this is 2.
>
> > Downloaded firmware is much longer than backuped. Is it OK?
>
> The GenericCSR.dfu contains two firmware files. One HCI 18.x for chips
> with 8 Mbit flash and a HCI 16.x for chips with 4 Mbit flash.
>
> Marcel
next prev parent reply other threads:[~2004-11-27 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 10:52 [Bluez-users] DBT-120 firmware upgrade Pavel Ruzicka
2004-11-26 17:25 ` Marcel Holtmann
2004-11-27 15:55 ` Pavel Ruzicka
2004-11-27 18:22 ` Marcel Holtmann
2004-11-27 20:30 ` Pavel Ruzicka [this message]
2004-11-27 20:50 ` Marcel Holtmann
2004-11-29 12:23 ` Steven Singer
2004-11-29 12:33 ` Marcel Holtmann
2004-11-29 12:49 ` Steven Singer
2004-11-29 17:30 ` Marcel Holtmann
2004-11-29 18:15 ` Peter Stephenson
2004-11-29 18:33 ` Marcel Holtmann
2004-11-29 18:44 ` Peter Stephenson
2004-11-29 18:46 ` Michal Semler
2004-11-27 0:58 ` Michal Semler
2004-11-27 3:03 ` Marcel Holtmann
2004-11-27 15:12 ` Pavel Ruzicka
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=200411272130.44783.pavouk@pavouk.org \
--to=pavouk@pavouk.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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