Open ClassicOldSong opened 5 years ago
Only setting initial boot mode would brick even more: the device could not even be recognized properly from the system. Load the dump from https://github.com/wmertens/textblade-dongler/blob/master/doc/virgin-dongle-output.txt
could get the device half-work, not paring with the written key and have no interface for the OS to use.
I bricked 5 dongles just one night.....
😢 I also bricked a few 32kB ones, AFAIK you really do need 64kB. The memory addresses it tries to write are in the 64kB range IIRC.
So rom file actually not matters but only rom size matters? I'm communicating with a manufacturer to make some 64k cheap ones, but I'm not sure if their rom file is correct for 64k version. Also, 500pcs at least for customization and I don't think I need that much.....
I actually don't know much about the internals, paging @awh-tokyo to see if he can help :)
CSR has a special version of the ROM that enables the HID Proxy mode, and that ROM won’t fit on a 32k EEPROM. I believe that CSR will provide it to any manufacturer that buys their chip, but so far only the ones from Laird, and a few consumer brands sold in Japan have that version of the ROM on them. Probably your manufacturer will need to contact the salesperson at CSR to get their hands on it.
Or they could get their hands on it be reading off a Laird dongle, but that would be software piracy and as such isn’t advisable.
Okay I'll ask if they can provide such ROM. Also is there anyone who wants some cheap ones? If more people need this, I could be less hesitate on making 500pcs or not......
I managed to ues this method to pair a non textblade keyboard with a super cheap Chinese 32k rom dongle, it seems OK before unplugging from my computer, but upon replug it shows
config 1 has no interface
in dmesg, and I cannot change it back to HCI mode for no interface could be handled bylibusb
. Any idea on what's happing?