On 20/6/20 7:12 am, Joel Sherrill wrote:
> *** Is there a reliable way to know the stack is settled out before the
> application can run?
This is a hard one. Some interfaces have PHYs that take different times to come
up, is the stack ready when one of several interfaces is available? Then there
i
This turned out to be a trivial problem but hard to figure out. :(
The code has a POSIX_Init which initializes the stack and then calls the
application's main() which spawns a number of threads which start using the
stack. I disabled the POSIX_Init from calling main(), added mcast-listener
and mca
I can agree with Cedric.
I use rtems5 with rtems-libbsd. I initialize the network interfaces of my
target via dhcpcd
and the interfaces are automatically multicast capable.
This works without creating a route:
if (setsockopt(conf->udp, IPPROTO_IP, IP_ADD_MEMBERSHIP,
(c
On 18.06.20 22:47, Joel Sherrill wrote:
Hi
I have an example FACE application I am trying to port to RTEMS. This
is a multi-question email:
First, it fails with EADDRNOTAVAIL on this call:
// Subscribe to multicast group
struct ip_mreq mreq;
rc = inet_pton(AF_I
Hi
I have an example FACE application I am trying to port to RTEMS. This is a
multi-question email:
First, it fails with EADDRNOTAVAIL on this call:
// Subscribe to multicast group
struct ip_mreq mreq;
rc = inet_pton(AF_INET, multicastGroup_m,
&mreq.imr_multiaddr.s_