Eagle enet tftpd Example - Revision history

Support at 14:33, 20 July 2010

2010-07-20T14:33:29Z

← Older revision		Revision as of 14:33, 20 July 2010
Line 55:		Line 55:
	The original TFTP specification allowed for file sizes up to 32MB but has been extended by RFC 2347 which allows for file sizes up to 4GB.		The original TFTP specification allowed for file sizes up to 32MB but has been extended by RFC 2347 which allows for file sizes up to 4GB.
	==Filesystems==		==Filesystems==
-	The enet_tftpd example implements a non-standard ROMFS filesystem for writing to flash memory which only supports the storage of a single file. ~~Anytime~~ data is written to the ROMFS filesystem, any previous data will be overwritten. This filesystem must also be share the 256KB of available flash memory with the bootloader and application.	+	The enet_tftpd example implements a non-standard ROMFS filesystem for writing to flash memory which only supports the storage of a single file. Any time data is written to the ROMFS filesystem, any previous data will be overwritten. This filesystem must also be share the 256KB of available flash memory with the bootloader and application.

	The FatFs filesystem used on the microSD card only supports short (8.3) file names and file sizes up to 4GB.		The FatFs filesystem used on the microSD card only supports short (8.3) file names and file sizes up to 4GB.
	=Summary=		=Summary=
	The TFTP protocol is small and simple enough for embedded applications and allows developers to add functionality for basic remote file accessibility. The enet_tftpd example demonstrates how data logs can be downloaded from the board, how application controlling scripts can be uploaded, and even how remote firmware updates are possible. Developers can choose to use the FatFs filesystem on a microSD card for relatively robust file storage or choose to use internal flash memory for basic operations. TFTP clients are available for any system and are easy for users to find and use. Since the TFTP protocol lacks any security provision, care must be taken so that boards are deployed safely to prevent unauthorized access. For any questions regarding this application, please contact Micromint support at [mailto:support@micromint.com support@micromint.com].		The TFTP protocol is small and simple enough for embedded applications and allows developers to add functionality for basic remote file accessibility. The enet_tftpd example demonstrates how data logs can be downloaded from the board, how application controlling scripts can be uploaded, and even how remote firmware updates are possible. Developers can choose to use the FatFs filesystem on a microSD card for relatively robust file storage or choose to use internal flash memory for basic operations. TFTP clients are available for any system and are easy for users to find and use. Since the TFTP protocol lacks any security provision, care must be taken so that boards are deployed safely to prevent unauthorized access. For any questions regarding this application, please contact Micromint support at [mailto:support@micromint.com support@micromint.com].

Support at 14:32, 20 July 2010

2010-07-20T14:32:27Z

← Older revision		Revision as of 14:32, 20 July 2010
Line 12:		Line 12:
	New and updated scripts which control your embedded application can be uploaded remotely from a network machine. Again, this can be done without physically accessing the board and without interruption.		New and updated scripts which control your embedded application can be uploaded remotely from a network machine. Again, this can be done without physically accessing the board and without interruption.
	==Firmware updates==		==Firmware updates==
-	~~The latest firmware updates~~ can be ~~pushed~~ to the ~~Eagle remotely via TFTP~~.	+	Applications can be developed so that uploaded data will be used to reprogram the firmware in flash memory. A soft reset can then allow the board to boot with the new firmware in place.
	=enet_tftpd example=		=enet_tftpd example=
	==microSD filesystem==		==microSD filesystem==

Support at 14:21, 20 July 2010

2010-07-20T14:21:54Z

← Older revision		Revision as of 14:21, 20 July 2010
Line 8:		Line 8:
	=Common uses for TFTP=		=Common uses for TFTP=
	==Data downloads==		==Data downloads==
-	Data collected and stored on the Eagle can be easily accessed and downloaded remotely via TFTP.	+	Data collected and stored on the Eagle can be easily accessed and downloaded remotely via TFTP. The board does not have to be physically accessed or taken offline.
	==Script uploads==		==Script uploads==
-	New and updated scripts which control your embedded application can be uploaded remotely from a network machine.	+	New and updated scripts which control your embedded application can be uploaded remotely from a network machine. Again, this can be done without physically accessing the board and without interruption.
	==Firmware updates==		==Firmware updates==
	The latest firmware updates can be pushed to the Eagle remotely via TFTP.		The latest firmware updates can be pushed to the Eagle remotely via TFTP.
Line 55:		Line 55:
	The original TFTP specification allowed for file sizes up to 32MB but has been extended by RFC 2347 which allows for file sizes up to 4GB.		The original TFTP specification allowed for file sizes up to 32MB but has been extended by RFC 2347 which allows for file sizes up to 4GB.
	==Filesystems==		==Filesystems==
-	The enet_tftpd example implements a non-standard ROMFS filesystem for writing ~~and~~ only supports the storage of a single file. Anytime data is written to the ROMFS filesystem, any previous data will be overwritten.	+	The enet_tftpd example implements a non-standard ROMFS filesystem for writing to flash memory which only supports the storage of a single file. Anytime data is written to the ROMFS filesystem, any previous data will be overwritten. This filesystem must also be share the 256KB of available flash memory with the bootloader and application.

-	The FatFs filesystem only supports short (8.3) ~~filenames~~.	+	The FatFs filesystem used on the microSD card only supports short (8.3) file names and file sizes up to 4GB.
	=Summary=		=Summary=
		+	The TFTP protocol is small and simple enough for embedded applications and allows developers to add functionality for basic remote file accessibility. The enet_tftpd example demonstrates how data logs can be downloaded from the board, how application controlling scripts can be uploaded, and even how remote firmware updates are possible. Developers can choose to use the FatFs filesystem on a microSD card for relatively robust file storage or choose to use internal flash memory for basic operations. TFTP clients are available for any system and are easy for users to find and use. Since the TFTP protocol lacks any security provision, care must be taken so that boards are deployed safely to prevent unauthorized access. For any questions regarding this application, please contact Micromint support at [mailto:support@micromint.com support@micromint.com].

Support at 13:35, 20 July 2010

2010-07-20T13:35:12Z

← Older revision		Revision as of 13:35, 20 July 2010
Line 17:		Line 17:
	This application uses the [http://elm-chan.org/fsw/ff/00index_e.html FatFs] FAT file system for embedded systems. This allows the data on the microSD to be read with other FAT compatible systems (including Windows, Linux, Mac OSX). The FatFs file system limits file sizes to 4GB, volume size to 2TB, cluster size to 64KB, and sector size to 4KB. The FAT sub-type is also required to be either FAT12, FAT16, or FAT32. A virtually unlimited number of new files can be uploaded via TFTP, dependent on memory space. Uploading an existing file will overwrite the old file.		This application uses the [http://elm-chan.org/fsw/ff/00index_e.html FatFs] FAT file system for embedded systems. This allows the data on the microSD to be read with other FAT compatible systems (including Windows, Linux, Mac OSX). The FatFs file system limits file sizes to 4GB, volume size to 2TB, cluster size to 64KB, and sector size to 4KB. The FAT sub-type is also required to be either FAT12, FAT16, or FAT32. A virtually unlimited number of new files can be uploaded via TFTP, dependent on memory space. Uploading an existing file will overwrite the old file.
	==Internal filesystem==		==Internal filesystem==
-	~~This application has limited support~~ for ~~data storage on its internal flash memory~~. ~~Storage capacity is severely limited~~ as ~~256KB~~ of ~~memory must be shared with~~ the ~~both~~ the ~~bootloader and application~~. ~~Data can either~~ be ~~stored at compile time or uploaded at run time~~.	+	The enet_tftpd example uses a standard ROMFS filesystem for supporting read operations from files included at compile time. These files are included as lmi-fsdata.h and occupy a part of the object code. Use the makefs.bat utility in the enet_tftpd directory to convert the files in the ''enet_tftpd\fs\'' directory to the lmi-fsdata.h header file. Remember, these files will be read only and must share the 256KB flash memory with the application and bootloader.

-	~~Files stored at compile time are included as lmi~~-~~fsdata.h and are a part of object code~~. ~~Use the makefs.bat utility~~ to ~~translate~~ the ~~files in ''\eagle\enet_tftpd\fs\'' to a single header file~~. ~~These files are read only~~.	+	For write operations to internal flash memory, enet_tftpd uses a non-standard ROMFS filesystem. Storage capacity is limited to the remaining flash memory that is not occupied by the bootloader, application, and existing ROMFS. The amount of memory used for ROMFS writing must be specified at compile time and has a default of 16KB.

-	~~Uploading of data to internal memory at run time is limited to a single file~~. Additionally, this file must fit within an allocated space determined at compile time. enet_tftpd uses a default of 16KB which can be made larger or smaller depending on the size of your application. Note: Uploading any new data to the internal file system will erase old data!	+	See filesystem limitations for more details.
	==Compile options==		==Compile options==
	===Firmware update mode===		===Firmware update mode===
Line 42:		Line 42:
	==GUI TFTP==		==GUI TFTP==
	===Tftpd32===		===Tftpd32===
-	Tftpd32 is a small utility that offers DHCP, TFTP, DNS, SNTP and Syslog servers as well a TFTP client. It's compatible with all modern Window's versions and does not require an installation.	+	[http://tftpd32.jounin.net/tftpd32.html Tftpd32] is a small utility that offers DHCP, TFTP, DNS, SNTP and Syslog servers as well a TFTP client. It's compatible with all modern Window's versions and does not require an installation.

	To begin a new TFTP session, execute Tftpd32.exe and click the ''Tftp Client'' tab. Enter the hostname and port of the TFTP server that you wish to connect to. For GET requests, specify the source file in the ''Remote File'' text box and the destination on your machine in the ''Local File'' text box. For PUT requests, specify the source file in ''Local File'' and the destination in ''Remote File''.		To begin a new TFTP session, execute Tftpd32.exe and click the ''Tftp Client'' tab. Enter the hostname and port of the TFTP server that you wish to connect to. For GET requests, specify the source file in the ''Remote File'' text box and the destination on your machine in the ''Local File'' text box. For PUT requests, specify the source file in ''Local File'' and the destination in ''Remote File''.
Line 49:		Line 49:
	==Security==		==Security==
	===No password===		===No password===
		+	TFTP has no provisions for access authorization. Anyone with network access to the application's TFTP port will have full read and write permissions. Thus, it is only recommended for use on private, local networks.
	===No firewall===		===No firewall===
		+	Because of the lack of security provisions, it is strongly recommended that the service should be placed behind a firewall to prevent outside network access.
	==File size==		==File size==
-	==~~Internal filesystem writing~~==	+	The original TFTP specification allowed for file sizes up to 32MB but has been extended by RFC 2347 which allows for file sizes up to 4GB.
		+	==Filesystems==
		+	The enet_tftpd example implements a non-standard ROMFS filesystem for writing and only supports the storage of a single file. Anytime data is written to the ROMFS filesystem, any previous data will be overwritten.
		+
		+	The FatFs filesystem only supports short (8.3) filenames.
	=Summary=		=Summary=

Support at 18:15, 15 July 2010

2010-07-15T18:15:36Z

← Older revision		Revision as of 18:15, 15 July 2010
Line 41:		Line 41:
	[[Image:LinuxCmdLine.png\|center\|alt=Linux Command Line\|frame\|]]		[[Image:LinuxCmdLine.png\|center\|alt=Linux Command Line\|frame\|]]
	==GUI TFTP==		==GUI TFTP==
		+	===Tftpd32===
		+	Tftpd32 is a small utility that offers DHCP, TFTP, DNS, SNTP and Syslog servers as well a TFTP client. It's compatible with all modern Window's versions and does not require an installation.
		+
		+	To begin a new TFTP session, execute Tftpd32.exe and click the ''Tftp Client'' tab. Enter the hostname and port of the TFTP server that you wish to connect to. For GET requests, specify the source file in the ''Remote File'' text box and the destination on your machine in the ''Local File'' text box. For PUT requests, specify the source file in ''Local File'' and the destination in ''Remote File''.
		+	[[Image:Tftp32.png\|center\|alt=Tftp32 GUI\|frame\|]]
	=TFTP Limitations=		=TFTP Limitations=
	==Security==		==Security==

Support at 17:52, 15 July 2010

2010-07-15T17:52:33Z

← Older revision		Revision as of 17:52, 15 July 2010
Line 8:		Line 8:
	=Common uses for TFTP=		=Common uses for TFTP=
	==Data downloads==		==Data downloads==
-	Data ~~files~~ stored on ~~network boards~~ can be easily accessed and downloaded ~~through~~ TFTP.	+	Data collected and stored on the Eagle can be easily accessed and downloaded remotely via TFTP.
	==Script uploads==		==Script uploads==
-	~~Applications can be controlled by new/~~updated scripts ~~that are~~ uploaded remotely.	+	New and updated scripts which control your embedded application can be uploaded remotely from a network machine.
	==Firmware updates==		==Firmware updates==
-	The latest firmware updates can be pushed to ~~boards through~~ TFTP.	+	The latest firmware updates can be pushed to the Eagle remotely via TFTP.
	=enet_tftpd example=		=enet_tftpd example=
	==microSD filesystem==		==microSD filesystem==
Line 19:		Line 19:
	This application has limited support for data storage on its internal flash memory. Storage capacity is severely limited as 256KB of memory must be shared with the both the bootloader and application. Data can either be stored at compile time or uploaded at run time.		This application has limited support for data storage on its internal flash memory. Storage capacity is severely limited as 256KB of memory must be shared with the both the bootloader and application. Data can either be stored at compile time or uploaded at run time.

-	Files stored at compile time are included as lmi-fsdata.h and are a part of object code. Use the makefs.bat utility to translate the files in enet_tftpd\fs\ to a single header file. These files are read only.	+	Files stored at compile time are included as lmi-fsdata.h and are a part of object code. Use the makefs.bat utility to translate the files in ''\eagle\enet_tftpd\fs\'' to a single header file. These files are read only.

	Uploading of data to internal memory at run time is limited to a single file. Additionally, this file must fit within an allocated space determined at compile time. enet_tftpd uses a default of 16KB which can be made larger or smaller depending on the size of your application. Note: Uploading any new data to the internal file system will erase old data!		Uploading of data to internal memory at run time is limited to a single file. Additionally, this file must fit within an allocated space determined at compile time. enet_tftpd uses a default of 16KB which can be made larger or smaller depending on the size of your application. Note: Uploading any new data to the internal file system will erase old data!
	==Compile options==		==Compile options==
	===Firmware update mode===		===Firmware update mode===
-	Firmware update mode is set by defining "BL_UPDATE" as a compiler pre-processor option. ~~This will flash~~ any ~~uploaded~~ file to memory at address 0x00 and ~~reset the~~ board. This data can not be downloaded later by a GET request as no file system information is recorded.	+	Firmware update mode is set by defining <code>BL_UPDATE</code> as a compiler pre-processor option. With this option, any file uploaded to the board will be flashed to memory address 0x00 and board will be reset. This data can not be downloaded later by a GET request as no file system information is recorded.
	===TFTP port===		===TFTP port===
		+	The TFTP port can be specified by defining <code>TFTP_PORT</code> as a compiler pre-processor option. For example, to set the port as 6969, use <code>TFTP_PORT=6969</code>. If no port is specified, enet_tftpd will use the default port, 69.
	=TFTP clients=		=TFTP clients=
	==Command line TFTP==		==Command line TFTP==
	===Windows===		===Windows===
		+	A TFTP command line client is included with Windows 2000, XP, Vista, and 7 licenses. You will need to make sure this utility is installed by checking the installed components in the Control Panel.
		+
		+	To learn about the TFTP client usage, enter <code>tftp</code> at a command prompt. To download a file from the board in ASCII mode, enter <code>tftp ''hostname'' GET ''filename''</code>. Alternatively, to upload an ASCII file to the board, enter <code>tftp ''hostname'' PUT ''filename''</code>. To specify a binary mode transfer, specify the <code>-i</code> option before the hostname, i.e. <code> tftp -i ''hostname'' GET ''filename''</code>.
		+
		+	[[Image:WinCmdLine.png\|center\|alt=Windows Command Line\|frame\|]]
	===Linux===		===Linux===
		+	A TFTP command line client is included in most Linux distributions. If not, it can easily be installed by entering <code>sudo apt-get install tftp</code> at the terminal.
		+
		+	To learn about the TFTP client usage, enter <code>man tftp</code> at the terminal. To begin a new session, enter <code>tftp ''hostname''</code>. To download or upload a file, enter <code>GET ''filename''</code> or <code>PUT ''filename''</code> respectively. Entering the <code>tftp</code> command each time in Linux is unnecessary. To switch to binary mode, enter <code>mode binary</code> (ASCII mode is default). To end the TFTP session, enter <code>quit</code>.
		+	[[Image:LinuxCmdLine.png\|center\|alt=Linux Command Line\|frame\|]]
	==GUI TFTP==		==GUI TFTP==
	=TFTP Limitations=		=TFTP Limitations=

Support at 22:34, 13 July 2010

2010-07-13T22:34:49Z

← Older revision		Revision as of 22:34, 13 July 2010
Line 24:		Line 24:
	==Compile options==		==Compile options==
	===Firmware update mode===		===Firmware update mode===
-	Firmware update mode is set by defining "BL_UPDATE" as a compiler pre-processor option. This will flash ~~and~~ uploaded file to memory at address 0x00 and reset the board. This data can not be downloaded later by a GET request as no file system information is recorded.	+	Firmware update mode is set by defining "BL_UPDATE" as a compiler pre-processor option. This will flash any uploaded file to memory at address 0x00 and reset the board. This data can not be downloaded later by a GET request as no file system information is recorded.
	===TFTP port===		===TFTP port===
	=TFTP clients=		=TFTP clients=

Support at 22:34, 13 July 2010

2010-07-13T22:34:19Z

← Older revision		Revision as of 22:34, 13 July 2010
Line 5:		Line 5:
	=TFTP Overview=		=TFTP Overview=
	==Origins==		==Origins==
-	=Common uses for TFTP	+	TFTP (Trivial File Transfer Protocol) is a very simple file transfer protocol commonly implemented on top of UDP (User Datagram Protocol) using port number 69. Its purpose is to move files between machines on different networks and is designed to be small and easily implemented. It's only features the reading and writing of files and does not offer any other advanced features or security. TFTP currently supports two different modes, "netascii" (ASCII) and "octet" (binary) with a third "mail" mode being made obsolete in 1992 by [http://tools.ietf.org/html/rfc1350 RFC1350].
		+	=Common uses for TFTP=
	==Data downloads==		==Data downloads==
		+	Data files stored on network boards can be easily accessed and downloaded through TFTP.
	==Script uploads==		==Script uploads==
		+	Applications can be controlled by new/updated scripts that are uploaded remotely.
	==Firmware updates==		==Firmware updates==
		+	The latest firmware updates can be pushed to boards through TFTP.
	=enet_tftpd example=		=enet_tftpd example=
	==microSD filesystem==		==microSD filesystem==
		+	This application uses the [http://elm-chan.org/fsw/ff/00index_e.html FatFs] FAT file system for embedded systems. This allows the data on the microSD to be read with other FAT compatible systems (including Windows, Linux, Mac OSX). The FatFs file system limits file sizes to 4GB, volume size to 2TB, cluster size to 64KB, and sector size to 4KB. The FAT sub-type is also required to be either FAT12, FAT16, or FAT32. A virtually unlimited number of new files can be uploaded via TFTP, dependent on memory space. Uploading an existing file will overwrite the old file.
	==Internal filesystem==		==Internal filesystem==
		+	This application has limited support for data storage on its internal flash memory. Storage capacity is severely limited as 256KB of memory must be shared with the both the bootloader and application. Data can either be stored at compile time or uploaded at run time.
		+
		+	Files stored at compile time are included as lmi-fsdata.h and are a part of object code. Use the makefs.bat utility to translate the files in enet_tftpd\fs\ to a single header file. These files are read only.
		+
		+	Uploading of data to internal memory at run time is limited to a single file. Additionally, this file must fit within an allocated space determined at compile time. enet_tftpd uses a default of 16KB which can be made larger or smaller depending on the size of your application. Note: Uploading any new data to the internal file system will erase old data!
	==Compile options==		==Compile options==
	===Firmware update mode===		===Firmware update mode===
		+	Firmware update mode is set by defining "BL_UPDATE" as a compiler pre-processor option. This will flash and uploaded file to memory at address 0x00 and reset the board. This data can not be downloaded later by a GET request as no file system information is recorded.
	===TFTP port===		===TFTP port===
	=TFTP clients=		=TFTP clients=

Support: TOC

2010-07-13T20:11:17Z

TOC

← Older revision		Revision as of 20:11, 13 July 2010
Line 1:		Line 1:
	=Ethernet TFTPD Server (enet_tftpd)=		=Ethernet TFTPD Server (enet_tftpd)=
	==Compatibility [http://www.micromint.com/index.php/SBC/eagle-50.html Eagle 50E], [http://www.micromint.com/index.php/SBC/eagle-100.html 100]==		==Compatibility [http://www.micromint.com/index.php/SBC/eagle-50.html Eagle 50E], [http://www.micromint.com/index.php/SBC/eagle-100.html 100]==
		+
		+	__TOC__
		+	=TFTP Overview=
		+	==Origins==
		+	=Common uses for TFTP
		+	==Data downloads==
		+	==Script uploads==
		+	==Firmware updates==
		+	=enet_tftpd example=
		+	==microSD filesystem==
		+	==Internal filesystem==
		+	==Compile options==
		+	===Firmware update mode===
		+	===TFTP port===
		+	=TFTP clients=
		+	==Command line TFTP==
		+	===Windows===
		+	===Linux===
		+	==GUI TFTP==
		+	=TFTP Limitations=
		+	==Security==
		+	===No password===
		+	===No firewall===
		+	==File size==
		+	==Internal filesystem writing==
		+	=Summary=

Support: Created page with '=Ethernet TFTPD Server (enet_tftpd)= ==Compatibility [http://www.micromint.com/index.php/SBC/eagle-50.html Eagle 50E], [http://www.micromint.com/index.php/SBC/eagle-100.html 100]…'

2010-06-20T01:11:22Z

Created page with '=Ethernet TFTPD Server (enet_tftpd)= ==Compatibility [http://www.micromint.com/index.php/SBC/eagle-50.html Eagle 50E], [http://www.micromint.com/index.php/SBC/eagle-100.html 100]…'

New page

=Ethernet TFTPD Server (enet_tftpd)=
==Compatibility [http://www.micromint.com/index.php/SBC/eagle-50.html Eagle 50E], [http://www.micromint.com/index.php/SBC/eagle-100.html 100]==