igotu2gpx

Errors trying i-gotU utilities on Linux

Asked by Graham Dicker

Compiled OK as far as I can tell but when I run it with the command

./igotu2gpx -v --action info

I get errors like this

Interface 0 already claimed by kernel driver, detaching
Command: 930101030000000000000000000000
Protocol violated : Invalid response packet: 303439
Command: 930101030000000000000000000000
Result:
Command: 930a00000000000000000000000000
Device error: Device responded with error code: -2
Command: 930a00000000000000000000000000
Result: d70e0500031800010b0c

and then it crashes after more messages like this:

Command: 930101000000000000000000000000
Result:
QThread: Destroyed while thread is still running
QWaitCondition::wakeOne(): mutex lock failure: Invalid argument

Using OpenSuse 12.2. My i-gotU is a model GT-120.

If I remove the call to cleanup() near the end of the info() and dump() functions then it does print out sensible information but hangs until I press Ctl-C.

What should I try please?

Question information

Language:
English Edit question
Status:
Answered
For:
igotu2gpx Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Michael Hofmann (mh21) said : 		#1

Hi Graham,

best thing to try is to use a different usb port/no usb hob or a different pc. It could be that you have a different version of the GT120, but I wouldn't think so.

Cheers
  Michael

Revision history for this message
Graham Dicker (graham-dicker) said : 		#2

I tried a different port but the problem still exists. There is no usb hub. I don't have another pc. I have been concentrating on trying to understand the purpose and action of the semaphore and Mutex in IgotuControlPrivate class and how they control the threading on the assumption that if I can understand that then I can start to track down where it goes wrong. Do you have something like a design document that gives an overview of how it all works?

Revision history for this message
Michael Hofmann (mh21) said : 		#3

Documentation of the protocol is in the HACKING file.

The semaphore/mutex are only used to relay the commands to the worker
thread. Everything is done in the reset/write/info/contents/purge
methods of IgotuControlPrivateWorker.

2014-06-28 10:02 GMT+02:00 Graham Dicker <email address hidden>:
> Question #250412 on igotu2gpx changed:
> https://answers.launchpad.net/igotu2gpx/+question/250412
>
> Graham Dicker posted a new comment:
> I tried a different port but the problem still exists. There is no usb
> hub. I don't have another pc. I have been concentrating on trying to
> understand the purpose and action of the semaphore and Mutex in
> IgotuControlPrivate class and how they control the threading on the
> assumption that if I can understand that then I can start to track down
> where it goes wrong. Do you have something like a design document that
> gives an overview of how it all works?
>
> --
> You received this question notification because you are a member of
> MobileAction i-gotU USB GPS travel logger Mac/Linux developers, which is
> an answer contact for igotu2gpx.
>

Can you help with this problem?

Provide an answer of your own, or ask Graham Dicker for more information if necessary.

To post a message you must log in.