Changes to TestSecurity README for clarification

diff --git a/apps/tests/cc2420/TestSecurity/README.txt b/apps/tests/cc2420/TestSecurity/README.txt
index fedc9c1ab45ae77d467019f69ea26eaee049f0ce..8c3700b65b53b0692b544136d384856982a3fb26 100644 (file)
--- a/apps/tests/cc2420/TestSecurity/README.txt
+++ b/apps/tests/cc2420/TestSecurity/README.txt
@@ -7,50 +7,41 @@ Jong Hyun Lim <ljh@cs.jhu.edu>
 
 Description:
 
-SecAMSend provides an interface to send Active Message based packets
-while using the CC2420 in-line security options.
-
-Instructions:
-
-All three in-line security options are implemented. The user can
-enable each mode by selecting one of the three commands, setCtr() to
-enable counter mode encryption, setCbcMac() to enable CBC-MAC
-authentication, and setCcm() to enable both functions (CCM) to the
-packet.
-
-The first parameter of all options lets the user select which of the
-two keys it will be using for security.
-
-The second parameter, sets the number of payload bytes to skip for
-encryption, number of bytes that will be skipped for authentication or
-the number of bytes that will be authenticated but not encrypted. By
-default when CCM is used the authentication starts at the byte after
-the length byte. Setting this second parameter to 0 will encrypt
-and/or sign all the payload, whereas, when this value is set to the
-length of the payload no bytes will be encrypted and/or signed.
-
-The third parameter for CBC-MAC and CCM are used to specify the number
-of bytes in the authentication field. The user can select an even
-number between 4 and 16 for this parameter.
-
-After specifying the three options the user can call a normal AMSend
-procedure to transmit secured packets.
-
-Before this process please note that the setKey() command should be
-used to specify the key the user desires to use for both the
-transmitter and the receiver.
-
-Please note that in the Makefile the flag CC2420_HW_SECURITY MUST be
-added for the security features to be active.
-
-Two application programs are included with security options
-enabled. The first application, RadioCountToLeds1, is a modification
-of RadioCountToLeds in the TinyOS 2.x repository. It dedicates one
-node (TOS_NODE_ID 1) to be the transmitting node and other nodes to
-receive its broadcast packets. Node 1 can use any of the three options
-enabled. The second application is the BaseStation application with
-the security extentions. Modifications were made to the Makefile by
-adding CFLAGS += -DCC2420_HW_SECURITY and a longer TOSH_DATA_LENGTH.
+Test the CC2420 hardware security support
+
+
+Applications:
+
+1. RadioCountToLeds1/ 
+
+This application is a modification to the RadioCountToLeds/
+application with CC2420 security features added to outgoing
+packets. The packets are decrypted at the receiver node. 
+
+> INSTALL
+
+Compile one node with ID 1 as the transmitter and other nodes with any
+node IDs to receive the decrypted packets
+
+>EXPECTATIONS
+
+LEDs on the receiver nodes will blink their LEDs sequentially like the
+original RadioCountToLeds/ application.
+
+
+2. Basestation/
+
+The BaseStation application with the security extensions
+
+> INSTALL
+
+Follow instructions on apps/BaseStation/README.txt
+
+> EXPECTATIONS
+
+Identical to the expectations in  apps/BaseStation/README.txt
+
+
 
 Known bugs/limitations: