Page Comparison

The code and documentation of This section discusses the modules available for μC/FTPc, and how they all fit together. A Windows®-based development platform is assumed. The directories and files make references to typical Windows-type directory structures. However, since μC/FTPc is available in source form, it can also be used with any ANSI-C compatible compiler/linker and Operating System.

Below is a summary of all directories and files involved in the µC/FTPc module are organized in a directory structure according to “AN-2002, µC/OS-II Directory Structure”. Specifically, the files may be found in the following directories:

\Micrium\Software\uC-FTPc

This is the main directory for µC/FTPc.. The ‘<-Cfg’ on the far right indicates that these files are typically copied into the application (i.e., project) directory and edited based on project requirements.

\Micrium
	\Software
		\uC-FTPc
			\Cfg
				\Template
					ftp-c_cfg.c           <-Cfg
					ftp-c_cfg.h           <-Cfg
			\Source
				ftp-c.c
				ftp-c.h
                ftp-c_type.h

\Micrium\Software\uC-FTPc\Doc

This is the main directory contains all for µC/FTPc documentation files, including this user’s manual.

\Micrium\Software\uC-FTPc\Cfg\Template

This directory contains a the template files of µC/FTPc configuration.

\Micrium\Software\uC-FTPc\Source

This directory contains the µC/FTPc source code. This protocol is implemented in two OS independent files:

ftp-c.c
ftp-c.h
ftp-c_type.h

Note that the ‘-c’ after ‘ftp’ stands for client and thus contains ‘client’ side code.

Required modules

µC/FTPc requires the µC/CPU, µC/LIB, µC/Common and µC/TCP-IP modules. If the network security manager is to be used, a security layer module (i.e Mocana’s NanoSSL) is required. Please refer to the µC/FTPc release notes document for required version information.