# FreeRTOS+TCP HW Timestamping Option

**URL:** <https://forums.freertos.org/t/freertos-tcp-hw-timestamping-option/8458>\
**Category:** Libraries\
**Created:** [December 18, 2019, 10:12pm UTC](https://forums.freertos.org/t/freertos-tcp-hw-timestamping-option/8458 "2019-12-18T22:12:31Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![htibosch](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/htibosch/32/62_2.png) [@htibosch](https://forums.freertos.org/u/htibosch)\
**Post date:** [December 19, 2019, 5:33am UTC](https://forums.freertos.org/t/freertos-tcp-hw-timestamping-option/8458/5 "2019-12-19T05:33:10Z")

</div>

The development of a general-purpose library is often guided by 2 contradicting desires: the wish to make it as complete as possible, and on the other hand, the wish to keep things simple. TCP Time-stamping has disappeared from the library in order to decrease its complexity.

But it is possibly not TCP time-stamping what you want to do?

Like Richard suggested, you could add a new field to `NetworkBufferDescriptor_t`:

```auto
typedef struct xNETWORK_BUFFER
{
	...
	#if( ipconfigUSE_MESSAGE_TIME_STAMP != 0 )
		uint32_t ulTimeStamp;
	#endif
} NetworkBufferDescriptor_t;

```

Just curiosity: does your application have to do with ( synchronising ) audio?

---

_[View the full topic](https://forums.freertos.org/t/freertos-tcp-hw-timestamping-option/8458)._