New release

Infineon · Apr 26, 2019 · 9d3f575 · 9d3f575
1 parent 446e459
commit 9d3f575
Show file tree

Hide file tree

Showing 9 changed files with 48 additions and 60 deletions.
diff --git a/documents/License.pdf b/documents/License.pdf
diff --git a/...ments/OPTIGA_Trust_M1_Datasheet_v1.50.pdf → ...ments/OPTIGA_Trust_M1_Datasheet_v1.60.pdf b/...ments/OPTIGA_Trust_M1_Datasheet_v1.50.pdf → ...ments/OPTIGA_Trust_M1_Datasheet_v1.60.pdf
diff --git a/documents/OPTIGA_Trust_M1_Keys_And_Certificates_v1.2.pdf b/documents/OPTIGA_Trust_M1_Keys_And_Certificates_v1.2.pdf
diff --git a/documents/OPTIGA_Trust_M1_Keys_And_Certificates_v1.30.pdf b/documents/OPTIGA_Trust_M1_Keys_And_Certificates_v1.30.pdf
diff --git a/documents/OPTIGA_Trust_M1_Release_Notes_v1.00.pdf b/documents/OPTIGA_Trust_M1_Release_Notes_v1.00.pdf
diff --git a/documents/OPTIGA_Trust_M1_Release_Notes_v1.01.pdf b/documents/OPTIGA_Trust_M1_Release_Notes_v1.01.pdf
diff --git a/...st_M1_Solution_Reference_Manual_v1.00.pdf → ...st_M1_Solution_Reference_Manual_v1.01.pdf b/...st_M1_Solution_Reference_Manual_v1.00.pdf → ...st_M1_Solution_Reference_Manual_v1.01.pdf
diff --git a/examples/tools/protected_update_data_set/README.md b/examples/tools/protected_update_data_set/README.md
diff --git a/examples/tools/protected_update_data_set/readme.txt b/examples/tools/protected_update_data_set/readme.txt
@@ -0,0 +1,48 @@
+1. Usage
+Start the "protected_update_data_generator.exe" with following options, in order to generate the data set for protected update data set.
+	payload_version=%%d		<default: 0>
+    trust_anchor_oid=%%s	<default: E0E8>
+    target_oid=%%s			<default: E0E2>						
+    offset=%%d				<default: 0>								
+	write_type=%%d 			<default: 1>			
+								<options : Write (1), EraseAndWrite (2)>
+    sign_algo=%%s 			<default: ES_256>							
+								<options : ES_256 , RSA-SSA-PKCS1-V1_5-SHA-256>
+    priv_key=%%s 			<default: NULL>		
+								<note : Provide key file(pem format). Corresponding certificate containing public key should be written to trust_anchor>		
+    payload=%%s 			<default: NULL>							
+								<note : Provide file with path with readable content>
+
+Example :											
+
+protected_update_data_generator.exe payload_version=3 trust_anchor=E0E8 target=E0E1 offset=01 write_type=1 sign_algo=RSA_SSA_PKCS1_V1_5_SHA_256 priv_key=<pem private key> payload=<text file with readable data>
+
+	a. Generate a manifest data with payload version 3, trust anchor 0xE0E3. The manifest is signed using "priv_key" and RSA_SSA_PKCS1_V1_5_SHA_256 is the signing algorithm
+	b. Fragments of data is generated from text file provided in option "payload"
+	b. The generated fragments is written at target OID 0xE0E1 from offset 1
+
+2. Sample :
+	A sample script demonstrating the usage of the tool is available in ..\samples
+
+3. Limitations
+	a. Only SHA-256 digest algorithm is supported for hash calculation
+	b. Manifest version number is 1	
+
+4. Environment
+	a. The availabel executable is built using microsoft visual studio 2010 in windows 10 (64 bit)
+	b. mbedTLS 2.7.0 is used for crypto operation.
+	c. The following MACRO must be disabled/ enabled when using mbedTLS for this tool.
+		i. Enable :
+			MBEDTLS_FS_IO
+			MBEDTLS_PEM_PARSE_C
+			MBEDTLS_BASE64_C
+			MBEDTLS_ECDSA_DETERMINISTIC
+			MBEDTLS_HMAC_DRBG_C
+			MBEDTLS_ECDSA_DETERMINISTIC_DEBUG
+			MBEDTLS_RSA_C
+			MBEDTLS_PKCS1_V15
+			MBEDTLS_PK_RSA_ALT_SUPPORT
+			MBEDTLS_TIMING_C
+
+		ii.Disable
+			MBEDTLS_NO_PLATFORM_ENTROPY in mbedTLS_config.h