<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>W5100 on Carmine Noviello</title><link>https://www.carminenoviello.com/tags/w5100/</link><description>Recent content in W5100 on Carmine Noviello</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 04 Sep 2015 13:09:20 +0000</lastBuildDate><atom:link href="https://www.carminenoviello.com/tags/w5100/index.xml" rel="self" type="application/rss+xml"/><item><title>Adding ethernet connectivity to a STM32-Nucleo</title><link>https://www.carminenoviello.com/2015/08/28/adding-ethernet-connectivity-stm32-nucleo/</link><pubDate>Fri, 28 Aug 2015 05:23:37 +0000</pubDate><guid>https://www.carminenoviello.com/2015/08/28/adding-ethernet-connectivity-stm32-nucleo/</guid><description>&lt;p&gt;One drawback of the Nucleo ecosystem is the lack of a version with ethernet connectivity or a dedicated shield officially supported by ST. There are 90 different STM32 MCUs available that provide an Ethernet MAC interface (this means that only an external ethernet transceiver - also called &lt;em&gt;phyter&lt;/em&gt; - and few other things are required to bring your MCU to the IoT world). STM32Cube (the HAL officially supported by ST) also provides support for &lt;a href="http://savannah.nongnu.org/projects/lwip/"&gt;lwIP&lt;/a&gt; stack. But, all the current Nucleo boards are designed with a MCU without an Ethernet interface (I think that the main reason is that only two STM32 MCUs with Ethernet MAC are available in LQFP-64 package and the Nucleo boards are designed to be pin-to-pin compatible between its releases - L0, F1, etc). This means that without a dedicated expansion shield it is impossible to add network connectivity to our Nucleo. And this is a sin considering what that MCU can do.&lt;/p&gt;</description></item></channel></rss>