The including Design-Tools support the customer setting-up the objects in the libraries and in creating the corresponding EDS Files (EDS and GSDML).
The middleware GOAL is the corresponding connector resp. anchor to the specific hardware and provides the real-world hooks to the hardware and to the environment while the protocol libraries implement the communication protocol itself and take comfort in the services, provided by GOAL.
While GOAL seems to be rather a complication – in the real world (and mean world) GOAL is the enabler to address and survive reality.
GOAL with PROFINET, EtherNet/IP supports the following targets:
Linux: using the eth0 (or any other ethx) and done.
RZ Family by Renesas: RN/N-1D, RZ/N-1S RZ/N-1L und RZ/T1
- RZ/N-1D: Dual Core A7 MCU + M3 Subsystem – GOAL runs in the M3 Sub system and the API is being mapped to the Linux Kernel.
- RZ/N-1S: Single Core A7 MCU + M3 Subsystem – GOAL runs in the M3 Sub system the Stack API are being mapped into the A7 Core – running ThreadX
- RZ/N-1L: M3 MCU – GOAL runs in the M3 Sub system
- RZ/T1: R4(F) MCU + M3 Sub system – GOAL runs in the M3 Sub system
STMicroelectronics: STM32F4x Series
Texas Instruments: Tiva TM4C
More about GOAL: https://www.port.de/en/products/goal-middleware.html
More about Design Tool: https://www.port.de/en/products/profinet/tools/profinet-design-tool.html