Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

NTDEV
21

David Craig wrote:

I see someone did it correct, but it seems someone didn’t. Maybe Microsoft
has that driver just to make it hard for the bad designs to work. It sounds
like something I would want to do if I had the power and worked at
Microsoft. No one has said what version information is available for the
‘problem’ driver. Is it Cypress or Microsoft or another company with a bad
design who happened to get it signed?

Actually, the original poster said it was a “KWorld” device. A quick
web search shows this is a Taiwanese company doing TV stuff. They made
a mistake, and Microsoft “enabled” it.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

22

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Tim Roberts[SMTP:xxxxx@probo.com]
Reply To: Windows System Software Devs Interest List
Sent: Tuesday, March 20, 2007 6:43 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

Michal Vodicka wrote:
> I found whole firmware loader idea quite funny (especially the part which changes device VID&&PID)…

Really? It is by far the simplest solution to this problem. It’s
certainly possible to use the same VID/PID for unconfigured and
configured devices, by having the driver test for the presence of a
custom vendor command, but you still need to re-enumerate because the
descriptors have to change. Might as well let PnP do some of the work.

OK, I never worked with Cypress boards before. I was just asked to the solve problem created by automatically installed driver. Automatical VID/PID change made it really funny.

The idea isn’t so bad until somebody uses it for default VID/PID. And until MS signs such a driver and puts it to Windows update site. It had to occurs sooner or later, according to Murphy’s law. Which means the idea is flawed :wink:

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

23

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Tim Roberts[SMTP:xxxxx@probo.com]
Reply To: Windows System Software Devs Interest List
Sent: Tuesday, March 20, 2007 6:58 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

The FX2 has very basic firmware built in. At boot time, that firmware
goes out to look for an EEPROM to supply its initial USB descriptors.
If no EEPROM is found, it falls back to the 04B4/8613 that caused the
trouble to begin with. Any designer who plans to release his device
into the wild will supplies a small EEPROM with descriptors that have a
custom VID/PID that identifies their specific unconfigured device. This
triggers the customized firmware loader, which loads the real firmware
and the real descriptors.

Yep, this makes sense. But coworker who encountered the problem used a board with no EEPROM just for development. He wanted to use default fw loader but WHQL signed driver from Windows update had precedence.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

24

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of David Craig[SMTP:xxxxx@yoshimuni.com]
Reply To: Windows System Software Devs Interest List
Sent: Tuesday, March 20, 2007 9:39 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

I see someone did it correct, but it seems someone didn’t. Maybe Microsoft
has that driver just to make it hard for the bad designs to work. It sounds
like something I would want to do if I had the power and worked at
Microsoft.

Use Hanlon’s razor: Never attribute to malice that which can be adequately explained by stupidity.

No one has said what version information is available for the
‘problem’ driver. Is it Cypress or Microsoft or another company with a bad
design who happened to get it signed?

Another company. It was some sound device or something like this.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

25

Can’t you use devcon?

This procedure works for PCI devices, it should work for USB too.

  1. devcon update “USB\VID_XXXX&PID_YYYY”
    2. devcon disable “USB\VID_XXXX&PID_YYYY”
    3. devcon enable “USB\VID_XXXX&PID_YYYY”

    Have a nice day
    GV

    ----- Original Message -----
    From: “Michal Vodicka”
    To: “Windows System Software Devs Interest List”
    Sent: Tuesday, March 20, 2007 1:53 PM
    Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A
    (FX2LP) VID 0x04B4 PID 0x8613

    > ----------
    > From:
    > xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
    > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
    > Reply To: Windows System Software Devs Interest List
    > Sent: Tuesday, March 20, 2007 10:04 AM
    > To: Windows System Software Devs Interest List
    > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
    > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
    >
    > 1. If this is truly a Microsoft signed driver (and not a virus) that is in
    > their driver compatibility list, where do I send a request to ask if
    > Microsoft would please consider removing this driver from its update site?
    >
    I hope the WHQL signature was really coming from MS. Which, of course,
    doesn’t necessarily mean it isn’t a virus :wink:

    > Our product developers and manufacturing engineers, who know nothing
    > about system files or registry entries, will push the “recommended” button
    > and I can’t seem to come up with a really easy way to load our driver once
    > the “recommended” path is taken. Any suggestions would be greatly
    > appreciated.
    >
    We did it following way:

    - identify the firmware loader driver entry in the registry
    (HKLM\System\CCS\Services<fw_loader_name>
    - unplug Cypress board(s)
    - change fw loader Start value from 3 to 4
    - plug the board back
    - in the Device Manager, board is marked with question mark because OS has
    problem loading driver
    - right click, Update driver and now it is possible to manually select
    something else than rogue fw loader
    - it is necessary to repeat process for every port where it was plugged

    You can make whole process a bit easier by creating .reg file which changes
    the Start value but beware about systems where rogue fw loader was never
    installed. For product developers above description should be enough, for
    manufacturing engineers add screenshots and for marketing persons (if
    involved) create Power Point presentation :wink:

    HTH

    Best regards,

    Michal Vodicka
    UPEK, Inc.
    [xxxxx@upek.com, http://www.upek.com]

    —
    Questions? First check the Kernel Driver FAQ at
    http://www.osronline.com/article.cfm?id=256

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer</fw_loader_name>
26

Will “devcon update” work if you need to replace WHQL signed driver with non-signed one?

Next problem is there are two VID/PID pairs involved and only uninteresting one is loaded. If #1 works, manual unplug/plug or board reset will be necessary.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
Reply To: Windows System Software Devs Interest List
Sent: Tuesday, March 20, 2007 10:38 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

Can’t you use devcon?

This procedure works for PCI devices, it should work for USB too.

  1. devcon update “USB\VID_XXXX&PID_YYYY”
    > 2. devcon disable “USB\VID_XXXX&PID_YYYY”
    > 3. devcon enable “USB\VID_XXXX&PID_YYYY”
    >
    > Have a nice day
    > GV
    >
    >
    >
    > ----- Original Message -----
    > From: “Michal Vodicka”
    > To: “Windows System Software Devs Interest List”
    > Sent: Tuesday, March 20, 2007 1:53 PM
    > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A
    > (FX2LP) VID 0x04B4 PID 0x8613
    >
    >
    > > ----------
    > > From:
    > > xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
    > > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
    > > Reply To: Windows System Software Devs Interest List
    > > Sent: Tuesday, March 20, 2007 10:04 AM
    > > To: Windows System Software Devs Interest List
    > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
    > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
    > >
    > > 1. If this is truly a Microsoft signed driver (and not a virus) that is in
    > > their driver compatibility list, where do I send a request to ask if
    > > Microsoft would please consider removing this driver from its update site?
    > >
    > I hope the WHQL signature was really coming from MS. Which, of course,
    > doesn’t necessarily mean it isn’t a virus :wink:
    >
    > > Our product developers and manufacturing engineers, who know nothing
    > > about system files or registry entries, will push the “recommended” button
    > > and I can’t seem to come up with a really easy way to load our driver once
    > > the “recommended” path is taken. Any suggestions would be greatly
    > > appreciated.
    > >
    > We did it following way:
    >
    > - identify the firmware loader driver entry in the registry
    > (HKLM\System\CCS\Services<fw_loader_name>
    > - unplug Cypress board(s)
    > - change fw loader Start value from 3 to 4
    > - plug the board back
    > - in the Device Manager, board is marked with question mark because OS has
    > problem loading driver
    > - right click, Update driver and now it is possible to manually select
    > something else than rogue fw loader
    > - it is necessary to repeat process for every port where it was plugged
    >
    > You can make whole process a bit easier by creating .reg file which changes
    > the Start value but beware about systems where rogue fw loader was never
    > installed. For product developers above description should be enough, for
    > manufacturing engineers add screenshots and for marketing persons (if
    > involved) create Power Point presentation :wink:
    >
    > HTH
    >
    > Best regards,
    >
    > Michal Vodicka
    > UPEK, Inc.
    > [xxxxx@upek.com, http://www.upek.com]
    >
    > —
    > Questions? First check the Kernel Driver FAQ at
    > http://www.osronline.com/article.cfm?id=256
    >
    > To unsubscribe, visit the List Server section of OSR Online at
    > http://www.osronline.com/page.cfm?name=ListServer
    >
    >
    > —
    > Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
    >
    > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
    ></fw_loader_name>
27

----- Original Message -----
From: “Michal Vodicka”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 20, 2007 2:52 PM
Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A
(FX2LP) VID 0x04B4 PID 0x8613

Will “devcon update” work if you need to replace WHQL signed driver with
non-signed one?

–GV–
I haven’t tested it with an unsigned driver. But I’d bet it works.
–GV–

Next problem is there are two VID/PID pairs involved and only uninteresting
one is loaded. If #1 works, manual unplug/plug or board reset will be
necessary.

–GV–
devcon disable HWID allows you to disable any device matching the pattern in
HWID, in the same way as you would disable a disable from device manager.
For PCI devices it works perfectly (it’s the way I update a PCI driver
during development: put a new binary in system32\drivers, and then
disable/enable the device itself).

Have a nice day
GV

–GV–

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

> ----------
> From:
> xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Tuesday, March 20, 2007 10:38 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
>
> Can’t you use devcon?
>
> This procedure works for PCI devices, it should work for USB too.
>
> 1. devcon update “USB\VID_XXXX&PID_YYYY”
> 2. devcon disable “USB\VID_XXXX&PID_YYYY”
> 3. devcon enable “USB\VID_XXXX&PID_YYYY”
>
> Have a nice day
> GV
>
>
>
> ----- Original Message -----
> From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, March 20, 2007 1:53 PM
> Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A
> (FX2LP) VID 0x04B4 PID 0x8613
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Tuesday, March 20, 2007 10:04 AM
> > To: Windows System Software Devs Interest List
> > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> >
> > 1. If this is truly a Microsoft signed driver (and not a virus) that is
> > in
> > their driver compatibility list, where do I send a request to ask if
> > Microsoft would please consider removing this driver from its update
> > site?
> >
> I hope the WHQL signature was really coming from MS. Which, of course,
> doesn’t necessarily mean it isn’t a virus :wink:
>
> > Our product developers and manufacturing engineers, who know nothing
> > about system files or registry entries, will push the “recommended”
> > button
> > and I can’t seem to come up with a really easy way to load our driver
> > once
> > the “recommended” path is taken. Any suggestions would be greatly
> > appreciated.
> >
> We did it following way:
>
> - identify the firmware loader driver entry in the registry
> (HKLM\System\CCS\Services<fw_loader_name>
> - unplug Cypress board(s)
> - change fw loader Start value from 3 to 4
> - plug the board back
> - in the Device Manager, board is marked with question mark because OS has
> problem loading driver
> - right click, Update driver and now it is possible to manually select
> something else than rogue fw loader
> - it is necessary to repeat process for every port where it was plugged
>
> You can make whole process a bit easier by creating .reg file which
> changes
> the Start value but beware about systems where rogue fw loader was never
> installed. For product developers above description should be enough, for
> manufacturing engineers add screenshots and for marketing persons (if
> involved) create Power Point presentation :wink:
>
> HTH
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer</fw_loader_name>

28

Hello Gianluca,
Thanks for the advice. Unfortunately, for whatever reason, my development
hardware causes the KWorld firmware to connect, disconnect, connect…
Because of this, devcon reports back that it cannot find the targeted
hardware. That’s the reason why I don’t see the hardware in the device
manager. For now I’m generating a README outlining Michal’s advice (editing
the Registry). My original README was to have end-users who were unfortunate
enough to fall into this dilemma, muck with system files and directories,
but I think that modifying the Registry is a bit more forward. Thanks to
everyone for all the help and support.

Motz

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-281222-
xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
Sent: Tuesday, March 20, 2007 3:02 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

----- Original Message -----
From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, March 20, 2007 2:52 PM
> Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A
> (FX2LP) VID 0x04B4 PID 0x8613
>
>
> Will “devcon update” work if you need to replace WHQL signed driver with
> non-signed one?
>
> --GV–
> I haven’t tested it with an unsigned driver. But I’d bet it works.
> --GV–
>
>
> Next problem is there are two VID/PID pairs involved and only
> uninteresting
> one is loaded. If #1 works, manual unplug/plug or board reset will be
> necessary.
>
> --GV–
> devcon disable HWID allows you to disable any device matching the pattern
> in
> HWID, in the same way as you would disable a disable from device manager.
> For PCI devices it works perfectly (it’s the way I update a PCI driver
> during development: put a new binary in system32\drivers, and then
> disable/enable the device itself).
>
> Have a nice day
> GV
>
> --GV–
>
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:bounce-281217-
> xxxxx@lists.osr.com]
> > on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Tuesday, March 20, 2007 10:38 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> >
> > Can’t you use devcon?
> >
> > This procedure works for PCI devices, it should work for USB too.
> >
> > 1. devcon update “USB\VID_XXXX&PID_YYYY”
> > 2. devcon disable “USB\VID_XXXX&PID_YYYY”
> > 3. devcon enable “USB\VID_XXXX&PID_YYYY”
> >
> > Have a nice day
> > GV
> >
> >
> >
> > ----- Original Message -----
> > From: “Michal Vodicka”
> > To: “Windows System Software Devs Interest List”
> > Sent: Tuesday, March 20, 2007 1:53 PM
> > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A
> > (FX2LP) VID 0x04B4 PID 0x8613
> >
> >
> > > ----------
> > > From:
> > > xxxxx@lists.osr.com[SMTP:bounce-281159-
> xxxxx@lists.osr.com]
> > > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
> > > Reply To: Windows System Software Devs Interest List
> > > Sent: Tuesday, March 20, 2007 10:04 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> > >
> > > 1. If this is truly a Microsoft signed driver (and not a virus) that
> is
> > > in
> > > their driver compatibility list, where do I send a request to ask if
> > > Microsoft would please consider removing this driver from its update
> > > site?
> > >
> > I hope the WHQL signature was really coming from MS. Which, of course,
> > doesn’t necessarily mean it isn’t a virus :wink:
> >
> > > Our product developers and manufacturing engineers, who know nothing
> > > about system files or registry entries, will push the “recommended”
> > > button
> > > and I can’t seem to come up with a really easy way to load our driver
> > > once
> > > the “recommended” path is taken. Any suggestions would be greatly
> > > appreciated.
> > >
> > We did it following way:
> >
> > - identify the firmware loader driver entry in the registry
> > (HKLM\System\CCS\Services<fw_loader_name>
> > - unplug Cypress board(s)
> > - change fw loader Start value from 3 to 4
> > - plug the board back
> > - in the Device Manager, board is marked with question mark because OS
> has
> > problem loading driver
> > - right click, Update driver and now it is possible to manually select
> > something else than rogue fw loader
> > - it is necessary to repeat process for every port where it was plugged
> >
> > You can make whole process a bit easier by creating .reg file which
> > changes
> > the Start value but beware about systems where rogue fw loader was never
> > installed. For product developers above description should be enough,
> for
> > manufacturing engineers add screenshots and for marketing persons (if
> > involved) create Power Point presentation :wink:
> >
> > HTH
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</fw_loader_name>

29

Hi everyone,

I’ve raised this issue to the appropriate folks internally. They seem
to understand the problem (but hadn’t heard of it). I’ll let you know
if there is any additional news.

Thanks,

Henry Gabryjelski
Senior Software Development Engineer
US - Windows Device Experience
Microsoft Corporation

-----Original Message-----
From: John Matsumoto [mailto:xxxxx@surfaceoptics.com]
Sent: Wednesday, March 21, 2007 12:28 AM
Subject: RE: Issue with Vista 64-bit recognizing Cypress CY7C68013A
(FX2LP) VID 0x04B4 PID 0x8613

Hello Gianluca,
Thanks for the advice. Unfortunately, for whatever reason, my
development
hardware causes the KWorld firmware to connect, disconnect, connect…
Because of this, devcon reports back that it cannot find the targeted
hardware. That’s the reason why I don’t see the hardware in the device
manager. For now I’m generating a README outlining Michal’s advice
(editing
the Registry). My original README was to have end-users who were
unfortunate
enough to fall into this dilemma, muck with system files and
directories,
but I think that modifying the Registry is a bit more forward. Thanks to
everyone for all the help and support.

Motz

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-281222-
xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
Sent: Tuesday, March 20, 2007 3:02 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

----- Original Message -----
From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, March 20, 2007 2:52 PM
> Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A
> (FX2LP) VID 0x04B4 PID 0x8613
>
>
> Will “devcon update” work if you need to replace WHQL signed driver
with
> non-signed one?
>
> --GV–
> I haven’t tested it with an unsigned driver. But I’d bet it works.
> --GV–
>
>
> Next problem is there are two VID/PID pairs involved and only
> uninteresting
> one is loaded. If #1 works, manual unplug/plug or board reset will be
> necessary.
>
> --GV–
> devcon disable HWID allows you to disable any device matching the
pattern
> in
> HWID, in the same way as you would disable a disable from device
manager.
> For PCI devices it works perfectly (it’s the way I update a PCI driver
> during development: put a new binary in system32\drivers, and then
> disable/enable the device itself).
>
> Have a nice day
> GV
>
> --GV–
>
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:bounce-281217-
> xxxxx@lists.osr.com]
> > on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Tuesday, March 20, 2007 10:38 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> >
> > Can’t you use devcon?
> >
> > This procedure works for PCI devices, it should work for USB too.
> >
> > 1. devcon update “USB\VID_XXXX&PID_YYYY”
> > 2. devcon disable “USB\VID_XXXX&PID_YYYY”
> > 3. devcon enable “USB\VID_XXXX&PID_YYYY”
> >
> > Have a nice day
> > GV
> >
> >
> >
> > ----- Original Message -----
> > From: “Michal Vodicka”
> > To: “Windows System Software Devs Interest List”

> > Sent: Tuesday, March 20, 2007 1:53 PM
> > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A
> > (FX2LP) VID 0x04B4 PID 0x8613
> >
> >
> > > ----------
> > > From:
> > > xxxxx@lists.osr.com[SMTP:bounce-281159-
> xxxxx@lists.osr.com]
> > > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
> > > Reply To: Windows System Software Devs Interest List
> > > Sent: Tuesday, March 20, 2007 10:04 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> > >
> > > 1. If this is truly a Microsoft signed driver (and not a virus)
that
> is
> > > in
> > > their driver compatibility list, where do I send a request to ask
if
> > > Microsoft would please consider removing this driver from its
update
> > > site?
> > >
> > I hope the WHQL signature was really coming from MS. Which, of
course,
> > doesn’t necessarily mean it isn’t a virus :wink:
> >
> > > Our product developers and manufacturing engineers, who know
nothing
> > > about system files or registry entries, will push the
“recommended”
> > > button
> > > and I can’t seem to come up with a really easy way to load our
driver
> > > once
> > > the “recommended” path is taken. Any suggestions would be greatly
> > > appreciated.
> > >
> > We did it following way:
> >
> > - identify the firmware loader driver entry in the registry
> > (HKLM\System\CCS\Services<fw_loader_name>
> > - unplug Cypress board(s)
> > - change fw loader Start value from 3 to 4
> > - plug the board back
> > - in the Device Manager, board is marked with question mark because
OS
> has
> > problem loading driver
> > - right click, Update driver and now it is possible to manually
select
> > something else than rogue fw loader
> > - it is necessary to repeat process for every port where it was
plugged
> >
> > You can make whole process a bit easier by creating .reg file which
> > changes
> > the Start value but beware about systems where rogue fw loader was
never
> > installed. For product developers above description should be
enough,
> for
> > manufacturing engineers add screenshots and for marketing persons
(if
> > involved) create Power Point presentation :wink:
> >
> > HTH
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</fw_loader_name>

30

Thanks, Henry.

As for “but hand’t heard of it” part. No surprise. There is no easy or straightforward way how to report this kind of problems to MS. At least I don’t know about it. PSS is long and painful process and I use it only for serious problems (OS bugs) which have direct impact to our products. They always want business case, anyway.

For the rest I found this list as more efficient solution. I really appreciate when you and other MS people here raise issues internally; I understand it is pure voluntary. I also understand it is very hard to built efficient support for a big company; the worst part is to distinguish real problems from garbage. Anyway, it’d be nice if there is an official way how developers could easily report (potential) bugs and they can be sure somebody tries to solve it. Writing good error report is time consuming and I personally was very disapointed how they were handled during Vista beta testing.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Henry Gabryjelski[SMTP:xxxxx@microsoft.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, March 22, 2007 5:16 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

Hi everyone,

I’ve raised this issue to the appropriate folks internally. They seem
to understand the problem (but hadn’t heard of it). I’ll let you know
if there is any additional news.

Thanks,

Henry Gabryjelski
Senior Software Development Engineer
US - Windows Device Experience
Microsoft Corporation

-----Original Message-----
From: John Matsumoto [mailto:xxxxx@surfaceoptics.com]
Sent: Wednesday, March 21, 2007 12:28 AM
Subject: RE: Issue with Vista 64-bit recognizing Cypress CY7C68013A
(FX2LP) VID 0x04B4 PID 0x8613

Hello Gianluca,
Thanks for the advice. Unfortunately, for whatever reason, my
development
hardware causes the KWorld firmware to connect, disconnect, connect…
Because of this, devcon reports back that it cannot find the targeted
hardware. That’s the reason why I don’t see the hardware in the device
manager. For now I’m generating a README outlining Michal’s advice
(editing
the Registry). My original README was to have end-users who were
unfortunate
enough to fall into this dilemma, muck with system files and
directories,
but I think that modifying the Registry is a bit more forward. Thanks to
everyone for all the help and support.

Motz

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-281222-
> xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
> Sent: Tuesday, March 20, 2007 3:02 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
>
>
> ----- Original Message -----
> From: “Michal Vodicka”
> > To: “Windows System Software Devs Interest List”
> > Sent: Tuesday, March 20, 2007 2:52 PM
> > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A
> > (FX2LP) VID 0x04B4 PID 0x8613
> >
> >
> > Will “devcon update” work if you need to replace WHQL signed driver
> with
> > non-signed one?
> >
> > --GV–
> > I haven’t tested it with an unsigned driver. But I’d bet it works.
> > --GV–
> >
> >
> > Next problem is there are two VID/PID pairs involved and only
> > uninteresting
> > one is loaded. If #1 works, manual unplug/plug or board reset will be
> > necessary.
> >
> > --GV–
> > devcon disable HWID allows you to disable any device matching the
> pattern
> > in
> > HWID, in the same way as you would disable a disable from device>
> manager.
> > For PCI devices it works perfectly (it’s the way I update a PCI driver
> > during development: put a new binary in system32\drivers, and then
> > disable/enable the device itself).
> >
> > Have a nice day
> > GV
> >
> > --GV–
> >
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> >
> > > ----------
> > > From:
> > > xxxxx@lists.osr.com[SMTP:bounce-281217-
> > xxxxx@lists.osr.com]
> > > on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
> > > Reply To: Windows System Software Devs Interest List
> > > Sent: Tuesday, March 20, 2007 10:38 PM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> > >
> > > Can’t you use devcon?
> > >
> > > This procedure works for PCI devices, it should work for USB too.
> > >
> > > 1. devcon update “USB\VID_XXXX&PID_YYYY”
> > > 2. devcon disable “USB\VID_XXXX&PID_YYYY”
> > > 3. devcon enable “USB\VID_XXXX&PID_YYYY”
> > >
> > > Have a nice day
> > > GV
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: “Michal Vodicka”
> > > To: “Windows System Software Devs Interest List”
>
> > > Sent: Tuesday, March 20, 2007 1:53 PM
> > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > CY7C68013A
> > > (FX2LP) VID 0x04B4 PID 0x8613
> > >
> > >
> > > > ----------
> > > > From:
> > > > xxxxx@lists.osr.com[SMTP:bounce-281159-
> > xxxxx@lists.osr.com]
> > > > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
> > > > Reply To: Windows System Software Devs Interest List
> > > > Sent: Tuesday, March 20, 2007 10:04 AM
> > > > To: Windows System Software Devs Interest List
> > > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> > > >
> > > > 1. If this is truly a Microsoft signed driver (and not a virus)
> that
> > is
> > > > in
> > > > their driver compatibility list, where do I send a request to ask
> if
> > > > Microsoft would please consider removing this driver from its
> update
> > > > site?
> > > >
> > > I hope the WHQL signature was really coming from MS. Which, of
> course,
> > > doesn’t necessarily mean it isn’t a virus :wink:
> > >
> > > > Our product developers and manufacturing engineers, who know
> nothing
> > > > about system files or registry entries, will push the
> “recommended”
> > > > button
> > > > and I can’t seem to come up with a really easy way to load our
> driver
> > > > once
> > > > the “recommended” path is taken. Any suggestions would be greatly
> > > > appreciated.
> > > >
> > > We did it following way:
> > >
> > > - identify the firmware loader driver entry in the registry
> > > (HKLM\System\CCS\Services<fw_loader_name>
> > > - unplug Cypress board(s)
> > > - change fw loader Start value from 3 to 4
> > > - plug the board back
> > > - in the Device Manager, board is marked with question mark because
> OS
> > has
> > > problem loading driver
> > > - right click, Update driver and now it is possible to manually
> select
> > > something else than rogue fw loader
> > > - it is necessary to repeat process for every port where it was
> plugged
> > >
> > > You can make whole process a bit easier by creating .reg file which
> > > changes
> > > the Start value but beware about systems where rogue fw loader was
> never
> > > installed. For product developers above description should be
> enough,
> > for
> > > manufacturing engineers add screenshots and for marketing persons
> (if
> > > involved) create Power Point presentation :wink:
> > >
> > > HTH
> > >
> > > Best regards,
> > >
> > > Michal Vodicka
> > > UPEK, Inc.
> > > [xxxxx@upek.com, http://www.upek.com]
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256&gt;
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> > >
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> > >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
></fw_loader_name>

31

> As for “but hand’t heard of it” part. No surprise. There is no easy or

straightforward way how to report this kind of problems to MS. At
least I
don’t know about it. PSS is long and painful process and I use it only
for
serious problems (OS bugs) which have direct impact to our products.
They
always want business case, anyway.

IMHO, PSS process is bureaucracy. You first need to explain the problem
to the 1st and possibly 2nd line support. At first, they might well have
no clue what you are talking about. It may take a couple of days or more
to reach the right people. By that time, the OEM may already get very
angry on you. We only use PSS when OEM is requesting an official
tracking number/channel so that they can deal with MSFT directly later
on.

If your team has direct contact with Microsoft, life will be much
easier. For example, I could just bounce an email to ali’s team or pick
up my phone to chat with them like hey, why Abc is doing xyz. They would
say, yes, this is known and have been fixed at… The issues and
concerns outside of their component can be brought up to the right
people in the order of hours if it is bad enough regardless where they
are in the OS. This is my experience with their Base Video, NDIS, and
the Stack teams. If the issue can’t be addressed between developers, you
can escalate to their managers and/or director. I think other teams in
MSFT would do the same. They are very helpful and business driven. It’s
overall a pleasure to work with Bill’s staffs. Our experience with some
opensource OS maintainers is exactly the opposite-:frowning:

Calvin Guan (expiring DDK MVP)
NetXtreme NTX Miniport
Broadcom Corporation
Connecting Everything(r)

32

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Calvin (Hao) Guan[SMTP:xxxxx@broadcom.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, March 22, 2007 9:20 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613

IMHO, PSS process is bureaucracy. You first need to explain the problem
to the 1st and possibly 2nd line support. At first, they might well have
no clue what you are talking about. It may take a couple of days or more
to reach the right people.

You’re rigth. In my experience it can take weeks.

By that time, the OEM may already get very
angry on you. We only use PSS when OEM is requesting an official
tracking number/channel so that they can deal with MSFT directly later
on.

It is good reason as OEMs can push the issue to be solved faster. Next advantage is OEMs may not trust us it is MS problem and official SR number helps to convince them.

If your team has direct contact with Microsoft, life will be much
easier.

I believe it is much easier but it isn’t the way how should things work, right? At least, it shouldn’t be necessary. I guess it is MS interest to be informed about (possible) bugs in their OSes. Especially when they released balf-baked OS of beta quality. If I encounter an issue which doesn’t have direct impact to my work, as the one which started this thread, what can I do? Report it here and hope some of participating MS people handles it. It doesn’t look very professional to me.

I think other teams in
MSFT would do the same. They are very helpful and business driven. It’s
overall a pleasure to work with Bill’s staffs. Our experience with some
opensource OS maintainers is exactly the opposite-:frowning:

Once you get right people, yes. Which is the problem.

Anyway, what if you need a hotfix? Don’t you need to use PSS for it? I just have few opened issues considered as bugs and wait until (and if) they approve bussiness justification and make the fix.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]