I've been putting together a couple of boards but one of them is giving me jip.
One of them enumerates properly and the usb device shows up, the other does not.
There are no dry joints (that I could find, obviously). There are no shorts between any of the pins on anything anywhere, i've looked with a microscope and probed it with a meter.
I've replaced the CY7C68014A IC (actually I have CY7C68013A, but they're identical apart from power consumption it seems).
The only clue I have is that the oscillator doesn't seem to be running, I don't have a scope though so I can only see some voltages, but on the board that works the CLK testing point is at 1.6v (which makes sense I guess, if the meter is giving me an average) and in the one that doesn't it has 0v.
Pin 11 of the CY7C68014A has 3.3V (tested on the crystal's leg) but Pin 12 gets 0v.
If anybody has any insight it would be appreciated. I just can't find what's up with the bugger.
USB device not recognised (CY7C68014A woes)
Moderators: BigEvilCorporation, prophet36
Re: USB device not recognised (CY7C68014A woes)
I have tried CY7C68014A and CY7C68013A, and both work fine, so your swap shouldn't cause problems.
Do you see the same behaviour if you remove the EEPROM links from both boards? Can you compare the levels on all pins, comparing the working board with the non-working board? That might give us a better idea. Aside from that, check that you put the right value capacitors and resistors in the reset circuit, the oscillator circuit, and the EEPROM circuit.
Do you see the same behaviour if you remove the EEPROM links from both boards? Can you compare the levels on all pins, comparing the working board with the non-working board? That might give us a better idea. Aside from that, check that you put the right value capacitors and resistors in the reset circuit, the oscillator circuit, and the EEPROM circuit.
Re: USB device not recognised (CY7C68014A woes)
All voltages match on the boards, resistors are correct.
Quite by chance I've managed to replicate the behaviour on the working board. If I measure the voltage at the crystals leg and hold the probes long enough (5-10 seconds), that stops the crystal until the device is reset. The leg now shows as 3.3v, and the USB device in windows switches to an "Unknown USB Device (Device Descriptor Request Failed)" all the same as the non-working board.
Quite by chance I've managed to replicate the behaviour on the working board. If I measure the voltage at the crystals leg and hold the probes long enough (5-10 seconds), that stops the crystal until the device is reset. The leg now shows as 3.3v, and the USB device in windows switches to an "Unknown USB Device (Device Descriptor Request Failed)" all the same as the non-working board.
Re: USB device not recognised (CY7C68014A woes)
I would try de-soldering the 22pF caps on the oscillator circuit and replacing them.
Re: USB device not recognised (CY7C68014A woes)
They've already been replaced.
Increasing the capacitance gets the crystal going but it's unstable. I'll have to pick up some different values and see what it needs.
The boards are identical though, I can only guess that the working board is just scraping by.
Increasing the capacitance gets the crystal going but it's unstable. I'll have to pick up some different values and see what it needs.
The boards are identical though, I can only guess that the working board is just scraping by.
Re: USB device not recognised (CY7C68014A woes)
So I got an oscilloscope (always nice to have an excuse to buy some new gear), the crystal is oscillating fine (with the 22pf caps)
It seems that the reset pin is outputting 3.3v (which for sure is not supposed to happen) I disconnected the resistor at R2 to verify, and sure enough it's getting some juice from somewhere.
At some point I'll move the chip to a working board and see if it's damaged or there is just a short somewhere on this board (or both).
It seems that the reset pin is outputting 3.3v (which for sure is not supposed to happen) I disconnected the resistor at R2 to verify, and sure enough it's getting some juice from somewhere.
At some point I'll move the chip to a working board and see if it's damaged or there is just a short somewhere on this board (or both).