On Tuesday 08 June 2010 22:55:33 Josua Dietze wrote: > Am 08.06.2010 20:40, schrieb Sven Eckelmann: > > I think I found the problem. The correct USB-Mass-Storage command to send > > would be 55534243123456782000000080000c85010101180101010101000000000000. > > The attached patch fixed the problem. I think it was an copy and paste > > error from 19d2:0053. > > I'm slightly confused - this is the command that is in the config file > right now ... Ok, my fault. Wanted to write something different and stopped in the middle of the sentence. I wanted to say that the windows software sends 55534243123456782400000080000685000000240000000000000000000000 and not 55534243123456782000000080000c85010101180101010101000000000000 - which (as far as I can follow your explanation) is the correct command for some other devices with the same vendor/productID.
>
> > The difference is the data transfer length, cdb length and the actual raw
> > data (850000002400) which is transferred to the device. It is what the
> > vodafone drivers/software uses on windows and what is used here by me.
>
> This family of devices continues to turn dark hair into grey ...
>
> The guy who is assigned by Vodafone to take care about Linux usage of
> their hardware tells me that ZTE insists the correct command is
> "eject" which results in the following "message":
> 5553424312345678000000000000061b000000030000000000000000000000
>
> Most reports tell me this fails and they are successful with the
> command you mention.
>
> Please be so good and try this in the 19d2:2000 file:
>
> MessageContent="5553424312345678000000000000061b000000030000000000000000000
> 000"
> MessageContent2="55534243876543212000000080000c850101011801010101010000000
> 00000" NeedResponse=1
>
> Works with my ZTE MF110 and should catch the cases when the first
> command doesn't switch. The "NeedResponse" is essential for adhering
> to the standards if other commands are following the first.
The problem is that the device will not receive the next command after the
first one and the first one doesn't work here.
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Trying to send message 2 to endpoint 0x01 ...
Sending the message returned error -110. Trying to continue
Trying to send message 3 to endpoint 0x01 ...
Sending the message returned error -110. Trying to continue
So when I change it to
MessageContent="55534243123456782400000080000685000000240000000000000000000000"
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"
NeedResponse=1
it works for me - but cannot guarantee anything for anybody else.
So I checked your eject command and noticed that it is more a close
command....somewhat (length for example is missing). I tried
5553424312345678240000008000061b000000020000000000000000000000 instead and it
worked perfectly here too (03 - the close command didn't work, but 02 - the
eject command seems to be ok).
So I see currently following two commands:
- Vodafone windows way:
55534243123456782400000080000685000000240000000000000000000000
- Eject command:
5553424312345678240000008000061b000000020000000000000000000000
Best regards,
Sven
signature.asc
Description: This is a digitally signed message part.
