From 6f9c3e5537ec8ab62fa95c301e1e15223d044d64 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 23 Mar 2016 11:24:18 +0100 Subject: bsp/motorola_powerpc: README.qemu --- c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu b/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu index cc23af65a1..9ccf3779a9 100644 --- a/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu +++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu @@ -82,7 +82,12 @@ can be used with unbundled/libbsdport drivers]) I use networking with a 'tap' interface on the host machine and can then communicate with the emulated target in any -desired way. +desired way. The Ethernet address specified in the RTEMS network interface +configuration and the Qemu command line must match, otherwise uni-cast frames +are not received. It is best to use a NULL pointer in the RTEMS network +interface configuration for the Ethernet address, so that the default from Qemu +is used. Make sure that your firewall settings allow communication between +different Qemu instances and your host. On (linux) host: -- cgit v1.2.3