[YARDStick] Yardstick One and Windows 10?

Wed May 4 12:40:11 EDT 2016

On 4 May 2016 at 17:14, Travis Lee <eelsivart at gmail.com> wrote:
> I don't have anything called RFCAT* in /dev
>
> This is what the YS1 shows up as: Bus 002 Device 014: ID 1d50:605b OpenMoko, Inc.
>
> Also, I am doing this through a VMware Player on a Win7 host.

That ID should change when the YS1 is in bootloader mode, but you'll
need to add an extra rule to your vmware setup to pass it through.

> Nothing related to rfcat in /etc/udev/rules.d

There's a file in the RfCat repository called 20-rfcat.rules, it's in
asubdirectory called etc/udev/rules.d, it will help things if you copy
it to /etc/udev/rules.d (I know that sentence looks confusing, not the
leading / on the second one).

> This line was in /var/messages too: "usb 2-2.1: config 1 descriptor has 1 excess byte, ignoring"

That warning goes away with this fix.

Unfortunately, the bad news is that I was able to boot a Windows 10
system today and, even with this firmware change, I saw the error
message that you describe.  I'll keep trying to find what's wrong with
the USB descriptors.

Thanks,
  Dominic

> -----Original Message-----
> From: Dominic Spill [mailto:dominicgs at gmail.com]
> Sent: Wednesday, May 04, 2016 2:04 AM
> To: Travis Lee <eelsivart at gmail.com>
> Cc: yardstick at greatscottgadgets.com
> Subject: Re: [YARDStick] Yardstick One and Windows 10?
>
> On 4 May 2016 at 06:34, Travis Lee <eelsivart at gmail.com> wrote:
>> Trying to get the rfcat_bootloader to work and I keep getting:
>>
>> "Something is talking to the RfCat dongle (Modem Manager, most likely).  Retrying again after 5 seconds.  This can take a minute, please be patient."
>>
>> It looks like it is going into the bootloader mode (solid LED), but I
>> don't see a /dev/ RFCAT_BL_YS1
>
> Do you have anything called RFCAT_BL_ in /dev ?
> What is the USB ID of the YS1 when it is in bootloader mode?
> Do you have a file called /etc/udev/rules.d/20-rfcat.rules (or something like that?
>
> It may be that your YS1 has a different USB ID when in bootloader mode than the one we're expecting.
>
> Thanks,
>   Dominic
>
>> -----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-ins
>>>>> ide
>>>>> r_devices/win-10-installed-in-vmware-doesnt-detect-usb/ff0b08dc-319
>>>>> 2-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
>>>>>
>>>>
>>
>