Olimex Support Forum

DUINO => ARDUINO => Topic started by: gregh on December 11, 2021, 06:58:04 PM

Title: Ethernet not repsonding LED1 blinking Olimexino-328 + MOD-ENC28J60
Post by: gregh on December 11, 2021, 06:58:04 PM
Hello,

After some time running fine (from a week to hours) my Olimexino-328 + MOD-ENC28J60 does not respond to pings anymore or ping times are > 5 sec and no ethernet connection is possible.
The LED1 is blinking very fast.
After power down / up everything is fine and the LED1 is constant.

I have added a watchdog timer with no luck.
I also changed the power supply unit, no change.

How can I debug this, some hints what to do?

Thank you!

greg


Title: Re: Ethernet not repsonding LED1 blinking Olimexino-328 + MOD-ENC28J60
Post by: gregh on December 12, 2021, 05:59:54 PM
I can reproduce this behavior when I unplug the MOS-ENC28J60 while running. LED1 blinks very fast, reset does not work, all other LEDS are normal (including the Ethernet LEDs on the socket). Power down/up solves the problem (and plugin in of course).
But not every time the LED1 blinks when the error occurs while running, sometimes only the Ethernet does not respond to ping or the ping times are extremely slow.
Is there a hardware issue?
Title: Re: Ethernet not repsonding LED1 blinking Olimexino-328 + MOD-ENC28J60
Post by: gregh on December 18, 2021, 02:25:19 PM
After reading a little on arduino forums [1] and blogs, it seems that the ENC28J60 chip needs a lot of CPU power and makes therefore problems with arduino uno boards.

Are there recommendations for a suitable Ethernet uext module for Olimexino-328?
Arduino forums recommend Wiznet W5100 or W5500 chips, but unfortunately I could not find one for Olimexino-328.

Or should I instead go with the OLIMEXINO-2560 + MOD-ENC28J60 ?
Did someone try this combination?

[1] https://forum.arduino.cc/t/enc28j60-vs-wiznet-whats-the-current-status/
Title: Re: Ethernet not repsonding LED1 blinking Olimexino-328 + MOD-ENC28J60
Post by: gregh on January 02, 2022, 09:46:10 PM
It is quite possible that the problem was related to a client program, that sometimes did not close socket connections. I can't test it now, because I changed the hardware.