search

thxomas / bdaddr

Updated version of the bluez bdaddr tool
23 stars 4 forks source link

Manufacturer: not assigned (6502) #5

Open cccsyy opened 1 year ago

cccsyy commented 1 year ago

sudo ./bdaddr -i hci0 C0:09:0A:14:47:10

Manufacturer: not assigned (6502) Device address: 80:45:DD:BF:C1:78

Unsupported manufacturer

what should I do to solve this? thank you.

thxomas commented 1 year ago

Hi ! As a dirty test, please try to edit line 359 of bdaddr.c and change the "2" value to "6502" then rebuild and retry. It will match your particular device values and try to use the commands I found for Intel chips. If it works, I'll add it properly. If not, some research will be needed to discover the commands to send to this new Intel chip type.

cccsyy commented 1 year ago

thanks a lot for your timely reply! And I've made it but it reports: Manufacturer: not assigned (6502) Device address: 80:45:DD:BF:C1:78 New BD address: C0:09:0A:14:47:10

Can't write new address

thxomas commented 1 year ago

OK, thus no luck. Research is needed, and I won't be able to help you directly, but can point you to the process :

  1. Identify your Intel BT chip (with lspci or lsusb)
  2. Dig on the internet (starting with intel.com) for a detailed datasheet if available.
  3. What you are looking for is the OCF byte of the command to be sent to the chip.
  4. Try your findings around line 253

Good luck if you push further !

cccsyy commented 1 year ago

thanks again for your reply. and I found my BT version is 5.2 so I've tried to search OCF byte from the specification. maybe I should try at "#define OCF_INTEL_WRITE_BD_ADDR 0x0031" and change the num 0x0031 could you please tell me the command name in HCI command of BT like "HCL_XXXXX_XXXX"? maybe although the chips and versions differ but the HCI command is still the same. thank you.

thxomas commented 1 year ago

Hi IIRC it's something like HCL_CUSTOM_COMMAND