You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: embedded/signature/README.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Signature Examples for Embedded Systems
2
2
3
-
This directory includes the following examples under the sub-directories.Each has a Makefile and source files to build and execute the example and a README to show how to build and Example output.
3
+
This directory includes the following examples. Each subdirectory has a Makefile, source files, and a README to show how to build the example, along with expected example output.
4
4
5
5
|Scheme|Directory|Description|
6
6
|---|---|---|
@@ -12,7 +12,8 @@ This directory includes the following examples under the sub-directories.Each ha
12
12
||ecc_vfy_only_nonblock|verify signature with non-blocking|
13
13
14
14
15
-
You can specify a target function of Simple example, Benchemark or Memory track program.It also has options for optimized code for MCU architectures such as Intel x86, ARM64 or a generic code by default, as well as Math library of Single Precision or TFM.
15
+
When building each example, you can specify arguments to control the build. Specify a target function to run either a simple example, benchmark, or memory tracking example. Specify an "arch" option to build optimized code for MCU architectures such as Intel x86, ARM64 or a generic code by default. And specify a "math" option to choose an underlying wolfCrypt math library to use, between Single Precision or TFM.
16
+
16
17
17
18
```
18
19
$ make <Function> math=<Mathlib> arch=<MCU>
@@ -30,7 +31,7 @@ $ make <Function> math=<Mathlib> arch=<MCU>
30
31
|math|Description|
31
32
|---|---|
32
33
|Default|Generic architecture by pure C language source code|
33
-
|sp| SP for generic or specified archtecture|
34
+
|sp| SP for generic or specified architecture|
34
35
|tfm|TFM for generic architecture|
35
36
## MCU Architectures
36
37
NOTE: No architecture specification is required when using TFM.
@@ -43,10 +44,10 @@ NOTE: No architecture specification is required when using TFM.
43
44
|x64|SP for x86 64bit|
44
45
45
46
46
-
The Makefile is self-contained without libwolfssl. Put your wolfSSL source filesin parallel with wolfssl-examples directory. It is defined by WOLFROOT in Makefile.It compiles only needed files for the target. OBJ and OBJ_xxx macro in Makefiledefine object files for the common and specific target.
47
-
48
-
Example programs are hard coded for a hash algorithm or signature scheme.Sha256 is for the hash by default. PKCS #1 v1.5 or ECDSA for the signature scheme.You can refer to the following API tables for modifying the examples for other algorithms or schemes.
47
+
Each Makefile is self-contained to statically link wolfCrypt source files (without using a shared libwolfssl.so). Put your wolfSSL source files in parallel with the wolfssl-examples directory. The location of the primary wolfSSL source directory is defined by WOLFROOT in each Makefile. Each build compiles only the needed files for the target. OBJ and OBJ_xxx macros in each Makefile define object files for the common and specific target.
49
48
49
+
Example programs are hard coded to use a specific hash algorithm or signature scheme. Sha256 is used for the hash by default. PKCS#1 v1.5 or ECDSA is used for the signature scheme. You can refer to the following API tables for modifying the examples for other algorithms or schemes.
0 commit comments