On Tue, 24 Jul 2007, Ron Gage wrote:
> OK, here is what I have done. After opening the dev, setting the
> configuration and claiming the interface, I am sending a control message
> of bRequestType = 0x42, bRequest of 0x06, all other values = 0. This
> is the first "out up" packet sent to the
Alan Stern wrote:
> No, I said to look at the "up" _reports_. "report" != "packet".
>
> For IN transfers (from the device to the host), yes, the transfer data
> is displayed in the "up" report. For OUT transfers (host to device)
> the transfer data is displayed in the "down" report. For con
On Tue, 24 Jul 2007, Ron Gage wrote:
> > Don't you remember what I told you a few days ago? The setup packet
> > contents in the "down" report are unreliable. You need to look at an
> > "up" report.
> >
> > Alan Stern
> >
> >
> I remember it quite clearly. You told me to look at the "UP" p
On Tue, 24 Jul 2007, Ron Gage wrote:
> I have made the entire SnoopyPro capture file available on my web site:
> http://www.rongage.org/xyloc.usblog
Consider URB #10 as a good example. The information for the "up" part
says that the Setup packet consists of:
c2 00 ac 53 00 00 08 00
That's
Alan:
Alan Stern wrote:
> On Tue, 24 Jul 2007, Ron Gage wrote:
>
>
>> This is a good one to start with as it is seen literally hundreds of
>> times in the trace.
>>
>> 20in downn/a3.195VENDOR_ENDPOINT-
>> URB Header (length: 80)
>> SequenceNumber: 20
>> Function: 0019 (V
On Tue, 24 Jul 2007, Ron Gage wrote:
> This is a good one to start with as it is seen literally hundreds of
> times in the trace.
>
> 20in downn/a3.195VENDOR_ENDPOINT-
> URB Header (length: 80)
> SequenceNumber: 20
> Function: 0019 (VENDOR_ENDPOINT)
> PipeHandle:
On Tue, 24 Jul 2007, Ron Gage wrote:
> Greetings:
>
> I need some help here. I am trying to develop a driver for an
> "EnsureTechnologies Xyloc Model U-1" USB-based security device. It is
> basically an RFID receiver and matchbook sized serialized remote - the
> RFID receiver detects when th
Oliver Neukum wrote:
> Am Dienstag 24 Juli 2007 schrieb Ron Gage:
>
>> Anyhow, the device appears to require a non-standard function code in
>> the URB header, code 0019. SnoopyPro (yeah, on Windows) says this
>> function code is "Vendor Endpoint". Obviously, there isn't any current
>> way
Oliver Neukum wrote:
> Am Dienstag 24 Juli 2007 schrieb Ron Gage:
>
>> Anyhow, the device appears to require a non-standard function code in
>> the URB header, code 0019. SnoopyPro (yeah, on Windows) says this
>> function code is "Vendor Endpoint". Obviously, there isn't any current
>> way
Am Dienstag 24 Juli 2007 schrieb Ron Gage:
> Anyhow, the device appears to require a non-standard function code in
> the URB header, code 0019. SnoopyPro (yeah, on Windows) says this
> function code is "Vendor Endpoint". Obviously, there isn't any current
> way to send such a function code wit
Greetings:
I need some help here. I am trying to develop a driver for an
"EnsureTechnologies Xyloc Model U-1" USB-based security device. It is
basically an RFID receiver and matchbook sized serialized remote - the
RFID receiver detects when the remote is within range and reports back
to the
11 matches
Mail list logo
