[FreeRTOS+TCP API Reference]
BaseType_t FreeRTOS_SendPingRequest( uint32_t ulIPAddress, size_t xNumberOfBytesToSend, TickType_t xBlockTimeTicks );
Send a ping (ICMP echo) request to a remote computer.
ipconfigSUPPORT_OUTGOING_PINGS must be set to 1 in FreeRTOSIPConfig.h for FreeRTOS_SendPingRequest() to be available.
the TCP/IP stack calls the application defined vApplicationPingReplyHook() hook (or callback) function when it receives a reply to an outgoing ping request.
The IP address to which the ping request is sent.
The IP address is expressed as a 32-bit number in network byte order.
The number of data bytes to send in the ping request.
The maximum time the calling RTOS task is prepared to wait
for a network buffer if one is not immediately available.
If a network buffer is not available then the calling RTOS task will be held in the Blocked state (so other tasks can execute) until either a buffer becomes available and therefore the ping request transmitted, or the block time expires.
The block time is specified in ticks. Milliseconds can be converted to ticks by dividing the time in milliseconds by portTICK_PERIOD_MS.
If a ping request is successfully sent then the sequence number sent in the ping message is returned to allow the application writer to match ping requests transmitted with ping replies received. See the example below.
If a ping request could not be sent then pdFAIL is returned.
This example defines two functions. vSendPing() transmits 8 bytes to a remote IP address. vApplicationPingReplyHook() is the standard FreeRTOS+TCP ping reply callback function. vApplicationPingReplyHook() receives the ping reply, then sends the received sequence number to vSendPing() where it is compared to the sequence number from the ping request.
/* FreeRTOS+TCP sockets include. */
/* This example code snippet assumes the queue has already been created! */
/* If ipconfigSUPPORT_OUTGOING_PINGS is set to 1 in FreeRTOSIPConfig.h then
vApplicationPingReplyHook() is called by the TCP/IP stack when the stack receives a
void vApplicationPingReplyHook( ePingReplyStatus_t eStatus, uint16_t usIdentifier )
switch( eStatus )
case eSuccess :
/* A valid ping reply has been received. Post the sequence number
on the queue that is read by the vSendPing() function below. Do
not wait more than 10ms trying to send the message if it cannot be
sent immediately because this function is called from the TCP/IP
RTOS task – blocking in this function will block the TCP/IP RTOS task. */
xQueueSend( xPingReplyQueue, &usIdentifier, 10 / portTICK_PERIOD_MS );
case eInvalidChecksum :
case eInvalidData :
/* A reply was received but it was not valid. */
BaseType_t vSendPing( const int8_t *pcIPAddress )
uint16_t usRequestSequenceNumber, usReplySequenceNumber;
/* The pcIPAddress parameter holds the destination IP address as a string in
decimal dot notation (for example, “192.168.0.200”). Convert the string into
the required 32-bit format. */
ulIPAddress = FreeRTOS_inet_addr( pcIPAddress );
/* Send a ping containing 8 data bytes. Wait (in the Blocked state) a
maximum of 100ms for a network buffer into which the generated ping request
can be written and sent. */
usRequestSequenceNumber = FreeRTOS_SendPingRequest( ulIPAddress, 8, 100 / portTICK_PERIOD_MS );
if( usRequestSequenceNumber == pdFAIL )
/* The ping could not be sent because a network buffer could not be
obtained within 100ms of FreeRTOS_SendPingRequest() being called. */
/* The ping was sent. Wait 200ms for a reply. The sequence number from
each reply is sent from the vApplicationPingReplyHook() on the
xPingReplyQueue queue (this is not standard behaviour, but implemented in
the example function above). It is assumed the queue was created before
this function was called! */
if( xQueueReceive( xPingReplyQueue,
200 / portTICK_PERIOD_MS ) == pdPASS )
/* A ping reply was received. Was it a reply to the ping just sent? */
if( usRequestSequenceNumber == usReplySequenceNumber )
/* This was a reply to the request just sent. */
Example use of the FreeRTOS_SendPingRequest() API function