I wait 5-seconds from when I first initialize ethernet to when I start
checking pd_havelink(). We are only using the RCM3000 for ethernet, the
RCM2200's may be more robust in this area.
Like I said, its not a big problem, in that only a few boards have had the
problem. But each time pd_havelink() gave false status replacing the core
module solved the problem.
Steve
Tom Collins <t...@tomlogic.com> wrote:
Tom Collins <t...@tomlogic.com> wrote:
On Mar 29, 2005, at 1:13 PM, Steve Trigero wrote:
> The function Tom was referring to is pd_havelink().
Thanks for the correction.
> I
> have occasional problems with pd_havelink() as well.
> But I've come to the conclusion that its not the
> function but the core module. I will occasionally get
> a core module where pd_havelink() always returns true
> whether a cable is connected or not, which causes
> havic with my program. I throw the board away and grab
> another and it works fine. In my opinion, its a
> hardware problem on the core module. But because the
> core modules are so cheap, and the failures so few,
> its not worth the time and money to go beyond throwing
> them away - at least for us.
I have found that you may need to delay for 1/2 to 1 second after
initializing the ethernet interface before pd_havelink() will report
accurate results.
I have not run into problems with it always returning true on the
RCM2200s I've used. Then again, I'm not sure I've thoroughly tested
that assumption. I'll start watching for it in my Q.C.
--
Tom Collins - t...@tomlogic.com
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet:
sniffter.com