igotu2gpx team mailing list archive
-
igotu2gpx team
-
Mailing list archive
-
Message #00341
[Bug 394618] Re: Unable to obtain info from GPS tracker: Device responded with error code: -1
Thanks for reminding me of this bug :-). Ok, let's investigate this a
bit.
Could you please
- post the output of igotu2gpx -v info for 0.2.3?
- try whether it works with the 0.2.91 version if you call it from the command line like
"IGOTU2GPX_WORKAROUND=enabled igotu2gpx -v info" or
"IGOTU2GPX_NOWORKAROUND=enabled igotu2gpx -v info"
and also post the output?
If you have access to a Linux or Windows system, could you check whether
igotu2gpx has the same problems on these platforms (binaries for Windows
are available at https://launchpad.net/igotu2gpx/0.3/0.2.91, and if you
use Ubuntu you can find packages for Linux at
https://launchpad.net/~igotu2gpx/+archive/rc-archive).
** Changed in: igotu2gpx
Importance: Undecided => High
** Changed in: igotu2gpx
Status: New => Confirmed
** Changed in: igotu2gpx
Milestone: None => 0.3.0
** Changed in: igotu2gpx
Assignee: (unassigned) => Michael Hofmann (mh21)
--
Unable to obtain info from GPS tracker: Device responded with error code: -1
https://bugs.launchpad.net/bugs/394618
You received this bug notification because you are a member of
MobileAction i-gotU USB GPS travel logger Mac/Linux developers, which is
subscribed to igotu2gpx.
Status in MobileAction i-gotU USB GPS travel logger Mac/Linux support: Confirmed
Bug description:
#sudo igotu2gpx -v info
Retrieving info...
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 008
usb_os_find_busses: Found 007
usb_os_find_busses: Found 006
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_devices: Found 003 on 002
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 10 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 008
usb_os_find_devices: Found 012 on 007
usb_os_find_devices: Found 001 on 007
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 006
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 006
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
USB error: could not get bound driver: No data available
Command: 930101030000000000000000000000
Result size: 0x0000
Result data:
Command: 930a00000000000000000000000000
Result size: 0x000a
Result data: ab4a0300021800021100
Command: 9305040003019f0000000000000000
Result size: 0x0003
Result data: c22014
Command: 930b03001d00000000000000000000
Result size: 0x0003
Result data: 6e1d05
Command: 930507100004030000000000000000
Failed protocol: Invalid reply packet: 6e1d05
Command: 930507100004030000000000000000
Device failure: Device responded with error code: -2
Command: 930507100004030000000000000000
Device failure: Device responded with error code: -1
Command: 930507100004030000000000000000
Device failure: Device responded with error code: -1
Command: 930507100004030000000000000000
Failed: Device responded with error code: -1
Unable to obtain info from GPS tracker: Device responded with error code: -1
-------------------------------------------------------------------------------
the device is now blocked and the blue light stop blinking
i start the command again and i got a different response...
-------------------------------------------------------------------------------
#sudo igotu2gpx -v info
Retrieving info...
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 008
usb_os_find_busses: Found 007
usb_os_find_busses: Found 006
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_devices: Found 003 on 002
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 10 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 008
usb_os_find_devices: Found 012 on 007
usb_os_find_devices: Found 001 on 007
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 006
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 006
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
USB error: could not get bound driver: No data available
Command: 930101030000000000000000000000
Failed protocol: Response too short: expected 3, got 0 bytes
Command: 930101030000000000000000000000
Failed protocol: Response too short: expected 3, got 0 bytes
USB error: error sending control message: Protocol error
Command: 930101030000000000000000000000
Failed: Unable to send data to the device: Protocol error
Unable to obtain info from GPS tracker: Unable to send data to the device: Protocol error
---------------------------------------------------------------------------------------------------------------------
If i disconnect the device the power button does not work any more and no light is on.
If i reconnect the device to my laptop the device restart and works again.
---------------------------------------------------------------------------------------------------------------------
Here is my lsusb:
Bus 007 Device 013: ID 0df7:0900 Mobile Action Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0df7 Mobile Action Technology, Inc.
idProduct 0x0900
bcdDevice 0.00
iManufacturer 1 Mobile Action
iProduct 2 GT100/GT200
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 0000000
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
----------------------------------------------------------------------------------------------------------------------------------
and the different lsusb after "sudo igotu2gpx -v info"
----------------------------------------------------------------------------------------------------------------------------------
Bus 007 Device 013: ID 0df7:0900 Mobile Action Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0df7 Mobile Action Technology, Inc.
idProduct 0x0900
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
---------------------------------------------------------------------------------------------
cannot read device status, Protocol error (71)
---------------------------------------------------------------------------------------------
thx for help
:)
References