Date: Wed, 4 Mar 2015 22:59:17 +0100 From: Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: Belkin F8T065 doesn't register properly (BCM20702A0) Message-ID: <20150304225917.56bb81d3e6da2773a0deb5fa@getmail.no> In-Reply-To: <CAFPOs6o1UYeUS45Pbdu_xEswf1cH6=m1ynQ%2BNpeyOi64ip8v-A@mail.gmail.com> References: <20150228220307.b0ab42716d574a9bcfd83094@getmail.no> <20150303223312.c7b12845ae652cfc315c1b61@getmail.no> <CAFPOs6o1UYeUS45Pbdu_xEswf1cH6=m1ynQ%2BNpeyOi64ip8v-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 Mar 2015 09:27:32 -0800
Maksim Yevmenkin <maksim.yevmenkin@gmail.com> wrote:
>
> bDeviceClass (0xff) is not matching UDCLASS_WIRELESS (0xe0). most
> likely it needs some sort of firmware to be loaded first.
Good call. I'll have a look.
>
> [...]
>
> >> Any hints on getting it to work?
>
> it probably needs firmware to be loaded first. you might be able to
> locate firmware, and, possibly hack on bcmfw(8) in the source tree to
> get it to load.
>
> if you have windows driver try to look at .hex, .img, .bin or
The included CD-ROM contains (Windows) software, organazied in nice folders with names WIN8, WIN7 and so on. I used the WIN7 folder for this example.
The folder contains just one file Setup.exe, but 7za can look into the archive. There are a lof of .hex files there, so I extract the archive.
Looking in the file bcbtums-win7x86-brcm.inf (text), I figure out that the correct firmwre file is named BCM20702A1_001.002.014.0889.0927.hex
Inspecting the file closer I find:
tingo@kg-core1$ ls -l BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
-rw-r--r-- 1 tingo users 57263 Oct 17 2012 BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
tingo@kg-core1$ file BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex: ASCII text, with very long lines, with CRLF line terminators
tingo@kg-core1$ srec_info BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
Format: Motorola S-Record
srec_info: BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex: 1: warning:
ignoring garbage lines
srec_info: BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex: 136: file contains
no data
tingo@kg-core1$ wc -l BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
135 BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
I'm not sure why srec_info complains, the first few lines of the file looks like this:
tingo@kg-core1$ head -5 BTW12/Win32/BCM20702A1_001.002.014.0889.0927.hex
:020000040009F1
:280000000108006999994204204EB1FD0400FFFFFFFF4006000000A0027020020A00280009000000000000001D
:FB002800411A0042726F6164636F6D20426C7565746F6F746820446576696365004C30003003420043004D00390032003000370030003200200042006C007500650074006F006F0074006800200034002E003000980100035C0100017206000300000800019304002000000068040012000C006A3600030012000000B0000000A0000000431008045310020180000000900000006310040273100402C1000000D000000020000000300000006902009F035D0C000A64E6B000008898425A33435F09003C280100040004F70C0A6F0098160800C600F3025D0066033000C900E10268005C033600C300E2026A0053033C00C200E1026C004E034100C500D6026C
:FB01230072004A034300C300CE02790042034800C500C00283003A034E00C800BF0282003B034E00C900BC028400370352000808070707070707060606060505050502C0F00094FC0E00FFFF00005E02000030FC0E00FFFF0F006304000000FD0E00FFFF00006602000088FC0E00FFFF0000000400002CFC0E00FFFF00004904000070FC0E00FFFF00000B09000074FC0E00FFFF00002E010000D8FF0E00FFFF000062190000D0FC0E00FFFF000020C90000C8FC0E00FFFF000038850000DCFC0E00FFFF00001CC80000CCFD0E00FFFF0000048000005CFC0E00FFFF00000200000020FC0E00FFFF000019210000E0FC0E000080000000000000C0FC0E00FF3C
:FB021E00FF000022000000948F0800FFFFFFFF00100010988F0800FFFF0000001000009C8F080000FFFFFF000A0A0ACCFC0E00FFFF00002B450000D07B0001040A08FC0E00FFFF00002E3600000CFC0E00FFFF00002CAE000010FC0E00FFFF00002AAC000014FC0E00FFFF0000A222000018FC0E00FFFF00001D2000001CFC0E00FFFF00000D15000020FC0E00FFFF0000858D000024FC0E00FFFF00008311000028FC0E00FFFF00000001000098FF0E00FFFF00003E410000C3160012691419310870047836042430607180764A3108290ACF0900100F0C6EF0B009F060D10900010403036B1420206B1A2400FF0108080A10060E020CFE0AFA08F606F20484
So the firmware route seems possible.
> looking for. of course, like i mentioned before, you need to hack
> something to load firmware. older Broadcom chips can be loaded with
> bcmfw(8). so its a good place to start.
If I understand this correctly, bcmfw(8) needs ubtbcmfw(4) to be able to download firmware?
Thanks for taking the time to answer my questions.
--
Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150304225917.56bb81d3e6da2773a0deb5fa>