Author Topic: firmware updating  (Read 5603 times)

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
firmware updating
« on: July 07, 2016, 05:16:55 AM »
My CleO works with a NerO card and most of the demos work; but My Win 7 computer steadfastly won't recognise the CleO for updates when directly connected; Zadig doesn't help; the Vid/pid are not recognised by windows as a valid usb device.
Do I have a faulty CleO?

prashanthb

  • Full Member
  • ***
  • Posts: 23
    • View Profile
Re: firmware updating
« Reply #1 on: July 07, 2016, 10:20:15 AM »
Hi David,

May I know as whether you are able to notice "WinUsb Device" in your windows device manager. Or does it report unknown device.

Kindly give us the below information for further analysis,

1. PC configuration. Eg: Windows version, chipset details
2. CleO package version. Eg: CleO 1.0.1 or CleO 1.0.0 or Alpha
3. CleO firmware version - version number displayed on the bootup screen


Best Regards
Prashanth B

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
Re: firmware updating
« Reply #2 on: July 07, 2016, 12:12:05 PM »
Hi Prashanth:

It shows "Unknown Device" in Device Manager
Machine is Thinkpad W520 with Intel i7-2620M CPU 16 Gb RAM 1TB SSD
CleO package 1.0.1
Firmware on Cleo Boot Screen Version 1.0.0 D164D457 93321826

Hope this is what you need..

cheers
dt..

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
Re: firmware updating
« Reply #3 on: July 07, 2016, 01:23:32 PM »
oops!

Thinkpad is uunning Windows 7 pro, SP 1

forgot about that...

cheers
dt..

NeilMan

  • Full Member
  • ***
  • Posts: 19
    • View Profile
Re: firmware updating
« Reply #4 on: July 07, 2016, 06:46:43 PM »
Well I tried the new package including the new PCTool on my Windows 7 64-bit desktop machine and tried to see if it might fix my duff Cleo.

Plugged Cleo in, got a new USB device "working properly", fired up PCTool, located the update firmware button, clicked it and Bam screen blacked out and the PC rebooted itself.

I daren't try it again with my working Cleos in case it kills them.  :(

I don't suppose there is an Apple (iMac) version is there (Mavericks)?

prashanthb

  • Full Member
  • ***
  • Posts: 23
    • View Profile
Re: firmware updating
« Reply #5 on: July 12, 2016, 11:07:27 AM »
Hi Neil,

If possible kindly send us the core dump for analysis. Strange that previous time only dfu-utils compatibility was the issue with the not working module.


Best Regards
Prashanth B

Fred Dart

  • CEO of FTDI
  • Administrator
  • Full Member
  • *****
  • Posts: 74
  • Welcome...
    • View Profile
    • FTDI CleO Page
Re: firmware updating
« Reply #6 on: July 12, 2016, 11:30:25 AM »
I think it's the not working module he's been trying...

prashanthb

  • Full Member
  • ***
  • Posts: 23
    • View Profile
Re: firmware updating
« Reply #7 on: July 12, 2016, 12:51:45 PM »
Hi David,

Kindly try out the below and let me know the outcome.

1. Check whether WinUsb has been installed by typing "driverquery" in command prompt and look for winusb string from the print.
2. Use a short USB cable or connect to different USB port.
3. Do you notice any information by right clicking on "Unknown device" and getting the properties?
4. Check if the device is listed in usbview, you can download usbview from http://www.ftdichip.com/Support/Utilities/usbview.zip. Please send me the information of the device.


Best Regards
Prashanth B

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
Re: firmware updating
« Reply #8 on: July 13, 2016, 08:05:13 AM »
Hi Prashanth

    1:Driverquery shows WinUsb as loaded
    2 and 4: USB View (after the CleO35 was moved to another USB port (not a USB 3 port) showed the device as "CLEO35     DFURuntm" -  see attached txt file for full USBView output.
    3: Device Manager showed a WinUsb device but with no problems - a lot of detail wich I will have to extract manually (Windows not helpful here!)
 
cheers
dt.. 

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
Re: firmware updating
« Reply #9 on: July 13, 2016, 08:14:48 AM »
Prashanth:

Just after checking all the details for the post, I tried the newest version of CleO PC tools again and the firmware upgrade to 1.2.0 worked! Not sure why, but I suspect that the USB ports that I was using on this machine were both USB3 and once I had moved the CleO to a standard USB port it started to work properly...

cheers
dt..

prashanthb

  • Full Member
  • ***
  • Posts: 23
    • View Profile
Re: firmware updating
« Reply #10 on: July 13, 2016, 08:27:01 AM »
Hi David,

That's good.

Would you mind to retry the upgrade connecting to usb3.0 port? Just curious to know as it works fine here.


-Prashanth

davidateeyore

  • Full Member
  • ***
  • Posts: 7
    • View Profile
    • The Gerb's Tech Blog
Re: firmware updating
« Reply #11 on: July 13, 2016, 01:55:35 PM »
Hi Prashanth

I tried the upgrade on both USB3 ports, but no CleO device appeared, Windows reported a USB device has malfunctioned. The upgrade works fine on the USB2 ports (CleO appears as CLEO35 DFURunTm)
The USB3 ports work fine with other USB 2 and 3 Devices.
Very strange!

cheers
dt..

CleOSupport

  • Administrator
  • Full Member
  • *****
  • Posts: 51
    • View Profile
Re: firmware updating
« Reply #12 on: July 13, 2016, 02:48:46 PM »
USB3.0 and Windows 7 is a bit of a minefield.

USB 3.0 did not exist prior to Windows 8 and as such Microsoft did not have driver support for USB 3.0 host controllers.

To allow silicon vendors to add USB 3.0 into pre windows 8 systems the vendors developed their own drivers. This has led to a different registry structure from that observed with USB 1.1 and USB 2.0 host controllers leading to potential compatibility issues.

e.g. In the registry pre Windows 8 there is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ROOT_HUB
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ROOT_HUB20

Following this system, the expectation for USB 3.0 hosts would be:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ROOT_HUB30 to follow on for 3.0

However, despite this being the case in Windows 8 with the Microsoft driver, it is often observed to be different with vendor specific drivers, with one example being:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\IUSB3\ROOT_HUB30

As such it is possible that one PC with one vendors host driver may work and another with a different host driver would not. In general all these issues go away with Windows 8 onwards using the default Microsoft host driver.

Any feedback is still valuable to us though.