Arduino esp8266 build fails

[Pfannex]

Hi,

I'm using the Arduino IDE 1.8.7 with the latest esp8266 Version 2.4.2 including lwIP2.
Board: WeMos D1 R1

I tried to compile this minimal sketch:

#include "ESP8266WiFi.h"
#include <w5500-lwIP.h>
void setup() {}
void loop() {}

build fails with:

Arduino: 1.8.2 (Windows 10), Board: "WeMos D1 R1, 80 MHz, Flash, 4M (1M SPIFFS), v2 Lower Memory, Disabled, None, Only Sketch, 921600"

In file included from C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/lwip/arch.h:48:0,

                 from C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/lwip/debug.h:40,

                 from C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/lwipopts.h:3004,

                 from C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/lwip/opt.h:51,

                 from C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/lwip/netif.h:40,

                 from C:\Users\pf\Documents\Arduino\libraries\W5500lwIP\w5500-lwIP.cpp:8:

C:\Users\pf\Documents\Arduino\libraries\W5500lwIP\w5500-lwIP.cpp: In member function 'err_t Wiznet5500lwIP::start_with_dhclient()':

C:\Users\pf\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.2/tools/sdk/lwip2/include/arch/cc.h:124:24: error: 'ethernet_input_LWIP2' was not declared in this scope

 #define ethernet_input ethernet_input_LWIP2

                        ^

C:\Users\pf\Documents\Arduino\libraries\W5500lwIP\w5500-lwIP.cpp:53:66: note: in expansion of macro 'ethernet_input'

     if (!netif_add(&_netif, &ip, &mask, &gw, this, netif_init_s, ethernet_input))

                                                                  ^

exit status 1
Fehler beim Kompilieren für das Board WeMos D1 R1.

How can I compile with lwip2?

regards
Pf@nne

[borisneubert]

Same issue here (minimal sample project referenced there).

David, you probably have a working project. Would you mind sharing the code with us?

Thank you and kind regards,
Boris

[d-a-v]

Will answer later today. Thanks for your interest.
This library should be moved directly into the core don't you think ?

[d-a-v]

Fix pushed

[borisneubert]

Thank you. I confirm successful compilation. Still need to test with actual hardware.

Benefits of library being in the core:

• W5500 module is preferred ethernet adapter (raw driver should made use of full potential of the chip to offload CPU, not only PHY layer)
• Being part of the standard greatly widens potential user base which is useful for getting feedback on issues and enhancements.
• We prefer standard over non-standard libraries as they tend to be more likely maintained for a long time

Thus yes, library should be moved to core.

[Pfannex]

Hi David,

thanks for fixing!

Can you give us a short example code?
We are using a ESP8266 WeMos D1 R1with a W5500-board like this:
https://www.ebay.de/itm/W5500-Ethernet-Network-Modul-TCP-IP-51-STM32-SPI-Schnittstelle-Fur-Arduino-New/272461200469?hash=item3f6ff3fc55:g:p~AAAOSwB09YNpwB&redirect=mobile

Please share also the wire connection with us, especially the CS pin.
We use GPIO4(D2) for CS. Because of the PullUp/GPIO15 problem.

Regards
Pf@nne

[d-a-v]

I use the same board ethernet board and wemos D1 mini lite.
I use D0 for CS.

Here's a stripped example.

// D0 CS SDCARD
// D8 CS ethernet
// D3 MOS
// D2 INPUT WATER
// D4 1-WIRE temp

#include <ESP8266WiFi.h>

#include <w5500-lwIP.h>

Wiznet5500lwIP eth(D0);

void setup ()
{
  // setup code
  // ...

  eth.setDefault(); // use ethernet for default route
  eth.begin(); // default mtu & mac address
}

void loop ()
{
  eth.loop(); // call this at least once per loop and around delay()/yield() calls

  // user code
}

[Pfannex]

Hi David,

thanks for your simpleCode, your code works well with the W5500.......
W5100 doesn´t work, begin() returns 0.

#include <Arduino.h>
#include "ESP8266WiFi.h"
#include <w5500-lwIP.h>

// Arduino Pin 4 = Wemos Pin D2
#define CSPIN 4

Wiznet5500lwIP eth(CSPIN);
byte mac[] = {0x00, 0xAA, 0xBB, 0xCC, 0xDE, 0x02};

void setup() {

  Serial.begin(115200);
  Serial.println("");
  Serial.println("start");

  eth.setDefault(); // use ethernet for default route
  int present = eth.begin(mac);
  Serial.println("");
  Serial.println("present= " + String(present, HEX));

  while (!eth.connected()) {
    eth.loop();
    Serial.print(".");
    delay(1000);
  }
}

void loop() {
   eth.loop();
   Serial.println(eth.localIP());
   delay(1000);
}

[Pfannex]

Hi David,

we are not able to bring a simple NTPClient or WebServer to work. We get an IP address but the NTPClient or WebServer do not connect/cannot be contacted as if the did not bind to the interface.

Would you mind providing a simple example for that, please?
Like this: https://github.com/blackketter/NTPClient

Regards,
Pf@nne

[borisneubert]

I guess the issue is that either the services do not bind to the interface (although they bind to IPANY in their code) or that some additional define is missing besides PIO_FRAMEWORK_ARDUINO_LWIP2_LOW_MEMORY

[d-a-v]

There are number of small issues to solve.
One of them is that incoming packets are processed when ::loop() is called, so

• it must be called quite often
• this is totally not compatible with delay() in loop() which is the usual arduino way
  (and the NTPCLient example)

So we should be using some sort of timer to call ::loop() or it should automatically be called when yield() is called (that would be after integration into the arduino core).

Before that, we do what we can, NTPClient example could then be:

#include <NTPClient.h>
// change next line to use with another board/shield
#include <ESP8266WiFi.h>
//#include <WiFi.h> // for WiFi shield
//#include <WiFi101.h> // for WiFi 101 shield or MKR1000
#include <WiFiUdp.h>
#include <w5500-lwIP.h>

#define WIFI 0

#if WIFI
const char *ssid     = "SSID";
const char *password = "PSK";
#endif

Wiznet5500lwIP eth(D0); // <- use your CS pin
WiFiUDP ntpUDP;

// By default 'time.nist.gov' is used with 60 seconds update interval and
// no offset
NTPClient timeClient(ntpUDP);

// You can specify the time server pool and the offset, (in seconds)
// additionaly you can specify the update interval (in milliseconds).
// NTPClient timeClient(ntpUDP, "europe.pool.ntp.org", 3600, 60000);

unsigned long sectest = 0;
unsigned long now = 0;
bool everysec ()
{
  now = millis();
  if ((now - sectest) > 1000)
  {
    sectest = now;
    return true;
  }
  return false;
}


void setup() {
  Serial.begin(115200);

#if WIFI
  WiFi.begin(ssid, password);

  while ( WiFi.status() != WL_CONNECTED ) {
    delay ( 500 );
    Serial.print ( "." );
  }
#else
  WiFi.mode(WIFI_OFF);
#endif

  if (eth.begin())
  {
    eth.setDefault();
    Serial.println("eth started");
    while (!eth.connected())
    {
      eth.loop();
      if (everysec())
        Serial.print(".");
    }
    Serial.println();
  }
  else
    Serial.println("could not start ethernet");
  Serial.println("starting");
  timeClient.begin();
}

void loop() {
  eth.loop();
  if (everysec()) //   delay(1000);
  {
    timeClient.update();

    Serial.print(timeClient.getFormattedTime());
    Serial.print(" eth-conn=");
    Serial.print(eth.connected());
    Serial.print(" eth-ip=");
    Serial.print(eth.localIP());
    Serial.print(" wifi-ip=");
    Serial.println(WiFi.localIP());
  }
}

[borisneubert]

Thank you very much, David, for looking into this and for providing the example. I still have to look at it in detail.

My W5500 arrived by mail order. Thus, yesterday night, I extended my example code.

The AsyncWebserver example worked right out of the box and is reachable both via WiFi and Ethernet.

NTP client example did not work right away and now does only with the IP address of the NTP server, not with its FQDN. I will rewrite it according to your example, though.

I monitored network traffic with wireshark yesterday. It looks like I am missing some packets in wireshark (I see no name resolution). At least I see issues with ARP. Ethernet has difficulties to get the MAC address of the gateway, sending ARP requests 5 times but receiving no response. I particular, the overall process hangs for seconds, which coincides with 4 to 5 seconds latencies of ping. This is compatible with your reasoning that eth.loop() is not called as often as required. This is like fishing in murky waters.

What can I do to foster integration of the library into the core?

Is it instead reasonable to do it in a minimal fork of the relevant Arduino Iibrary if the integration into the core does not happen or takes too much time?

Cheers
Boris

[borisneubert]

@d-a-v We created a full real-world example with AsyncWebserver, NTP Client and MQTT Client. Observations:

• AsyncWebserver + NTP Client + MQTT Client work over WiFi (with Ethernet turned off)
• AsyncWebserver + NTP Client work over WiFi plus Ethernet
• AsyncWebserver + NTP Client + MQTT Client do not work at all if WiFi and Ethernet are both turned on, no matter if Ethernet is the default interface or not

This is likely due to Ethernet getting stuck if the MQTT Client tries to connect without calling eth.loop(). This is consistent with your considerations about ::loop() to be called with yield().

We now have a real-world example for testing a future version of the Arduino library with integrated W5500 ethernet.

We are keen to support the integration into the core with testing. @Pfannex is experienced with low-level device programming and could support the addition of status functions and the like into the W5500 device class.

@d-a-v How do you like to proceed and how can we help?