|
From: Jason K. <kra...@gm...> - 2013-08-16 17:56:52
|
Also, it's important to note that I've tried to follow the instructions listed here in order to put the Ubertooth into bootloader mode: http://sourceforge.net/mailarchive/forum.php?thread_name=CAPvyD7yFBuzpoDpJFD2VyL_RRecXzr-e8O8N%2BXveSZZ34Nqndg%40mail.gmail.com&forum_name=ubertooth-general However, after running ubertooth-util -f The device goes back to 2 green LEDS (1V8 and RST) On Fri, Aug 16, 2013 at 1:54 PM, Jason Kratzer <kra...@gm...>wrote: > Unfortunately it seems like I cannot update the firmware: > root@bt:~/ubertooth-2012-10-R1/host/usb_dfu# ./ubertooth-dfu --write > ../../ubertooth-one-firmware-bin/bluetooth_rxtx.bin > [Errno 32] Pipe error > > Traceback (most recent call last): > File "./ubertooth-dfu", line 226, in <module> > print dfu.get_status() > AttributeError: 'module' object has no attribute 'get_status' > root@bt:~/ubertooth-2012-10-R1/host/usb_dfu# lsusb > Bus 001 Device 007: ID ffff:0004 > > > On Fri, Aug 16, 2013 at 1:38 PM, Jared Boone <jb...@ea...> wrote: > >> On Aug 16, 2013, at 10:26 AM, Jason Kratzer <kra...@gm...> >> wrote: >> >> bNumInterfaces 2 >> >> >> I'm pretty sure this is a firmware issue. My recollection is that the >> first release had USB descriptors that were invalid (claimed two >> interfaces, but only one was described) and confused various hosts. I >> thought it was confined to Windows, but perhaps Linux has varying >> strictness concerning invalid descriptors. >> >> - Jared >> >> > |