DisablePHY() gives error when compiling

[khoney]

I monitored the status of both the RSTI and RSTO pins while doing my manual reset. RSTO does go low while my reset button is pressed. When the system comes up, the Link LED just flashes on and off about every 2 seconds. I did try doing an EnablePhy, but it seemed to make no difference. In my case, I had also stopped the processor after the DisablePhy call, but I don't see why that would make any difference.

Edit: I removed the calls to stop the processor and just disabled the PHY. I still have the same problem - I must power cycle the module for the network to come up correctly.

[lgitlitz]

This is pretty strange. Have you tried calling DisablePhy in a blank project without stopping the processor? This problem would be better handled through the NetBurner support system, you should start a ticket there.

[khoney]

I can't log into support for some reason. I even had it do a password reset, and the password sent does not get me in.

So I created a blank project in which all I do is alternate between calls to DisablePHY and EnablePHY every ten seconds. Once DisablePHY is called the first time, I get the flashing link light the next time EnablePHY is called.

[khoney]

I tried bringing in the Ethernet.cpp code into my test project. I changed the code in EnablePHY so that auto-negotiate is set to FALSE, and now the EnablePHY call works. I'm not an Ethernet guru - can someone explain why autonegotiation wouldn't work?

Edit:
Actually, the link light comes back on now, but the data link shows no activity.

[lgitlitz]

For your support account, send an email with your serial to rtadmin@netburner.com and he should be able to help you.

The auto-negotiation fix is strange since you only have this issue after calling disablePHY. What is the other end of the Ethernet cable connected to, ie. a specific roter or PC? Is that linked device set to not use auto negotiation?

-Larry

[khoney]

I'm connected to a laptop - I've never messed with its settings, so I'm pretty sure it's set to auto-negotiate. My system works fine on power-up, but even calling DisablePHY() followed by EnablePHY() results in this behavior. One thing to note is that we are running with a module with the Ethernet header, not the one with the jack on-board. I'm pretty sure this is not an issue, since our system works fine on power-up.

[khoney]

Just thought I'd update the resolution to this issue. We are using the 5270 with the connector for an external network jack, and the signals that are labelled 2.5V are supply outputs from the Netburner module. The layout guy thought they were just regular digital supply connections, so he connected 3V to them. We corrected on the 2nd board rev, and all is well now.