I have searched the forum in order to find some answer if LPC1769 or LPC1768 has been used with FreeRTOS-TCP by someone successfully. I found closest @ulysses dealt with it at least for LPC1788 which is here (FreeRTOS+TCP for LPC17xx).
I can be considered quite new to FeeRTOS. I have managed to run uIP sample code with FreeRTOS 10.3.1 on my IAR workbench safe and sound. However, I have advised to move on to either lwIP or FreeRTOS-TCP. I believe that this is a good idea when I read some more.
My ultimate goal running those features
Having web interface for some settings (vital)
Running FTP Client (vital)
Firmware upgrade functionality (nice to have)
Advertising my devices in a Local network (vital)
My Questions
(preferred) Would you please tell me if somebody has at least some sample code for LPC1769 device?
(backup) Or instead should I go for lwIP for my device (if it has some known stuff for my device)?
I have already seen NetworkInterface.c from one your posts.
I will give it a try to implement on top of my reasonably working project based on uIP stack and ask here when I need some help (highly likely).
I will come to other parts like LLMNR, NBNS or mDNS after a working base with FreeRTOS+TCP.
However, you didn’t mention about lwIP stack. If we have a solid demo for my device, I can also use it. What do you think? I have to tell, my devices won’t suffer from a heavy network traffic. They will usually talk to a TCP Server once a while only for some particular command exchange between them.
Even furthermore, what if I still stick to uIP stack as it works out of the box with my device, what would be the consequences of it? Limited number of html pages? Less complex, very simple html pages? slow loading pages, unresponsive pages?
Sorry to ask many questions. I am still trying to find my way, a kickstart before getting my hands dirty.
my reasonably working project based on uIP stack and
ask here when I need some help (highly likely).
I liked to use uIP. The only thing is that it has a very peculiar implementation ( due to limitations of resources ). There is no clear difference between the kernel and user tasks, many call-backs. And it is difficult to port a uIP-project to a platform that uses a different IP-stack.
However, you didn’t mention about lwIP stack.
AWS supports lwIP, many of the AWS projects can run on both lwIP and FreeRTOS+TCP. Here on this forum, we only give support to FreeRTOS+TCP.
I think that this is the home page of lwIP.
If we have a solid demo for my device, I can also use it. What do you think?
I have to tell, my devices won’t suffer from a heavy network traffic.
They will usually talk to a TCP Server once a while only for some particular
command exchange between them.
I think that all IP-stacks can handle high-volume traffic as well.
Even furthermore, what if I still stick to uIP stack as it works
out of the box with my device, what would be the consequences of it?
Limited number of html pages? Less complex, very simple html pages?
slow loading pages, unresponsive pages?
That is your decision to take.
I recommend using FreeRTOS+TCP, because it integrates perfectly with FreeRTOS, and because it’s API’s are standard BSD style. It shouldn’t be too difficult to start up with +TCP.
Sorry to ask many questions. I am still trying to find my way,
a kickstart before getting my hands dirty.