[YARDStick] Yardstick One and Windows 10?

[Travis Lee]

So far so good on Win 10 with the following changes you discovered:

wLength = 32
EP0_MAX_PACKET_SIZE = 64

Only time will tell if there are any functional issues with it, but so far some basic tests seem to work okay.

Thanks!!


-----Original Message-----
From: Dominic Spill [mailto:dominicgs at gmail.com] 
Sent: Friday, May 06, 2016 11:49 AM
To: Travis Lee <eelsivart at gmail.com>
Subject: Re: [YARDStick] Yardstick One and Windows 10?

Ok, same URL as before.  There's a working firmware with only a single change from my previous one (two changes from the main repo).

The change is that the EP0 maximum packet size is now 64 bytes, not 32.  32 is perfectly valid within the USB spec, but for some reason it's not allowing it.  I'll have to investigate further.

Dominic

On 6 May 2016 at 19:19, Dominic Spill <dominicgs at gmail.com> wrote:
> On 6 May 2016 at 19:13, Travis Lee <eelsivart at gmail.com> wrote:
>> What did you change on it?
>
> Everything!
>
> I zeroed out the strings, changed one of the string descriptors, the
> EP0 packet size, the interface and device classes, the EP poll 
> interval and removed the device qualifier section.
>
> I don't even know if this version works with RfCat yet.
>
>> From: Dominic Spill [mailto:dominicgs at gmail.com]
>> Sent: Friday, May 06, 2016 10:57 AM
>>
>>
>> To: Travis Lee <eelsivart at gmail.com>
>> Subject: RE: [YARDStick] Yardstick One and Windows 10?
>>
>>
>>
>> I have a firmware that doesn't error, but I'm not happy with it. It's 
>> at the same URL as the previous one that I sent you.
>>
>> On 6 May 2016 6:36 p.m., "Travis Lee" <eelsivart at gmail.com> wrote:
>>
>> I tried that as well, setting all the string indexes to 0. No luck 
>> with that.
>>
>>
>>
>> I used MS Message Analyzer
>> (https://www.microsoft.com/en-us/download/details.aspx?id=44226)
>>
>>
>>
>> -Install it
>>
>> -Start a new session
>>
>> -Choose the USB 3 profile
>>
>> -Start the session
>>
>> -Plug in the YS1
>>
>> -You should see all the requests/responses
>>
>> -Stop the session
>>
>>
>>
>> Another option is using logman to capture the trace and then using 
>> netmon to view it. Step by step instructions here:
>>
>>
>>
>> https://blogs.msdn.microsoft.com/usbcoreblog/2012/08/07/how-to-captur
>> e-and-read-usb-etw-traces-in-windows-8/
>>
>>
>>
>>
>>