FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [December 2016 Threads]
Hi,
I'm woking with STM32L486RG MCU using IAR v7.4 IDE.
In my poject , I'm required to implement an FTP server on my SD card **using the **FreeRTOS+ library.
For the internet connection , I'm using the WINC1500 module of ATMEL.
When I started the integration of the FreeRTOS +, I found that there are files called "FreeRTOS_sockets.c" and "FreeRTOS_sockets.h" and I start to be a little bit confused whether these files use my** WINC1500 socket** or they use and create another socket type.
Currently in my project, I have an MQTT client implemented and it uses the WINC1500 socket. So, if I want to implement the FTP server , should I use the some socket of my WINC1500 module or let the FreeRTOS_sockets files use their own ?
Sorry , but I'm in urgent need for help because I'm getting lost and I don't really find enough information about this issue on the net.
Thanks in advance !
Hi again,
maybe the good question is : how to tie my winc1500 module and the freertos socket ?
kind and best regards,
Dhibi
I'm afraid I don't know anything about the WINC1500, but a quick look at
information on the Internet leads me to the conclusion that the device
has the TCP/IP stack on board, and provides access through a serial
interface - so I'm not sure it is intended for use with a source code
TCP/IP stack.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.