deac/osd-contiki
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Minor docu update.

Browse source
This commit is contained in:
oliverschmidt 2008-11-13 20:26:27 +00:00
parent 699c493866
commit a844636218
2 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
cpu/native/net/README-WPCAP
View file

@ -1,11 +1,11 @@
Contiki network I/O on Microsoft Windows (including the Cygwin environment) is Contiki network I/O on Microsoft Windows (including the Cygwin environment) is
implemented based on the quite popular WinPcap library that is available at implemented based on the quite popular WinPcap library that is available at
http://www.winpcap.org/install/default.htm. http://www.winpcap.org/.
Developing Contiki network applications most likely involves working with a Developing Contiki network applications most likely involves working with a
network protocol analyzer. Wireshark (formerly known as Ethereal) is a very network protocol analyzer. Wireshark (formerly known as Ethereal) is a very
popular one that on Windows uses - and actually comes with - the WinPcap popular one that on Windows uses - and actually comes with - the WinPcap
libary. Wireshark is available at http://www.wireshark.org/download.html. libary. Wireshark is available at http://www.wireshark.org/.
So with Wireshark installed Contiki network I/O doesn't need any additional So with Wireshark installed Contiki network I/O doesn't need any additional
components. components.
@ -14,10 +14,10 @@ On Windows every Contiki application has one obligatory comand line argument
that identifies the Windows network interface to be used by Contiki. While on that identifies the Windows network interface to be used by Contiki. While on
Unix those network interfaces are called i.e. '/dev/tap0' they have on Windows Unix those network interfaces are called i.e. '/dev/tap0' they have on Windows
names like '\Device\NPF_{F76B480A-1D31-4B3D-8002-C0EF49185737}'. In order to names like '\Device\NPF_{F76B480A-1D31-4B3D-8002-C0EF49185737}'. In order to
avoid the necessity to enter such names on the command line instead the IP avoid the necessity to enter such names on the command line instead the IPv4
address used by Windows is entered to identify the network interface to be address used by Windows is entered to identify the network interface to be
used by Contiki. Please note that this IP address is _NOT_ the IP address to used by Contiki. Please note that this IPv4 address is _NOT_ the IPv4 address
be used by Contiki ! to be used by Contiki !
Contiki network I/O on Windows uses the same MAC address used by Windows. This Contiki network I/O on Windows uses the same MAC address used by Windows. This
approach often described as IP-Aliasing was primarily choosen because it avoids approach often described as IP-Aliasing was primarily choosen because it avoids

4
platform/win32/README
View file

@ -22,7 +22,7 @@ extend two makefiles are necessary:
- Makefile.win32 is an ordinary (yet complex) Contiki 2.x Makefile.$(TARGET) - Makefile.win32 is an ordinary (yet complex) Contiki 2.x Makefile.$(TARGET)
As an alternative to building with Cygwin, gcc and the Contiki 2.x build system As an alternative to building with Cygwin, gcc and the Contiki 2.x build system
it is also possible to use Microsoft Visual Studio 2005 (including the Express it is also possible to use Microsoft Visual Studio 2008 (including the Express
Edition) by loading platform/win32/contiki.sln. Edition) by loading platform/win32/contiki.sln.
As platform/win32/Makefile.win32 includes cpu/native/Makefile.native the WinPcap As platform/win32/Makefile.win32 includes cpu/native/Makefile.native the WinPcap
@ -37,4 +37,4 @@ Windows system menu under 'Properties'.
As the console is used for displaying the actual user interface the log output As the console is used for displaying the actual user interface the log output
is routed to the debug output. DebugView is a very lean program for displaying is routed to the debug output. DebugView is a very lean program for displaying
the debug output in case no debugger is active and does so. It is available at the debug output in case no debugger is active and does so. It is available at
http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx. http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx.