Thank you for your reply. I have already tried this driver (version 220.127.116.11) earlier in the week when I found it in a post by Hemanth. It did not correct my problem.
I understand that the problems with the Redstone3 (1709) Fall Creators update by Microsoft has created much confusion with USB 3.0 support. Our customers have been experiencing problems and are in need of support. The difficulty is that there are multiple problems that are corrected in different ways.
The SPECIFIC problem I am trying to debug is different than any I have seen described:
1. CyUSB3.sys installs correctly.
2. CyUSB3.sys loads correctly when my FX3 device is plugged in.
3. CyUSB3.sys fails to load firmware and restart my FX3 device as it should.
I may be able to gather further information and maybe even diagnose the source of the problem but I have no clue what is going on in CyUSB3.sys. Is there any diagnostic output, logging or possibly TraceView.exe information that I can get????
I noticed that the 18.104.22.168 driver came with a .PDB file that might contain traceview logging information but it does not. I do not have any .PDB file for the previous driver version, 22.214.171.124.
Can you help me diagnose what is happening in CyUSB3.sys? Where can I look for information about what is happening when it loads and runs????
I've had an opportunity to work on this some more.
No one would tell me how to trace/debug CyUSB3.sys so I used USBlyzer on it and figured out that when this fails (sticks in boot load VID/PID) it's actually failing DURING the firmware download, anywhere from 25-75% complete. It actually locks up the front end on USBLyzer and it only comes back alive if I unplug my USB device. I have traces if anyone cares to look at them.
Since this project is a few years old, I feared that the boot loader firmware for CyUSB3.sys might be out of date so I downloaded the latest SDK (1.3.3) and customized the loader firmware from fresh source. Exactly the same problem.
Since all the problems go away when I use a USB2.0 port on the aberrant machines, I figured that I would make the boot firmware NOT take advantage of the SuperSpeed setting (restrict descriptors to High Speed) but for some reason I could not get the descriptors correct and I can
t get the boot_fw project won't run at High Speed when plugged into a SuperSpeed port. I always get an enumeration error, no matter what I try. I can forward that source of someone is interested in looking at it for me.
Just to be sure it wasn't our hardware, I programmed the boot loader into the I2C eeprom on the Cypress FX3 SuperSpeed Explorer Kit (DVK) and I have the exact same problem.
I'm running out of things to try so any suggestions would be helpful.
Embedded Systems Engineer
Upload the firmware project and the traces here for the review.
Will try to re-produce here.
Hello Srdr -
Sorry for the delay in response. Got side tracked with a different project.
USBLyzerTraces.zip contains both raw (.ulz) and exported Text (.html) traces from the USBLyzer tool. There are 2 traces, one good, one bad, for you to compare. The bad trace stops mid-download at about 60%. The difference between these 2 is the bad trace is when our device is directly plugged into the PC's USB3.0 port, the good trace shows what happens when a USB3.0 4-port hub is inserted in between our device and the PC.
I've included source for our boot loader in Usb2ScsiBootLoader.zip. This firmware will enumerate as VID/PID 0x1826/0x0122.
Please let me know if you need more information. I will try to be more prompt in my response.
Thank you in advance for your help.