Cable not detected
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: Cable not detected
by Eugeny ·
Of course. Connection detection is performed using sensing electricity in the wire, not sensing physiscal insertion of the cable.
If there’s another active device at another end of the cable.
RE: RE: Cable not detected
by Daan ·
Thank you for your reply.
But just like I said, the other side of the cable is connected to a (active) router, however, no LED is light up. What I mean is, should I configure some register in the software to have the LEDs light up when I insert the cable?
RE: Cable not detected
by Eugeny ·
I do not think so. If PHY is up it must turn at least link LED on. Does the switch light its link LED up?
So the things to check are cable (try another one), circuit diagram (check again - did you use parts from reference or replaced some with another parts?), and assembly quality (missing some ferrite beads?). Would be good if you share your actual circuit diagram here.
RE: Cable not detected
by Daan ·
I have already tried another cable and checked the PCB, all looks OK. I can read the W5100s registers, so the interface between CPU and Wizchip is OK.
The 25MHz xtal is running and all 1.2 and 3.3 voltages are correct.
The router doesn’t light up any LED either.
I attached our schematic .
RE: RE: Cable not detected
by Eugeny ·
It misses part number for the jack and pin assignments. Also some values (e.g. ferrite bead).
RE: Cable not detected
by Daan ·
This is the jack (Wurth 74990111217):
RE: Cable not detected
by Daan ·
Bead (Wurth 742863160): 600 ohm, 500 mA, WE-CBF HF Series, 0.35 ohm, ± 25%
RE: Cable not detected
by Eugeny ·
The problem could be in your wiring pins of jack wrongly, that’s why for circuit diagram pin numbers are the MUST. It will also assumes that you wired device properly at the device editor level.
RE: Cable not detected
by Daan ·
Yes, that could have been the cause, but we have checked the connector layout and it is OK. Our hardware engineer has inserted the pin numbers:
RE: Cable not detected
by Daan ·
Do you have any other suggestion?
RE: RE: Cable not detected
by Eugeny ·
Yes, reset circuit does not look good. What timing diagram you expect from this circuit?
As a test make it digital connecting to the MCU’s configurable output pin.
RE: Cable not detected
by Daan ·
This is my initialisation:
RE: Cable not detected
by Daan ·
The reset circuit is designed to give a high level after 1.53ms. The datasheet describes this should be 210ns minimum.
Could you please explain what is wrong with our reset circuit? Why is a MCU pin better than an RC-circuit?
RE: RE: Cable not detected
by Eugeny ·
PHY is independent of the host interface, and if it does not light link LED when cable is connected (with this cable connected to another live device at another end) then you have one or more of the following problems:
On your circuit diagram I do not see connection between 1V2O and 1V2D/1V2A. And while datasheet says that chip should have Schmitt triggers inside on inputs, if I would you I would try clean digital signal on the reset pin according to datasheet timing. And you still do not give part numbers you use on the circuit diagram. You must write what is the jack, what is the chip, and that is the crystal. Respect others who takes effort considering your circtuit, and in general respect yourself so that in 3 years when returning to this device you (or your colleagues) would not look for this information elsewhere.