From owner-freebsd-bluetooth@FreeBSD.ORG Fri Mar 6 03:18:05 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CC7CE8A for ; Fri, 6 Mar 2015 03:18:05 +0000 (UTC) Received: from galore.getmail.no (galore.getmail.no [84.210.184.6]) by mx1.freebsd.org (Postfix) with ESMTP id E517626B for ; Fri, 6 Mar 2015 03:18:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by galore.getmail.no (Postfix) with ESMTP id 1700345AAF; Wed, 4 Mar 2015 22:59:20 +0100 (CET) Received: from galore.getmail.no ([127.0.0.1]) by localhost (galore.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 5nGPdu3wHD0t; Wed, 4 Mar 2015 22:59:19 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by galore.getmail.no (Postfix) with ESMTP id 89935549BA; Wed, 4 Mar 2015 22:59:19 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.8.4 galore.getmail.no 89935549BA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1425506359; bh=52+NYdD3gN2Sc0qPWrwMVk5TYOzp2HJOByRMEYjtmNQ=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=ug2ozvr5GFB7jgzkyuTnxDDAHAkbxIp8gc6adb0b8r2zLw+wsSa/XUH4LbNBn3RkR uUfsJZqDw44E03AFsSKRX1Xj+XYRHMRLn+XuYUdUTIWp5POj6NGy2eysiIISBnd4XY YUftme3gRQM+dtfGCnokuap5aAD3bFpzfmgp15C0= X-Virus-Scanned: amavisd-new at galore.get.c.bitbit.net Received: from galore.getmail.no ([127.0.0.1]) by localhost (galore.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id oaJW9OQKyN1I; Wed, 4 Mar 2015 22:59:19 +0100 (CET) Received: from kg-core1.kg4.no (cm-84.215.180.206.getinternet.no [84.215.180.206]) by galore.getmail.no (Postfix) with ESMTPSA id 5E76A45AAF; Wed, 4 Mar 2015 22:59:19 +0100 (CET) Date: Wed, 4 Mar 2015 22:59:17 +0100 From: Torfinn Ingolfsen To: Maksim Yevmenkin Subject: Re: Belkin F8T065 doesn't register properly (BCM20702A0) Message-Id: <20150304225917.56bb81d3e6da2773a0deb5fa@getmail.no> In-Reply-To: References: <20150228220307.b0ab42716d574a9bcfd83094@getmail.no> <20150303223312.c7b12845ae652cfc315c1b61@getmail.no> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; amd64-portbld-freebsd9.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-bluetooth@freebsd.org" X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2015 03:18:05 -0000 On Wed, 4 Mar 2015 09:27:32 -0800 Maksim Yevmenkin 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