Hi all, im now dying of getting the example project “FreeRTOS+TCP and FreeRTOS+FAT Examples
Using the FreeRTOS Windows Port ” run under the Winodws Simulator, maybe some of you can give some hope. I did everything excatly as the example description says, the only problem is that my host pc is connected to a wlan repeater using ethernet, i dont know if it is the problem that the FreeRTOS can not use the DHCP server on it , but anyway, i shutted it down by setting the* ipconfigUSEDHCP* to 0. Now i got all FreeRTOS IP initialization done and the IP configuration will be recognized:
~~~
The following network interfaces are available:

Interface 1 – rpcap://DeviceNPF_{D17BDD20-0D3F-4FEA-A117-248AF89AA803}
(Network adapter ‘Intel(R) Ethernet Connection (2) I219-V’ on local host)

The interface that will be opened is set by “configNETWORKINTERFACETO_USE”, which
should be defined in FreeRTOSConfig.h
Attempting to open interface number 1.
0 15 [IP-task]

IP Address: 172.25.218.200
1 15 [IP-task] Subnet Mask: 255.255.0.0
2 15 [IP-task] Gateway Address: 172.25.218.1
3 15 [IP-task] DNS Server Address: 208.67.222.222
~~~
But when i follow the instruction to try ping this RTOSDemo, it didn’t work, no matter with the host name or with ip address:
~~~
C:UsersJason>ping RTOSDemo
Ping-Anforderung konnte Host “RTOSDemo” nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut.

C:UsersJason>ping 172.25.218.200

Ping wird ausgeführt für 172.25.218.200 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 172.25.218.200:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),
~~~
Actually i also tryed this in my office, my laptop there was connected to a normal switch using ethernet, and still it didn’t work, i mean i can not ping this demo either. The only difference is that i could use DHCP configuration in my office and magicly all the IP configuration of FreeRTOS will be set exactly the same as my real windows network.
Does any of you guys have an idea how to fix this problem? My original attention is to use this FreeRTOS windows simulator to connect a MQTT server through TCP in our office to publish and subscribe, if some one did this before, that would be more than great if you can send me a demo to my email, pretty girl photos or any other advise like and throw FreeRTOS away out of my project is also welcome.
Thanks !!!

By the way, windows 7 and windows 10 are used by me in office and at home, WinPcap is also installed.

Do you have configREPLYTOINCOMINGPINGS set to 1? (https://www.freertos.org/FreeRTOS-Plus/FreeRTOSPlusTCP/TCPIPConfiguration.html#ipconfigREPLYTOINCOMINGPINGS )

There is also a Windows Simulator project that includes MQTT with TLS here https://github.com/aws/amazon-freertos/tree/master/demos/pc/windows/visual_studio

Hi, i’ve already checked the define of ipconfigREPLYTOINCOMINGPINGS, it is set to 1, it seemd not to be the problem. And i tried something else using FreeRTOS_Socket and FreeRTOS_bind API, which is also the example code from the official site:
~~~
void aFunction(void)
{
/* Variable to hold the created socket. */
Socket_t xSocket;
struct freertos_sockaddr xBindAddress;

/* Create a UDP socket. */
xSocket = FreeRTOS_socket(FREERTOS_AF_INET,
    FREERTOS_SOCK_DGRAM,
    FREERTOS_IPPROTO_UDP);

/* Check the socket was created successfully. */
if (xSocket != FREERTOS_INVALID_SOCKET)
{
    /* The socket was created successfully and can now be used to send data
    using the FreeRTOS_sendto() API function.  Sending to a socket that has
    not first been bound will result in the socket being automatically bound
    to a port number.  Use FreeRTOS_bind() to bind the socket to a
    specific port number.  This example binds the socket to port 9999.  The
    port number is specified in network byte order, so FreeRTOS_htons() is
    used. */
    xBindAddress.sin_port = FreeRTOS_htons(9999);
    if (FreeRTOS_bind(xSocket, &xBindAddress, sizeof(&xBindAddress)) == 0)
    {
        /* The bind was successful. */
    }
}
else
{
    /* There was insufficient FreeRTOS heap memory available for the socket
    to be created. */
}

}
~~~
I called this function in my vApplicationIPNetworkEventHook and used debug to see if anything didn’t work. FreeRTOS_Socket works fine, i could get a socket successfully, the problem is the FreeRTOS_bind, i found that i could not bind my socket to any port.
~~~
BaseTypet FreeRTOSbind( Sockett xSocket, struct freertossockaddr * pxAddress, socklent xAddressLength )
{
IPStackEventt xBindEvent;
FreeRTOSSockett *pxSocket = ( FreeRTOS_Socket_t * ) xSocket;
BaseType_t xReturn = 0;

( void ) xAddressLength;

if( ( pxSocket == NULL ) || ( pxSocket == FREERTOS_INVALID_SOCKET ) )
{
    xReturn = -pdFREERTOS_ERRNO_EINVAL;
}
/* Once a socket is bound to a port, it can not be bound to a different
port number */
else if( socketSOCKET_IS_BOUND( pxSocket) != pdFALSE )
{
    /* The socket is already bound. */
    FreeRTOS_debug_printf( ( "vSocketBind: Socket already bound to %dn", pxSocket->usLocalPort ) );
    xReturn = -pdFREERTOS_ERRNO_EINVAL;
}
else
{
    /* Prepare a messages to the IP-task in order to perform the binding.
    The desired port number will be passed in usLocalPort. */
    xBindEvent.eEventType = eSocketBindEvent;
    xBindEvent.pvData = ( void * ) xSocket;
    if( pxAddress != NULL )
    {
        pxSocket->usLocalPort = FreeRTOS_ntohs( pxAddress->sin_port );
    }
    else
    {
        /* Caller wants to bind to a random port number. */
        pxSocket->usLocalPort = 0u;
    }

    /* portMAX_DELAY is used as a the time-out parameter, as binding *must*
    succeed before the socket can be used.  _RB_ The use of an infinite
    block time needs be changed as it could result in the task hanging. */
    if( xSendEventStructToIPTask( &xBindEvent, ( TickType_t ) portMAX_DELAY ) == pdFAIL )
    {
        /* Failed to wake-up the IP-task, no use to wait for it */
        FreeRTOS_debug_printf( ( "FreeRTOS_bind: send event failedn" ) );
        xReturn = -pdFREERTOS_ERRNO_ECANCELED;
    }
    else
    {
        /* The IP-task will set the 'eSOCKET_BOUND' bit when it has done its
        job. */
        xEventGroupWaitBits( pxSocket->xEventGroup, eSOCKET_BOUND, pdTRUE /*xClearOnExit*/, pdFALSE /*xWaitAllBits*/, portMAX_DELAY );
        if( socketSOCKET_IS_BOUND( pxSocket ) == pdFALSE )
        {
            xReturn = -pdFREERTOS_ERRNO_EINVAL;
        }
    }
}
return xReturn;

}
~~~
Be more specific, everything works great in FreeRTOS_bind until bind event is sent to IPTask by xSendEventStructToIPTask and wait for the eSOCKET_BOUND status from IPTask using xEventGroupWaitBits. Ever since xEventGroupWaitBits is called, it is the end of the world, eSOCKET_BOUND will never be returned, and the function call will never jump back even that i set portMAX_DELAY to like 10 ticks, basicly the function is totally dead…
Maybe you have any other idea? Or should i burn my computer and buy a new one?
Thank you for the kind answer and wait for reply.

Hi Jiaxin Long, vApplicationIPNetworkEventHook() is being called from the IP-task, and it is not allowed to call FreeRTOS_bind() from within the IP-task.
The best solution is to keep vApplicationIPNetworkEventHook() very short, just set a variable:

~~~

BaseType_t xMustCreateSockets = pdFALSE;
extern void vCreateSockets();

void vApplicationIPNetworkEventHook()
{
/* If the network has just come up…/
if( eNetworkEvent == eNetworkUp )
{
/ Remember that sockets must be created. */
xMustCreateSockets = pdTRUE;
}
}

~~~

And check this variable from within on of your tasks:

~~~

void vMyTask( void *pvArg )
{
for( ;; )
{
if( xMustCreateSockets != pdFALSE )
{
xMustCreateSockets = pdFALSE;
vCreateSockets();
}
}
}

~~~

Another possibility is to created your tasks from within the hook, as is being done in the FreeRTOS+TCP example projects.

What we should have done is write in the documentation that blocking +TCP API’s may not be called.

Also we’d better add a configASSERT() in FreeRTOS_bind():

~~~
BaseTypet FreeRTOSbind( Sockett xSocket, struct freertossockaddr * pxAddress, socklent xAddressLength )
{
IPStackEventt xBindEvent;
FreeRTOSSockett *pxSocket = ( FreeRTOS_Socket_t * ) xSocket;
BaseType_t xReturn = 0;

 ( void ) xAddressLength;

• configASSERT( xIsCallingFromIPTask() == pdFALSE );
  ~~~

So it will assert in case FreeRTOS_bind() is called from vApplicationIPNetworkEventHook() or other application hooks.

Maybe you have any other idea? Or should I burn my computer and buy a new one?

There is hope 🙂
We’re sorry for the inconvenience that it has caused you

Hi hein, thank you so much!! I tried your solution and it did work! Now the port binding problem is solved, one reason less to kill my pc, but it doesn’t mean he is safe…I still can not ping my RTOSDemo! I think the IP address of FreeRTOS should be available after the IPInit call right? Even if i bind the socket to a port, my RTOSDemo is still a black-(ass)-hole…Or should i do something more? Basicly i want to ask, is it possible to create a tcp port under windows simulator and use it communicate with a real world ip address? Or it is just as stupid as my other fantasy like”im rich”…? As long as i don’t get an answer, i can only blame my stupid pc…
As usual, if it is possible, a simplest example code will be great!
Thank again for the reply and 2 sexy kisses from pretty blond girl are sent to you via my brain, you are welcome.

is it possible to create a tcp port under windows simulator and
use it communicate with a real world ip address?

The Windows port is at the same time very real as it is a simulation.
The Ethernet driver must bypass the Windows’ IP-stack and so it uses WinPcap.

As usual, if it is possible, a simplest example code will be great!

The example code can be found in the ZIP file found here

There are two sample projects:

FreeRTOS-PlusDemoFreeRTOS_Plus_TCP_Minimal_Windows_Simulator
FreeRTOS-PlusDemoFreeRTOS_Plus_TCP_and_FAT_Windows_Simulator

Mind you that release 160919 is somewhat old by now. You better use the latest releases found on AWS. You will find both the latest kernel (V10.0.1), all ports and the latest release of FreeRTOS+TCP.

Could you post 2 files of your project please: FreeRTOSConfig.h and FreeRTOSIPConfig.h?

Hi hein, you are really my hero! As requested, hier are my FreeRTOSConfig.h and FreeRTOSIPConfig.h files:

FreeRTOSConfig.h :
~~~
/*
* FreeRTOS Kernel V10.0.1
* Copyright (C) 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy of
* this software and associated documentation files (the “Software”), to deal in
* the Software without restriction, including without limitation the rights to
* use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
* the Software, and to permit persons to whom the Software is furnished to do so,
* subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in all
* copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
* FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
* COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
* IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*
* http://www.FreeRTOS.org
* http://aws.amazon.com/freertos
*
* 1 tab == 4 spaces!
*/

ifndef FREERTOSCONFIGH

define FREERTOSCONFIGH

/———————————————————–
* Application specific definitions.
*
* These definitions should be adjusted for your particular hardware and
* application requirements.
*
* THESE PARAMETERS ARE DESCRIBED WITHIN THE ‘CONFIGURATION’ SECTION OF THE
* FreeRTOS API DOCUMENTATION AVAILABLE ON THE FreeRTOS.org WEB SITE.
* http://www.freertos.org/a00110.html
*
* The bottom of this file contains some constants specific to running the UDP
* stack in this demo. Constants specific to FreeRTOS+TCP itself (rather than
* the demo) are contained in FreeRTOSIPConfig.h.
*———————————————————-/

define configENABLEBACKWARDCOMPATIBILITY 0

define configUSE_PREEMPTION 1

define configUSEPORTOPTIMISEDTASKSELECTION 1

define configMAX_PRIORITIES ( 7 )

define configTICKRATEHZ ( 1000 ) /* In this non-real time simulated environment the tick frequency has to be at least a multiple of the Win32 tick frequency, and therefore very slow. */

define configMINIMALSTACKSIZE ( ( unsigned short ) 60 ) /* In this simulated case, the stack only has to hold one small structure as the real stack is part of the Win32 thread. */

define configTOTALHEAPSIZE ( ( size_t ) ( 2048U * 1024U ) )

define configMAXTASKNAME_LEN ( 15 )

define configUSETRACEFACILITY 1

define configUSE16BIT_TICKS 1

define configIDLESHOULDYIELD 1

define configUSECOROUTINES 0

define configUSE_MUTEXES 1

define configUSERECURSIVEMUTEXES 1

define configQUEUEREGISTRYSIZE 1

define configUSEAPPLICATIONTASK_TAG 1

define configUSECOUNTINGSEMAPHORES 1

define configUSEALTERNATIVEAPI 0

define configNUMTHREADLOCALSTORAGEPOINTERS 3 /* FreeRTOS+FAT requires 2 pointers if a CWD is supported. */

/* Hook function related definitions. */

define configUSETICKHOOK 0

define configUSEIDLEHOOK 1

define configUSEMALLOCFAILED_HOOK 1

define configCHECKFORSTACK_OVERFLOW 0 /* Not applicable to the Win32 port. */

/* Software timer related definitions. */

define configUSE_TIMERS 1

define configTIMERTASKPRIORITY ( configMAX_PRIORITIES – 1 )

define configTIMERQUEUELENGTH 5

define configTIMERTASKSTACKDEPTH ( configMINIMALSTACK_SIZE * 2 )

/* Event group related definitions. */

define configUSEEVENTGROUPS 1

/* Run time stats gathering definitions. */

define configGENERATERUNTIME_STATS 0

/* Co-routine definitions. */

define configUSECOROUTINES 0

define configMAXCOROUTINE_PRIORITIES ( 2 )

/* Set the following definitions to 1 to include the API function, or zero
to exclude the API function. */

define INCLUDE_vTaskPrioritySet 1

define INCLUDE_uxTaskPriorityGet 1

define INCLUDE_vTaskDelete 1

define INCLUDE_vTaskCleanUpResources 0

define INCLUDE_vTaskSuspend 1

define INCLUDE_vTaskDelayUntil 1

define INCLUDE_vTaskDelay 1

define INCLUDE_uxTaskGetStackHighWaterMark 1

define INCLUDE_xTaskGetSchedulerState 1

define INCLUDE_xTimerGetTimerTaskHandle 0

define INCLUDE_xTaskGetIdleTaskHandle 0

define INCLUDE_xQueueGetMutexHolder 1

define INCLUDE_eTaskGetState 1

define INCLUDE_xEventGroupSetBitsFromISR 1

define INCLUDE_xTimerPendFunctionCall 1

define INCLUDE_pcTaskGetTaskName 1

/* This demo makes use of one or more example stats formatting functions. These
format the raw data provided by the uxTaskGetSystemState() function in to human
readable ASCII form. See the notes in the implementation of vTaskList() within
FreeRTOS/Source/tasks.c for limitations. configUSESTATSFORMATTING_FUNCTIONS
is set to 2 so the formatting functions are included without the stdio.h being
included in tasks.c. That is because this project defines its own sprintf()
functions. */

define configUSESTATSFORMATTING_FUNCTIONS 1

/* Assert call defined for debug builds. */

ifdef _DEBUG

extern void vAssertCalled( const char *pcFile, uint32_t ulLine );
#define configASSERT( x ) if( ( x ) == 0 ) vAssertCalled( __FILE__, __LINE__ )

endif /* _DEBUG */

/* Application specific definitions follow. **********************************/

/* If configINCLUDEDEMODEBUG_STATS is set to one, then a few basic IP trace
macros are defined to gather some UDP stack statistics that can then be viewed
through the CLI interface. */

define configINCLUDEDEMODEBUG_STATS 1

/* The size of the global output buffer that is available for use when there
are multiple command interpreters running at once (for example, one on a UART
and one on TCP/IP). This is done to prevent an output buffer being defined by
each implementation – which would waste RAM. In this case, there is only one
command interpreter running, and it has its own local output buffer, so the
global buffer is just set to be one byte long as it is not used and should not
take up unnecessary RAM. */

define configCOMMANDINTMAXOUTPUTSIZE 1

/* Only used when running in the FreeRTOS Windows simulator. Defines the
priority of the task used to simulate Ethernet interrupts. */

define configMACISRSIMULATORPRIORITY ( configMAXPRIORITIES – 1 )

/* This demo creates a virtual network connection by accessing the raw Ethernet
or WiFi data to and from a real network connection. Many computers have more
than one real network port, and configNETWORKINTERFACETOUSE is used to tell
the demo which real port should be used to create the virtual port. The ports
available are displayed on the console when the application is executed. For
example, on my development laptop setting configNETWORKINTERFACETOUSE to 4
results in the wired network being used, while setting
configNETWORKINTERFACETO_USE to 2 results in the wireless network being
used. */

define configNETWORKINTERFACETO_USE 1L

/* The address of an echo server that will be used by the two demo echo client
tasks.
http://www.freertos.org/FreeRTOS-Plus/FreeRTOSPlusTCP/TCPEchoClients.html
http://www.freertos.org/FreeRTOS-Plus/FreeRTOSPlusTCP/UDPEchoClients.html */

define configECHOSERVERADDR0 192

define configECHOSERVERADDR1 168

define configECHOSERVERADDR2 0

define configECHOSERVERADDR3 11

/* Default MAC address configuration. The demo creates a virtual network
connection that uses this MAC address by accessing the raw Ethernet/WiFi data
to and from a real network connection on the host PC. See the
configNETWORKINTERFACETO_USE definition above for information on how to
configure the real network connection to use. */

define configMAC_ADDR0 0x00

define configMAC_ADDR1 0x11

define configMAC_ADDR2 0x22

define configMAC_ADDR3 0x33

define configMAC_ADDR4 0x44

define configMAC_ADDR5 0x41

/* Default IP address configuration. Used in ipconfigUSEDNS is set to 0, or
ipconfigUSEDNS is set to 1 but a DNS server cannot be contacted. */

define configIP_ADDR0 172

define configIP_ADDR1 25

define configIP_ADDR2 218

define configIP_ADDR3 200

/* Default gateway IP address configuration. Used in ipconfigUSEDNS is set to
0, or ipconfigUSEDNS is set to 1 but a DNS server cannot be contacted. */

define configGATEWAY_ADDR0 172

define configGATEWAY_ADDR1 25

define configGATEWAY_ADDR2 218

define configGATEWAY_ADDR3 1

/* Default DNS server configuration. OpenDNS addresses are 208.67.222.222 and
208.67.220.220. Used in ipconfigUSEDNS is set to 0, or ipconfigUSEDNS is set
to 1 but a DNS server cannot be contacted.*/

define configDNSSERVERADDR0 208

define configDNSSERVERADDR1 67

define configDNSSERVERADDR2 222

define configDNSSERVERADDR3 222

/* Default netmask configuration. Used in ipconfigUSEDNS is set to 0, or
ipconfigUSEDNS is set to 1 but a DNS server cannot be contacted. */

define configNET_MASK0 255

define configNET_MASK1 255

define configNET_MASK2 0

define configNET_MASK3 0

/* The UDP port to which print messages are sent. */

define configPRINT_PORT ( 15000 )

if( defined( MSCVER ) && ( MSCVER <= 1600 ) && !defined( snprintf ) )

/* Map to Windows names. */
#define snprintf    _snprintf
#define vsnprintf   _vsnprintf

endif

/* Visual studio does not have an implementation of strcasecmp(). */

define strcasecmp _stricmp

define strncasecmp _strnicmp

define strcmpi _strcmpi

endif /* FREERTOSCONFIGH */

~~~

and the FreeRTOSIPConfig.h
~~~
/*
* FreeRTOS Kernel V10.0.1
* Copyright (C) 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy of
* this software and associated documentation files (the “Software”), to deal in
* the Software without restriction, including without limitation the rights to
* use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
* the Software, and to permit persons to whom the Software is furnished to do so,
* subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in all
* copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
* FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
* COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
* IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*
* http://www.FreeRTOS.org
* http://aws.amazon.com/freertos
*
* 1 tab == 4 spaces!
*/

/*****************************************************************************
*
* See the following URL for configuration information.
* http://www.freertos.org/FreeRTOS-Plus/FreeRTOSPlusTCP/TCPIPConfiguration.html
*
*****************************************************************************/

ifndef FREERTOSIPCONFIG_H

define FREERTOSIPCONFIG_H

/* Prototype for the function used to print out. In this case it prints to the
console before the network is connected then a UDP port after the network has
connected. */
extern void vLoggingPrintf( const char *pcFormatString, … );

/* Set to 1 to print out debug messages. If ipconfigHASDEBUGPRINTF is set to
1 then FreeRTOSdebugprintf should be defined to the function used to print
out the debugging messages. */

define ipconfigHASDEBUGPRINTF 0

if( ipconfigHASDEBUGPRINTF == 1 )

#define FreeRTOS_debug_printf(X)    vLoggingPrintf X

endif

/* Set to 1 to print out non debugging messages, for example the output of the
FreeRTOSnetstat() command, and ping replies. If ipconfigHASPRINTF is set to 1
then FreeRTOS_printf should be set to the function used to print out the
messages. */

define ipconfigHAS_PRINTF 1

if( ipconfigHAS_PRINTF == 1 )

#define FreeRTOS_printf(X)          vLoggingPrintf X

endif

/* Define the byte order of the target MCU (the MCU FreeRTOS+TCP is executing
on). Valid options are pdFREERTOSBIGENDIAN and pdFREERTOSLITTLEENDIAN. */

define ipconfigBYTEORDER pdFREERTOSLITTLE_ENDIAN

/* If the network card/driver includes checksum offloading (IP/TCP/UDP checksums)
then set ipconfigDRIVERINCLUDEDRXIPCHECKSUM to 1 to prevent the software
stack repeating the checksum calculations. */

define ipconfigDRIVERINCLUDEDRXIPCHECKSUM 1

/* Several API’s will block until the result is known, or the action has been
performed, for example FreeRTOSsend() and FreeRTOSrecv(). The timeouts can be
set per socket, using setsockopt(). If not set, the times below will be
used as defaults. */

define ipconfigSOCKDEFAULTRECEIVEBLOCKTIME ( 5000 )

define ipconfigSOCKDEFAULTSENDBLOCKTIME ( 5000 )

/* Include support for LLMNR: Link-local Multicast Name Resolution
(non-Microsoft) */

define ipconfigUSE_LLMNR ( 1 )

/* Include support for NBNS: NetBIOS Name Service (Microsoft) */

define ipconfigUSE_NBNS ( 1 )

/* Include support for DNS caching. For TCP, having a small DNS cache is very
useful. When a cache is present, ipconfigDNSREQUESTATTEMPTS can be kept low
and also DNS may use small timeouts. If a DNS reply comes in after the DNS
socket has been destroyed, the result will be stored into the cache. The next
call to FreeRTOS_gethostbyname() will return immediately, without even creating
a socket. */

define ipconfigUSEDNSCACHE ( 1 )

define ipconfigDNSCACHENAME_LENGTH ( 16 )

define ipconfigDNSCACHEENTRIES ( 4 )

define ipconfigDNSREQUESTATTEMPTS ( 2 )

/* The IP stack executes it its own task (although any application task can make
use of its services through the published sockets API). ipconfigUDPTASKPRIORITY
sets the priority of the task that executes the IP stack. The priority is a
standard FreeRTOS task priority so can take any value from 0 (the lowest
priority) to (configMAXPRIORITIES – 1) (the highest priority).
configMAXPRIORITIES is a standard FreeRTOS configuration parameter defined in
FreeRTOSConfig.h, not FreeRTOSIPConfig.h. Consideration needs to be given as to
the priority assigned to the task executing the IP stack relative to the
priority assigned to tasks that use the IP stack. */

define ipconfigIPTASKPRIORITY ( configMAX_PRIORITIES – 2 )

/* The size, in words (not bytes), of the stack allocated to the FreeRTOS+TCP
task. This setting is less important when the FreeRTOS Win32 simulator is used
as the Win32 simulator only stores a fixed amount of information on the task
stack. FreeRTOS includes optional stack overflow detection, see:
http://www.freertos.org/Stacks-and-stack-overflow-checking.html */

define ipconfigIPTASKSTACKSIZEWORDS ( configMINIMALSTACKSIZE * 5 )

/* ipconfigRAND32() is called by the IP stack to generate random numbers for
things such as a DHCP transaction number or initial sequence number. Random
number generation is performed via this macro to allow applications to use their
own random number generation method. For example, it might be possible to
generate a random number by sampling noise on an analogue input. */
extern UBaseType_t uxRand();

define ipconfigRAND32() uxRand()

/* If ipconfigUSENETWORKEVENTHOOK is set to 1 then FreeRTOS+TCP will call the
network event hook at the appropriate times. If ipconfigUSENETWORKEVENTHOOK
is not set to 1 then the network event hook will never be called. See
http://www.FreeRTOS.org/FreeRTOS-Plus/FreeRTOSPlusUDP/API/vApplicationIPNetworkEventHook.shtml
*/

define ipconfigUSENETWORKEVENT_HOOK 1

/* Sockets have a send block time attribute. If FreeRTOSsendto() is called but
a network buffer cannot be obtained then the calling task is held in the Blocked
state (so other tasks can continue to executed) until either a network buffer
becomes available or the send block time expires. If the send block time expires
then the send operation is aborted. The maximum allowable send block time is
capped to the value set by ipconfigMAXSENDBLOCKTIMETICKS. Capping the
maximum allowable send block time prevents prevents a deadlock occurring when
all the network buffers are in use and the tasks that process (and subsequently
free) the network buffers are themselves blocked waiting for a network buffer.
ipconfigMAXSENDBLOCKTIMETICKS is specified in RTOS ticks. A time in
milliseconds can be converted to a time in ticks by dividing the time in
milliseconds by portTICKPERIOD_MS. */

define ipconfigUDPMAXSENDBLOCKTIMETICKS ( 5000 / portTICKPERIOD_MS )

/* If ipconfigUSEDHCP is 1 then FreeRTOS+TCP will attempt to retrieve an IP
address, netmask, DNS server address and gateway address from a DHCP server. If
ipconfigUSEDHCP is 0 then FreeRTOS+TCP will use a static IP address. The
stack will revert to using the static IP address even when ipconfigUSEDHCP is
set to 1 if a valid configuration cannot be obtained from a DHCP server for any
reason. The static configuration used is that passed into the stack by the
FreeRTOSIPInit() function call. */

define ipconfigUSE_DHCP 0

/* When ipconfigUSEDHCP is set to 1, DHCP requests will be sent out at
increasing time intervals until either a reply is received from a DHCP server
and accepted, or the interval between transmissions reaches
ipconfigMAXIMUMDISCOVERTXPERIOD. The IP stack will revert to using the
static IP address passed as a parameter to FreeRTOSIPInit() if the
re-transmission time interval reaches ipconfigMAXIMUMDISCOVERTXPERIOD without
a DHCP reply being received. */

define ipconfigMAXIMUMDISCOVERTXPERIOD ( 120000 / portTICKPERIOD_MS )

/* The ARP cache is a table that maps IP addresses to MAC addresses. The IP
stack can only send a UDP message to a remove IP address if it knowns the MAC
address associated with the IP address, or the MAC address of the router used to
contact the remote IP address. When a UDP message is received from a remote IP
address the MAC address and IP address are added to the ARP cache. When a UDP
message is sent to a remote IP address that does not already appear in the ARP
cache then the UDP message is replaced by a ARP message that solicits the
required MAC address information. ipconfigARPCACHEENTRIES defines the maximum
number of entries that can exist in the ARP table at any one time. */

define ipconfigARPCACHEENTRIES 6

/* ARP requests that do not result in an ARP response will be re-transmitted a
maximum of ipconfigMAXARPRETRANSMISSIONS times before the ARP request is
aborted. */

define ipconfigMAXARPRETRANSMISSIONS ( 5 )

/* ipconfigMAXARPAGE defines the maximum time between an entry in the ARP
table being created or refreshed and the entry being removed because it is stale.
New ARP requests are sent for ARP cache entries that are nearing their maximum
age. ipconfigMAXARPAGE is specified in tens of seconds, so a value of 150 is
equal to 1500 seconds (or 25 minutes). */

define ipconfigMAXARPAGE 150

/* Implementing FreeRTOSinetaddr() necessitates the use of string handling
routines, which are relatively large. To save code space the full
FreeRTOSinetaddr() implementation is made optional, and a smaller and faster
alternative called FreeRTOSinetaddrquick() is provided. FreeRTOSinetaddr()
takes an IP in decimal dot format (for example, “192.168.0.1”) as its parameter.
FreeRTOSinetaddrquick() takes an IP address as four separate numerical octets
(for example, 192, 168, 0, 1) as its parameters. If
ipconfigINCLUDEFULLINETADDR is set to 1 then both FreeRTOSinetaddr() and
FreeRTOSindetaddrquick() are available. If ipconfigINCLUDEFULLINETADDR is
not set to 1 then only FreeRTOSindetaddrquick() is available. */

define ipconfigINCLUDEFULLINET_ADDR 1

/* ipconfigNUMNETWORKBUFFER_DESCRIPTORS defines the total number of network buffer that
are available to the IP stack. The total number of network buffers is limited
to ensure the total amount of RAM that can be consumed by the IP stack is capped
to a pre-determinable value. */

define ipconfigNUMNETWORKBUFFER_DESCRIPTORS 60

/* A FreeRTOS queue is used to send events from application tasks to the IP
stack. ipconfigEVENTQUEUELENGTH sets the maximum number of events that can
be queued for processing at any one time. The event queue must be a minimum of
5 greater than the total number of network buffers. */

define ipconfigEVENTQUEUELENGTH ( ipconfigNUMNETWORKBUFFER_DESCRIPTORS + 5 )

/* The address of a socket is the combination of its IP address and its port
number. FreeRTOSbind() is used to manually allocate a port number to a socket
(to ‘bind’ the socket to a port), but manual binding is not normally necessary
for client sockets (those sockets that initiate outgoing connections rather than
wait for incoming connections on a known port number). If
ipconfigALLOWSOCKETSENDWITHOUTBIND is set to 1 then calling
FreeRTOSsendto() on a socket that has not yet been bound will result in the IP
stack automatically binding the socket to a port number from the range
socketAUTOPORTALLOCATIONSTARTNUMBER to 0xffff. If
ipconfigALLOWSOCKETSENDWITHOUTBIND is set to 0 then calling FreeRTOS_sendto()
on a socket that has not yet been bound will result in the send operation being
aborted. */

define ipconfigALLOWSOCKETSENDWITHOUTBIND 1

/* Defines the Time To Live (TTL) values used in outgoing UDP packets. */

define ipconfigUDPTIMETO_LIVE 128

define ipconfigTCPTIMETO_LIVE 128 /* also defined in FreeRTOSIPConfigDefaults.h */

/* USE_TCP: Use TCP and all its features */

define ipconfigUSE_TCP ( 1 )

/* USE_WIN: Let TCP use windowing mechanism. */

define ipconfigUSETCPWIN ( 1 )

/* The MTU is the maximum number of bytes the payload of a network frame can
contain. For normal Ethernet V2 frames the maximum MTU is 1500. Setting a
lower value can save RAM, depending on the buffer management scheme used. If
ipconfigCANFRAGMENTOUTGOINGPACKETS is 1 then (ipconfigNETWORKMTU – 28) must
be divisible by 8. */

define ipconfigNETWORK_MTU 1200

/* Set ipconfigUSEDNS to 1 to include a basic DNS client/resolver. DNS is used
through the FreeRTOSgethostbyname() API function. */

define ipconfigUSE_DNS 1

/* If ipconfigREPLYTOINCOMING_PINGS is set to 1 then the IP stack will
generate replies to incoming ICMP echo (ping) requests. */

define ipconfigREPLYTOINCOMING_PINGS 1

/* If ipconfigSUPPORTOUTGOINGPINGS is set to 1 then the
FreeRTOS_SendPingRequest() API function is available. */

define ipconfigSUPPORTOUTGOINGPINGS 0

/* If ipconfigSUPPORTSELECTFUNCTION is set to 1 then the FreeRTOS_select()
(and associated) API function is available. */

define ipconfigSUPPORTSELECTFUNCTION 1

/* If ipconfigFILTEROUTNONETHERNETII_FRAMES is set to 1 then Ethernet frames
that are not in Ethernet II format will be dropped. This option is included for
potential future IP stack developments. */

define ipconfigFILTEROUTNONETHERNETII_FRAMES 1

/* If ipconfigETHERNETDRIVERFILTERSFRAMETYPES is set to 1 then it is the
responsibility of the Ethernet interface to filter out packets that are of no
interest. If the Ethernet interface does not implement this functionality, then
set ipconfigETHERNETDRIVERFILTERSFRAMETYPES to 0 to have the IP stack
perform the filtering instead (it is much less efficient for the stack to do it
because the packet will already have been passed into the stack). If the
Ethernet driver does all the necessary filtering in hardware then software
filtering can be removed by using a value other than 1 or 0. */

define ipconfigETHERNETDRIVERFILTERSFRAMETYPES 1

/* The windows simulator cannot really simulate MAC interrupts, and needs to
block occasionally to allow other tasks to run. */

define configWINDOWSMACINTERRUPTSIMULATORDELAY ( 20 / portTICKPERIODMS )

/* Advanced only: in order to access 32-bit fields in the IP packets with
32-bit memory instructions, all packets will be stored 32-bit-aligned, plus 16-bits.
This has to do with the contents of the IP-packets: all 32-bit fields are
32-bit-aligned, plus 16-bit(!) */

define ipconfigPACKETFILLERSIZE 2

/* Define the size of the pool of TCP window descriptors. On the average, each
TCP socket will use up to 2 x 6 descriptors, meaning that it can have 2 x 6
outstanding packets (for Rx and Tx). When using up to 10 TP sockets
simultaneously, one could define TCPWINSEG_COUNT as 120. */

define ipconfigTCPWINSEG_COUNT 240

/* Each TCP socket has a circular buffers for Rx and Tx, which have a fixed
maximum size. Define the size of Rx buffer for TCP sockets. */

define ipconfigTCPRXBUFFER_LENGTH ( 1000 )

/* Define the size of Tx buffer for TCP sockets. */

define ipconfigTCPTXBUFFER_LENGTH ( 1000 )

/* When using call-back handlers, the driver may check if the handler points to
real program memory (RAM or flash) or just has a random non-zero value. */

define ipconfigISVALIDPROG_ADDRESS(x) ( (x) != NULL )

/* Include support for TCP hang protection. All sockets in a connecting or
disconnecting stage will timeout after a period of non-activity. */

define ipconfigTCPHANGPROTECTION ( 1 )

define ipconfigTCPHANGPROTECTION_TIME ( 30 )

/* Include support for TCP keep-alive messages. */

define ipconfigTCPKEEPALIVE ( 1 )

define ipconfigTCPKEEPALIVE_INTERVAL ( 20 ) /* in seconds */

define portINLINE __inline

endif /* FREERTOSIPCONFIG_H */

~~~

I may have another concern, both in my office and at home are not the normal wired ethernet binding situation, in my office we used a cisco IP telephone, so the ethernet connection sequence is like: router->switch->switch->cisco IP telephone->my laptop.
And at home im using a WiFi repeater, and i connect my pc to this WiFi repeater via a cable, because my computer doesn’t have a wireless ethernet card, so the sequence should be: router->via wlan->repeater->via cable->my pc.
So im not sure if my PC will be treated as “physically connected to a network”. Would this be a problem to run the demo?

And my last question:
If everything is fine, even if i set both
mainCREATE_SIMPLE_UDP_CLIENT_SERVER_TASKS
mainCREATE_TCP_ECHO_TASKS_SINGLE
to 0 for FreeRTOS-PlusDemoFreeRTOSPlusTCPMinimalWindows_Simulator, i should still be able to ping my Demo wenn i run the RTOSDemo.exe, right?

And my last question:
If everything is fine, even if i set both
/mainCREATESIMPLEUDPCLIENTSERVERTASKS/
/mainCREATETCPECHOTASKSSINGLE/
to 0 for
*FreeRTOS-PlusDemoFreeRTOSPlusTCPMinimalWindowsSimulator*, i
should still be able to ping my Demo wenn i run the RTOSDemo.exe, right?

Yes.

That should not be a problem – the Win32 code needs a wired connection
in any case, the WinPCap utility doesn’t work with wireless.

OK, i can only hope that tomorrow the laptop in office won’t extinguish the last spark in my heart …thank you so much

Your application will use IP-address “172.25.218.200”. What is the IP-address of the PC that you use for testing?

I think it is the best to give the application its own unique IP-address. If it is the same as the PC, there will be conflicts.

There is a problem with “ping RTOSDemo” : this will either use LLMNR or NBNS: those are protocols based on UDB broadcasting and multi-casting respectively. I think that the request will end-up in the PC’s IP-stack and it may not reach the application.

So “ping 172.25.218.200” should work in your case.

And if it does not: try to add “172.25.218.200” to your LAN network card so it gets 2 IP-addresses:

~~~
172.25.218.xxx // Your usual PC’s IP address
255.255.0.0 // Net-mask

172.25.218.200  // The IP-address of the application
255.255.0.0     // Net-mask

~~~

It is also possible to use an entirely different IP-address for the application, like e.g. 192.168.1.xxx

Now I’m not sure what happens to the MAC address of the secondary IP-address. Maybe the PC will assign the existing MAC-address from the hardware.

Do you have a second PC connected to the same LAN? Can you try ping from that PC?

If this all doesn’t work, I would start debugging: see if any packets arrive in the driver here:

~~~
/* WinPCAP function. /
void pcap_callback( u_char *user, const struct pcap_pkthdr *pkt_header, const u_char *pkt_data )
{
…
uxStreamBufferAdd( xRecvBuffer, 0, ( const uint8_t ) pktheader, sizeof( *pktheader ) );
uxStreamBufferAdd( xRecvBuffer, 0, ( const uint8t* ) pktdata, ( sizet ) pktheader->caplen );
}
~~~

See if the packets are treated by the IP-task here:

~~~
static void prvIPTask( void pvParameters )
{
…
case eNetworkRxEvent:
/ The network hardware driver has received a new packet. A
pointer to the received buffer is located in the pvData member
of the received event structure. */
prvHandleEthernetPacket( ( NetworkBufferDescriptor_t * ) ( xReceivedEvent.pvData ) );
break;
~~~

And finally, see if any packets gets sent here:

~~~
DWORD WINAPI prvWinPcapSendThread( void pvParam )
{
…
uxStreamBufferGet( xSendBuffer, 0, ( uint8_t * ) &xLength, sizeof( xLength ), pdFALSE );
uxStreamBufferGet( xSendBuffer, 0, ( uint8_t ) ucBuffer, xLength, pdFALSE );
}
~~~

And if the ICMP (=echo) packet doesn’t get answered, you may discover the reason why.

Hi Hein, sorry for the late post, i tried your solution and finally i found out that FreeRTOS_IPInit works all the time, the only problem is that i can not ping my virtuell simulator from the same pc. When i tried this from other pcs in my office, there was no problem. Maybe you know why this happend?

Hi Jiaxin,

The only problem is that I can not ping my virtual simulator from the same pc

I’m not sure about the cause but I had the same problem: I can only test the Windows simulation +TCP project from a different laptop, or from an external embedded device.

Possibly WinPcap only works through a physical Ethernet device, whereas “ping myself” will be directed to a loop-back device and it will never reach WinPcap.

The host PC and the FreeRTOS application using WinPCap should be using
different IP addresses as the WinPCap is ‘sort of’ spoofing a completely
separate network interface. So I don’t think pings would be forwarded
to the loopback interface. I haven’t verified it right now but I’m
pretty sure I don’t have this problem and can ping the WinPCap IP
address from my host address without any problem. Could it be something
to do with the NIC in the PC? Perhaps it’s promiscuous mode is off, or
something like that (guessing).