Hi there,

I designed a PCB which has a FE1.1s USB bub controller. The problem is that when I connect my device to computer,"device not recognized" error appears. device LED's turns on for a moment and everything goes off again.
I have searched for driver issues but it seems that everything is OK here. My question is, what mistake caused this error and how should I solve it?! The attached file is my schematic with some changes (to make it bus powered)

Is there any thoughts on this?!?

best regards,
HAMIDREZA

 

Welcome to AAC.

I am assuming this is a Windows system. What does Device Manager say about it?

 

Thank you so much!
This is two screenshots of my computer when i plug in my device

 

Any thought on this?????

 

Sorry, I didn’t see your reply. If you look into device manager after the error and while it is still plugged in, do you see it enumerated as an unknown device under the USB devices?

 

yes! its enumerated there, but it says that "A request for the USB device descriptor failed." .

 

yes! its enumerated there, but it says that "A request for the USB device descriptor failed." .

Well, that's the problem, though not the cause. Do you have to program that chip with the descriptor? The datasheet describes using an E²PROM to provide the information to the chip at startup. I don't know if it has useful default data.

 

Today I had a little search on this problem and thought this might be the problem but not for sure!
Now that you say that, can you please guide me for this problem? any kind of guide or document that help me with programming this chip will be a great help! I'm a self-learner!
By the way, is this programming just for first run of this chip or an EEPROM must be included in my circuit?
And also, what kind of properties is specified by device descriptor?

 

Today I had a little search on this problem and thought this might be the problem but not for sure!
Now that you say that, can you please guide me for this problem? any kind of guide or document that help me with programming this chip will be a great help! I'm a self-learner!
By the way, is this programming just for first run of this chip or an EEPROM must be included in my circuit?
And also, what kind of properties is specified by device descriptor?

DO oyu have a copy of the datasheet?
Does device manager show a vendor ID?

I am not an expert on this, maybe someone else can help.

 

Thank you so much ya’akov, for your valuable time!

Yes, I have it. But it doesn’t say anything about details! I searched in web and YouTube but I didn’t find any straight forward tutorial on fe1.1s but some similar E2PROM-aided programming might help!

Wish someone helped me that I didn’t need to try and error in this project!

 

Thank you so much ya’akov, for your valuable time!

Yes, I have it. But it doesn’t say anything about details! I searched in web and YouTube but I didn’t find any straight forward tutorial on fe1.1s but some similar E2PROM-aided programming might help!

Wish someone helped me that I didn’t need to try and error in this project!

I wish I had more information. I think you need better diagnostic tools. I know there are some for MacOS and Linux but I don't know about Windows. My best suggestion is to see if you can find the log that might have records about the insertion and failure.

There is one other possible cause in my mind, overcurrent. If your device, for some reason draws to much current, it might shut down the port for a moment and interrupt the process. This is just a guess, but maybe you could measure the current or use a powered hub.

Very sorry I can't help more. Good luck.

 

You're so helpful.
I think reading complete document of USB2.0 might be helpful for me.
Wish that would benefit!