Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I want to be able to transfer large blocks of data to and from my host processor.
I was reading that the NETX FTP functionality needs a file system to work, but the posts are from 5 years ago.
If my host processor is connected to the WICED device (Murata Type1LD) with SPI, can I tell the WICED application that my "file system" is on the other side of the SPI? - I could write firmware on the host processor to behave like a virtual serial EEPROM.
Is this doable? or is there a better way to get blocks of data to and from my host? Should I not be using FTP? I have an AWS based server.
I currently have a cellular modem connected to my host via a UART, and that supports FTP, so I wanted to do something similar with my WiFi channel.
Thanks for the reply. Here is a diagram of our topology.
The files I want to transfer would be to and from the filesystem of the host processor. Currently we use FTP because our destination server has supports FTP without needing any custom implementation, and also because the cellular modems we use have the stack to support FTP. We transmit data to a customer server which has password protection.
If it was simple values, I could have used a protocol like MQTT, but with large blocks of file data, I am trying to understand what application protocols are available that maybe also take care of integrity checking during the transfer.
Is there a specific reason why standard FTP is not supported? - is it an obsolete protocol?