koseng1 wrote on Tuesday, July 10, 2018:
Hello,
In the FreeRTOS TCP readme there is the following:
“At this time it is recommended to use BufferAllocation_2.c in which case it is
essential to use the heap_4.c memory allocation scheme:
http://www.FreeRTOS.org/a00111.html”
What were the specific reasons for this statement? Will BufferAllocation1.c eventually become obsolete? I thought 1.c was better if one was trying to avoid dynamic heap allocation. Is that still the case?
Thanks
rtel wrote on Tuesday, July 10, 2018:
I’m not sure of the context. Can you please link to the page that text
is cut from. There is no plan to obsolete BufferAllocation1.c -
although it is a bit harder to use as you need to pre-allocate memory
(sometimes within the network driver itself if the driver has certain
memory alignment requirements).
koseng1 wrote on Tuesday, July 10, 2018:
https://github.com/aws/amazon-freertos/blob/master/lib/FreeRTOS-Plus-TCP/source/readme.txt
Contents of the file:
"
Contains the files that implement FreeRTOS+TCP.
User documentation, including an API reference is available on:
http://www.FreeRTOS.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/
A description of the source code organisation is available on:
http://www.FreeRTOS.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/TCP_Networking_Tutorial.html
The porting guide is available on:
http://www.FreeRTOS.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/FreeRTOS_TCP_Porting.html
License information is available on:
http://www.FreeRTOS.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/FreeRTOS_Plus_TCP_License.html
At this time it is recommended to use BufferAllocation_2.c in which case it is
essential to use the heap_4.c memory allocation scheme:
http://www.FreeRTOS.org/a00111.html
"