Yocto Linux for Rpi3 + netHAT

[Armin@netPI]

as I understand from another topic in the forum it is feasible to use a generic Rpi3 + netHAT in order to have a netPI RTE like device. Is it also possible to use the RT-patched Yocto Linux used on netPI on the raspberry or just a generic Linux OS with docker?

Hello Reinhard, yes this is correct. While netHAT is made more for "students" and show the use case EtherCAT, EtherNet/IP and PROFINET as slave device in a simple manner with fixed I/O length of 32bytes input and output, netPI is more flexible and allows to configure any possible I/O length. But neither for netHAT nor for netPI we provide POWERLINK support today.

Using Docker has no need for YOCTO linux as used on netPI. Docker can be installed on native Linux as described here https://www.raspberrypi.org/blog/docker-...pberry-pi/. I am running it at home on my Pi too. But what you must know is that netHAT uses netX52 network controller and netPI uses the netX51 chip. Both have the same chip die, but since they are different chips, different firmwares are used to be loaded into them. So not all firmwares that are available for netPI and netX51 are available for netHAT and netX52. For example on netPI the netX network controller can be standard ethernet ... for netHAT we never compiled this firmware.

I want to test what I can to with the POWERLINK and Codesys before investing in a netPI. For example I guess there will also be the slave only issue decribed by others for other fieldbuses.

This question you have to explain closer to me. You have Codesys that you can run on any Raspberry Pi, this is ok for me, but how is it about POWERLINK. Do you want Codesys to run POWERLINK stack or netPI/netHAT POWERLINK the stack? Is is POWERLINK slave or master you are talking about

Armin