[Tinyos-beta-commits] CVS: tinyos-1.x/beta/Deluge README.txt, 1.24, 1.25

[Jonathan Hui]

Update of /cvsroot/tinyos/tinyos-1.x/beta/Deluge
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11602

Modified Files:
	README.txt 
Log Message:
No longer support automatic cloning of Golden Image into external
flash. There are many complications with doing so since compile-time
information is hard to get at. Removing Golden Image cloning code
saves over 1K of program space. The Deluge java app is used to inject
a program image into the Golden Image slot.



Index: README.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-1.x/beta/Deluge/README.txt,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** README.txt	9 Jun 2005 22:20:35 -0000	1.24
--- README.txt	21 Jun 2005 23:34:29 -0000	1.25
***************
*** 12,58 ****
  - New features:
    - Verify image before programming: TOSBoot first verifies the CRCs
!   in the image before programming to help ensure the program is valid.
    - Check system voltage before programming: Make sure the system
!   voltage is above the required threshold to ensure that bits are
!   written correctly.
    - Rollback to Golden Image on failure: TOSBoot will automatically
!   attempt to load the Golden Image if a programming attempt has
!   failed, bringing the node into a network programmable state.
    - Hardware write protect: Support for hardware write protection to
!   prevent application code from modifying the Golden Image.
    - Verbose information: Image metadata include program name, compile
!   time, hostname that compiled the code, and user that compiled the
!   code.
    - Protected data structures: Metadata data-structures include CRCs
!   generated by the host PC to limit propagation of corrupt
!   data-structures.
    - Auto-detection of TOSBase: The Deluge java app operates exactly
!   the same whether a Deluge or TOSBase node is connect. The '-t'
!   option is no longer required at the command line.
    - Auto-resume incomplete images: Auto-resume of incomplete images,
!   using program name, unix time, and user hash to identify identical
!   images.
    - Auto-detect identical images: Auto-detection of identical images
!   so that images are not accidentally downloaded more than once by the
!   user.
    - Operator error protection: Metadata information clearly displayed
!   and now requires user confirmation to continue execution.
    - Reset images: Reset Deluge images before shifting your nodes from
!   network to network and prevent unintentional reprogramming of nodes.
    - nesC TOSBoot: TOSBoot bootloader now written in nesC.
    - TinyOS 2.x storage abstraction: Support for TinyOS 2.x hardware
!   independent storage abstraction.
    - Protocol version number: Version number information included in
!   Deluge packets to prevent nodes with different versions of Deluge
!   from conflicts.
    - DMA transfer support: CRCs are no longer inlined with program
!   data, thus allowing for DMA transfers from external flash to program
!   flash.
!   -Less code size: All improvements implemented in less code size than
!   Deluge 1.0.
  
  - Major user differences:
!   - Golden image is now slot 0. While it cannot be written to, the user
!     can retrieve Ident.h information about the golden image.
    - Versions numbers are no longer shown explicitly to the user.
    - When specifying an image for download, the user specifies the 
--- 12,59 ----
  - New features:
    - Verify image before programming: TOSBoot first verifies the CRCs
!     in the image before programming to help ensure the program is valid.
    - Check system voltage before programming: Make sure the system
!     voltage is above the required threshold to ensure that bits are
!     written correctly.
    - Rollback to Golden Image on failure: TOSBoot will automatically
!     attempt to load the Golden Image if a programming attempt has
!     failed, bringing the node into a network programmable state.
    - Hardware write protect: Support for hardware write protection to
!     prevent application code from modifying the Golden Image.
    - Verbose information: Image metadata include program name, compile
!     time, hostname that compiled the code, and user that compiled the
!     code.
    - Protected data structures: Metadata data-structures include CRCs
!     generated by the host PC to limit propagation of corrupt
!     data-structures.
    - Auto-detection of TOSBase: The Deluge java app operates exactly
!     the same whether a Deluge or TOSBase node is connect. The '-t'
!     option is no longer required at the command line.
    - Auto-resume incomplete images: Auto-resume of incomplete images,
!     using program name, unix time, and user hash to identify identical
!     images.
    - Auto-detect identical images: Auto-detection of identical images
!     so that images are not accidentally downloaded more than once by the
!     user.
    - Operator error protection: Metadata information clearly displayed
!     and now requires user confirmation to continue execution.
    - Reset images: Reset Deluge images before shifting your nodes from
!     network to network and prevent unintentional reprogramming of nodes.
    - nesC TOSBoot: TOSBoot bootloader now written in nesC.
    - TinyOS 2.x storage abstraction: Support for TinyOS 2.x hardware
!     independent storage abstraction.
    - Protocol version number: Version number information included in
!     Deluge packets to prevent nodes with different versions of Deluge
!     from conflicts.
    - DMA transfer support: CRCs are no longer inlined with program
!     data, thus allowing for DMA transfers from external flash to program
!     flash.
!   - Less code size: All improvements implemented in less code size than
!     Deluge 1.0.
  
  - Major user differences:
!   - Golden image is now slot 0. The Golden Image is not automatically
!     cloned. The Golden Image is no longer automatically cloned into
!     external flash. Instead, use the java app to install your Golden Image.
    - Versions numbers are no longer shown explicitly to the user.
    - When specifying an image for download, the user specifies the 
***************
*** 62,66 ****
  
  - To setup the Deluge tools, create the directory net/tinyos/deluge
! and copy all files in 'delugetools' into it.
  
  - Operation is very similar to Deluge v1.0.
--- 63,67 ----
  
  - To setup the Deluge tools, create the directory net/tinyos/deluge
!   and copy all files in 'delugetools' into it.
  
  - Operation is very similar to Deluge v1.0.
***************
*** 71,72 ****
--- 72,80 ----
    Reboot:
      $ java net.tinyos.deluge.Deluge -r -in=<imagenum>
+ 
+ - Deluge 2.0 is also integrated with the make system. The following
+   commands will inject and reboot your nodes:
+   Build and install:
+     $ make telosb deluge
+   Install without build:
+     $ make telosb redeluge