USB3.0 device cannot be recognized properly on E3950 F-1 stepping

JLin7 · ‎09-06-2019

we meet an issue about USB3.0 device cannot be recognized properly on E3950 F-1 stepping, but it's no problem on N3350.

Does any one also have this issue ?

CarlosAM_INTEL · ‎09-06-2019

Thank you for contacting Intel Embedded Community.

Could you please tell us if the affected designs have been designed by you or by a third-party company? In case that they are third-party units please give the part number, model, name of the manufacturer, where it is stated the information related to it. In case that it is your design, could you please clarify it has been reviewed by Intel and the list the sources that you have used to develop it?

We are waiting for your reply.

Best regards,

@Mæcenas_INTEL.

JLin7 · ‎09-09-2019

Hi @Mæcenas_INTEL ,

Thanks for your reply.

The USB 3.0 device we've tested is "Gigastone USB3.0 flash drive, U301 16GB ". We didn't have Intel to review the schematic.

CarlosAM_INTEL · ‎09-09-2019

Hello, @JLin7:

Thanks for your clarification.

Based on your previous communication, we would like to address the following questions:

Could you please reproduce the cited condition but using different USB 3.0 ports, also use different USB 3.0 devices (it is better if they have different characteristics and have been manufactured by different companies) to verify the conditions that this problem happens? Please give a detailed description of the results related to these suggestions.

Finally, could you please list the documents with their numbers used to design the affected project?

We are waiting for all information requested in these questions.

Best regards,

@Mæcenas_INTEL.

JLin7 · ‎10-14-2019

Hi @Mæcenas_INTEL ,

Sorry for my reply late.

This symptom is only with that USB dongle so far. I think this should be device issue . So we will not keep to track this issue only if the symptom also happens on the other devices.

Thank you !

CarlosAM_INTEL · ‎10-15-2019

Hello, @JLin7:

Thanks for your reply.

In case that this situation happens with just one device, we suggest contact the manufacturer to find a solution.

Best regards,

@Mæcenas_INTEL.