Ethernet support missing from STM32F1

I wanted to see if I could use the Ethernet_STM library configured for a Wiznet W5100 with a maple mini as the target.
In order to get the Ethernet_STM library compile with a maple mini as the hardware target, I had to copy the following files from STM32F4/cores/maple into STM32F1/cores/maple:

IPAddress.h
IPAddress.cpp
Client.h
Printable.h
Server.h
Udp.h

Why would these files be missing? Are there some hardware tweaks required to make these files compatible with the STM32F1 and the maple mini?

viewtopic.php?f=13&t=330

Double-check your installation. Could be that a past reorg in gethub created a pathing issue, but I have heard no other complaints.

ALSO:
Why would these files be missing? Are there some hardware tweaks required to make these files compatible with the STM32F1 and the maple mini?

In the future, please search the forum before posting questions. If something is stated as working, but not then you have a great segue into a post. Everything is indexed by Google, so the query could have been: 5100 site:stm32duino.com or use the forum search in the top-right of the page.

Ray

hwstar wrote:I wanted to see if I could use the Ethernet_STM library configured for a Wiznet W5100 with a maple mini as the target.
In order to get the Ethernet_STM library compile with a maple mini as the hardware target, I had to copy the following files from STM32F4/cores/maple into STM32F1/cores/maple:

IPAddress.h
IPAddress.cpp
Client.h
Printable.h
Server.h
Udp.h

Why would these files be missing? Are there some hardware tweaks required to make these files compatible with the STM32F1 and the maple mini?

Hi Vassilis

I just saw your PR.

Are these files part of the AVR and SAM core as well, or something specific to support the W5100 library ?

Thanks for confirming this.

“In the future, please search the forum before posting questions. If something is stated as working, but not then you have a great segue into a post. Everything is indexed by Google, so the query could have been: 5100 site:stm32duino.com or use the forum search in the top-right of the page.”

I did do both searches prior to posting to see if anyone had already reported the missing files.

Hi Roger,

The files mentioned above were added in github when I’ve added arduino_uip under F4 back in July.
They are the same whatever ethernet module been used, ENC28J60/W5100/W5500.
Of course they can simply be copied from F4 to F1 folder, but since they are the same, longer term solution would be to have common folder for platforms, but if you remember, this is not an easy task, so copies are the simplest solution for now.

OK.

I can see these files in the AVR Arduino

Is this where you copied them from?

Probably yes for the original, from what I recall back in July.
There are also in the ESP8266 github, but a bit reformatted.
Also, I’ve added the toString() method in IPAddress class in both STM32 and ESP8266 versions.

UPDATE
My regrets forum… I sometimes forget this is a democratic forum, my ideas and wants are no more important than anyone else nor is my time or effort. I forget that everything evolves and I do not think anyone could have thought that the STM32 would have created such interest. I think I would be far more efficient if I did not attempt to butt-in.

Ray

Ray,

I must have missed you butting in???

Anyway, it’s no big deal, I just need to add those files

We occasionally come across stuff that’s in Arduino 1.0 or newer that wasnt in Arduino 0022 when Leaflabs started the ball rolling all those years ago.

So I’m sure this won’t be the last time we find things that are missing

RogerClark wrote:So I’m sure this won’t be the last time we find things that are missing

Hi Martin

So I guess my best option is to copy the F4 versions into the other cores ?

mrburnette wrote:UPDATE
My regrets forum… I sometimes forget this is a democratic forum, my ideas and wants are no more important than anyone else nor is my time or effort. I forget that everything evolves and I do not think anyone could have thought that the STM32 would have created such interest. I think I would be far more efficient if I did not attempt to butt-in.

Ray

I don’t know much about support for symbolic links in Windows, but install.sh could generate all the required symbolic links to a common directory after the repo is cloned from Github (at least in Linux) This would allow the common files to be placed in a single directory and avoid the referential integrity issue with multiple files.

hwstar wrote:I don’t know much about support for symbolic links in Windows, but install.sh could generate all the required symbolic links to a common directory after the repo is cloned from Github (at least in Linux) This would allow the common files to be placed in a single directory and avoid the referential integrity issue with multiple files.

Thanks Ray

ummm.
Now… I remember you mentioning it a while ago.

I guess if it was done automatically it would work.

I wonder how git handles this on multiple os’s .e.g Windows mainly would be my concern.

About symbolic links, I’ve always think that Microsoft did a big mistake about them. Those links exist since almost the beginning of Unixes, both Microsoft decide to partially implement them in NTFS but without any commands/tools available in their older Windows earlier than Vista.

MKLINK is the tool available since Vista, while JONCTION from sysinternals is alvailable for older Windows :

https://technet.microsoft.com/en-us/lib … 53194.aspx
https://technet.microsoft.com/en-CA/sys … 96768.aspx

But, if I remember, there is a caveat : it doesn’t work across drives/volumes.

RogerClark wrote:Thanks Ray
<…>
I wonder how git handles this on multiple os’s .e.g Windows mainly would be my concern.