The Internet Control Message Protocol (ICMP) is one of the core transport protocols in the IP stack. It’s used to convey error messages between systems and to debug and probe network topology. It does not carry user data, unless you could describe the content of an echo request as user...

The IPv4 module (abbreviated to just IP from hereon) implements the Internet Protocol, version 4. IP is a network layer protocol that is responsible for marshalling data to and from the transport layer protocols such as UDP and TCP and the datalink layer protocols such as Ethernet. To do this...

ARP. The mission-critical protocol that you’ve never heard of. The Address Resolution Protocol (ARP) exists because the datalink layer talks in terms of MAC addresses and the network layer talks IP addresses. ARP exists as a translation module that maps between the two. Under the hood...

The ethernet PHY is responsible for the transmission and reception of frames on the network. The PHY is very closely tied to the MAC and supports one or both of the MII and/or the RMII interfaces. PHY implementations stm32plus::net comes with support for two PHYs, the DP83848C from Texas...

The MAC module is responsible for providing an interface between application code that wants to send and receive ethernet frames and the ethernet PHY that provides the protocol for doing so. The MAC is also responsible for implementing error detection and reporting as well as collision...

Welcome to a landmark release, version 3.0.0, of my stm32plus C++ library for the STM32F1 and STM32F4 series of microcontrollers. This release introduces support for the ethernet MAC peripheral in the form of an object-oriented TCP/IP stack as well as support for the STM32F107 connectivity...