[En-Nut-Discussion] TCP/IP problems with httpd

[uprinz]

Bernd Walter-2 wrote:
> 
> On Wed, Jan 12, 2011 at 05:42:05AM -0800, uprinz wrote:
> 
> Either a correct packet reaches the MAC or not and in the incorrect
> case the MAC should filter it out - and if this fails the IP checksum
> should do.
> Or is it that the PHY itself (it has a link related state machine)
> or it's oscillator crashes?
> In that case the MAC might even be unable to send packets because it
> gets it's transmit clock from the PHY and probably Nut/OS hangs
> in any transmit routine.
> I can even imagine that a bufer full hang wouldn't happen under normal
> conditions and if can't resolve such a condition it even can't got on
> after the PHY has recovered from the faulty condition.
> 
> -- 
> B.Walter <bernd at bwct.de> http://www.bwct.de
> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> 
> 
Hi!

I will check that if I have some spare time. The boards that crash had been
used with PoE split Adapters (Linksys PDS-1000) and had been installed in
various non optimal surroundings ( former ore mine) for a while. As you
might know ESD switches chips from 2-pole (high/low) to 3-pole (
high/low/maybe) logic. 

So we sorted out the boards that malfunction.

What we now have to optimize is the MAC setup. I can't count ho many times a
fresh programmed Nut/OS driven board threw out other systems as it claimed
the same MAC address. 

My Micrel kit for the SPI EMAC/PHY MIC8851SNL arrived, the parallel version
is still missing. So I focus on the EMAC drivers again, hoping that you guys
can find the other problems in the upper layer.

About the locking functions of the EMAC part, yes I encountered that and
actually think about how to handle that more elegant. In lower part of the
network system there are many functions implemented that do not return any
status information or if, it is fixed to 0. Even I repeat myself, the AT91
EMAC is initialized to the "possible ability" list of the PHY instead to the
"link ability" list and there are other bugs too.

I will split the fixes one by one and commit them around weekend. The
splitting of EMAC and PHY driver will be a big one and I'd like to test it
to extreme before I commit that.


-----
Best regards
Ulrich
-- 
View this message in context: http://old.nabble.com/TCP-IP-problems-with-httpd-tp30636692p30660242.html
Sent from the MicroControllers - Ethernut mailing list archive at Nabble.com.