...
This section discusses the modules available for μC/TFTPs, 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/TFTPs 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/TFTPs module
...
\Micrium\Software\uC-TFTPs
...
. 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.
Code Block |
---|
\Micrium
\Software
\uC-TFTPs
\Cfg
\Template
tftp-s_cfg.h
\OS
\uCOS-II
tftp-s_os.c
\uCOS-III
tftp-s_os.c
\Source
tftp-s.c
tftp-s.h |
\Micrium\Software\uC-TFTPs\Doc
This is the main directory contains all for µC/TFTPs documentation files, including this user’s manual..
\Micrium\Software\uC-TFTPs\Cfg\Template
This directory contains a template of µC/TFTPs configuration.
\Micrium\Software\uC-TFTPs\Source
This directory contains the µC/TFTPs source code. This protocol is implemented in two OS and FS independent files:
tftp-s.c
tftp-s.h
Note that the ‘-s
’ after ‘tftp
’ stands for server and thus contains ‘server’ side code.
...