[YARDStick] Yardstick One and Windows 10?

[Travis Lee]

Cool, thanks Dominic. I'll give it a test later tonight.

Curious about what you changed? I was trying to do some more research on it last night and did some USB tracing on it to try to determine what actually failed validation.

-----Original Message-----
From: Dominic Spill [mailto:dominicgs at gmail.com] 
Sent: Tuesday, May 03, 2016 6:12 AM
To: Travis Lee <eelsivart at gmail.com>
Cc: yardstick at greatscottgadgets.com
Subject: Re: [YARDStick] Yardstick One and Windows 10?

Hi,

I have built a test firmware for you and uploaded it here:
https://dominicspill.com/RfCatYS1CCBootloader.hex

You'll need a copy of the rfcat source too.

>From the rfcat/firmware directory, run the following:
wget https://dominicspill.com/RfCatYS1CCBootloader.hex
rfcat --bootloader --force
rfcat_bootloader /dev/RFCAT_BL_YS1 erase_all rfcat_bootloader /dev/RFCAT_BL_YS1 download RfCatYS1CCBootloader.hex rfcat_bootloader /dev/RFCAT_BL_YS1 verify RfCatYS1CCBootloader.hex && rfcat_bootloader /dev/RFCAT_BL_YS1 run

This should change the USB descriptors and hopefully Windows 10 will recognise the YARDStick One.

Let me know how it turns out.

Thanks,
  Dominic

On 2 May 2016 at 17:46, Dominic Spill <dominicgs at gmail.com> wrote:
> On 2 May 2016 at 17:19, Travis Lee <eelsivart at gmail.com> wrote:
>> It shows up in the Windows 10 device manager as: "Unknown USB Device (Invalid Configuration Descriptor)"
>
> That's what I thought it might say.  There's an off by one error in 
> the USB descriptors, I guess Windows 10 is more strict about this.
>
>> Yup, I have another system that works with the yardstick.
>
> I'm trying to build you a firmware binary so that you can test an 
> updated firmware to see if it fixes the problem.  Unfortunately I'm 
> flighting the compiler right now.  I'll upload something when I manage 
> to build it.
>
> Dominic
>
>> -----Original Message-----
>> From: Dominic Spill [mailto:dominicgs at gmail.com]
>> Sent: Monday, May 02, 2016 6:05 AM
>> To: Travis Lee <eelsivart at gmail.com>
>> Cc: yardstick at greatscottgadgets.com
>> Subject: Re: [YARDStick] Yardstick One and Windows 10?
>>
>> On 2 May 2016 at 06:48, Travis Lee <eelsivart at gmail.com> wrote:
>>> Yup, using Windows 10 as the host and the latest version of VMware Player. Other USB devices show up just fine and HackRF works just fine as well. I think its more of a Win 10 issue since the Yardstick works just fine on Windows 7 as  the host and VMware Player. Have a colleague that has the exact same issue on this Windows 10 system as well with his Yardstick.
>>
>> Let's assume that this is a Windows 10 issue then, and we can ignore VMware Player for the time being.
>>
>> Does the device show up in the Windows device manager?
>>
>> Do you have access to a system that still works with YARDStick One that you could use to update firmware?
>>
>> Thanks,
>>   Dominic
>>
>>> -----Original Message-----
>>> From: Dominic Spill [mailto:dominicgs at gmail.com]
>>> Sent: Saturday, April 30, 2016 4:03 AM
>>> To: Travis Lee <eelsivart at gmail.com>
>>> Cc: yardstick at greatscottgadgets.com
>>> Subject: Re: [YARDStick] Yardstick One and Windows 10?
>>>
>>> On 28 April 2016 at 23:45, Travis Lee <eelsivart at gmail.com> wrote:
>>>> I have recently acquired a Yardstick One and it works fine on Win7 
>>>> with VMware Player, however, it is not recognized on a Win 10 box 
>>>> with VMware Player. Win 10 says it is an unrecognized device and it 
>>>> doesn’t show up in VMware Player’s removable devices.
>>>
>>> Are you using Windows 10 as the host OS for VMware Player?  Do all other USB devices show up in the VMware list?
>>>
>>>> Have other people had this problem and if so, are there any solutions?
>>>
>>> I have never used VMware Player, but looking online for others with this problem, I see recommendations to upgrade to the latest version of VMware Player, are you using the latest version?
>>>
>>> Also, this forum post:
>>> https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insi
>>> de
>>> r_devices/win-10-installed-in-vmware-doesnt-detect-usb/ff0b08dc-3192
>>> -4
>>> 4c6-97e5-e4a8a0ba1110?auth=1 suggests that changing the USB 
>>> controller in VMware to be USB 2.0 may help.  Could you try that?
>>>
>>> Thanks,
>>>   Dominic
>>>
>>