From 46cd3a915bbe0b669531fe595d58e3107687ecd0 Mon Sep 17 00:00:00 2001 From: lchristina26 Date: Tue, 29 Sep 2015 12:49:24 -0600 Subject: [PATCH 1/4] VxWorks README --- IDE/WORKBENCH/README.md | 67 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) create mode 100644 IDE/WORKBENCH/README.md diff --git a/IDE/WORKBENCH/README.md b/IDE/WORKBENCH/README.md new file mode 100644 index 000000000..066e2f3e6 --- /dev/null +++ b/IDE/WORKBENCH/README.md @@ -0,0 +1,67 @@ +## Wind River Workbench using VxWorks with wolfSSL +###SETUP: +####Steps (There is many ways to set this up, this is one example) +1. Open WorkBench and go to File > Import > Existing Projects Into Workspace +2. Make sure the correct path to wolfSSL header files(wolfssl/wolfssl) is +selected by right clicking the project and going to Properties > Build +Properties > Paths. If you need to change this to a different path, do so now. +3. Right click on the project and go to Import > Filesystem. Choose your path +to the wolfSSL library here. Uncheck everything except the src and wolfcrypt +directories. Only keep wolfcrypt/test/test.h, not test.c. Also uncheck test +and benchmark directories and aes\_asm.asm and aes\_asm.s files from wolfcrypt/src. +4. In wolfSSL/test.h, make sure certs are in the proper directory, or move. +5. The wolfcrypt source files, namely misc.c, may need to be moved directly under +a wolfcrypt folder within the project. It will be \/wolfcrypt/src/misc.c. +Alnternatively, add wolfssl to the include path, #include +\. +6. Make sure TFM\_X86 is undefined. +####Necessary Files +You will need the following files to replicate this build: +* vxsim\_linux\_1\_0\_2\_2 (directory) +* Includes + * compilers/gnu-4.8.1.5/include/c++/4.8 + * compilers/gnu-4.8.1.5/include/c++/4.8/i586-wrs-vxworks + * compilers/gnu-4.8.1.5/lib/gcc/i586-wrs-vxworks/4.8.1/include + * compilers/gnu-4.8.1.5/lib/gcc/i586-wrs-vxworks/4.8.1/include-fixed + * vsb\_vxsim\_linux/share/h + * vsb\_vxsim\_linux/krnl/h/system + * vsb\_vxsim\_linux/krnl/h/public + * vsb\_vxsim\_linux/krnl/configlette + * vsb\_vxsim\_linux/h +* usrAppInit.c (should be created when you create a new VxWorks image) + * Include this at the top: + #include + #include + #include /* name change portability layer */ + #include + extern int benchmark_test(void* args); + extern THREAD\_RETURN WOLFSSL\_THREAD client\_test(void* args); + extern THREAD\_RETURN WOLFSSL\_THREAD server\_test(void* args); + * Inside main function UsrAppInit (void): + func\_args args = { 0 }; + tcp\_ready ready; + InitTcpReady(&ready); + args.signal = &ready; + benchmark\_test(NULL); + wolfcrypt\_test(NULL); + /* client\_test(NULL); */ + /*server\_test(&args);*/ +* usrRtpAppInit.c (should be created when you create a new VxWorks image) + Leave unchanged +* This project was tested with a pre-built image in the VxWorks distribution +called vsb\_vxsim\_linux. $(VSB\_DIR) line in the .wpj file may need to be +changed according to the VxWorks package being used. + +###VXWORKS SIMULATOR: +In "Open Connection Details" under VxWorks Simulator which is in the connections +dropdown. Choose IDE/WORKBENCH/wolfssl-vxworks-image/default/vxWorks as the +kernel image after building the project. Select simnetd from the dropdown and +enter 192.168.200.1 as the IP address. + +To connect to a server running on the VxWorks Simulator, enter these commands +into the host terminal (for Ubuntu 14.04): + sudo openvpn --mktun --dev tap0 +In Wind River directory: + vxworks-7/host/x86-linux2/bin/vxsimnetd +This will start the vxsimnetd application. Leave it open. The IP address to +connect to the server is the same as above. From 389bbc94ebb433edd8f7c67c68860914b2cccc8b Mon Sep 17 00:00:00 2001 From: Leah Date: Tue, 29 Sep 2015 12:51:03 -0600 Subject: [PATCH 2/4] Update README.md --- IDE/WORKBENCH/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/IDE/WORKBENCH/README.md b/IDE/WORKBENCH/README.md index 066e2f3e6..7e7f3e54c 100644 --- a/IDE/WORKBENCH/README.md +++ b/IDE/WORKBENCH/README.md @@ -1,6 +1,6 @@ ## Wind River Workbench using VxWorks with wolfSSL ###SETUP: -####Steps (There is many ways to set this up, this is one example) +####Steps (There are many ways to set this up, this is one example) 1. Open WorkBench and go to File > Import > Existing Projects Into Workspace 2. Make sure the correct path to wolfSSL header files(wolfssl/wolfssl) is selected by right clicking the project and going to Properties > Build @@ -15,6 +15,7 @@ a wolfcrypt folder within the project. It will be \/wolfcryp Alnternatively, add wolfssl to the include path, #include \. 6. Make sure TFM\_X86 is undefined. + ####Necessary Files You will need the following files to replicate this build: * vxsim\_linux\_1\_0\_2\_2 (directory) From 914ed31ff2c7553e3e665a419ab355882deab0af Mon Sep 17 00:00:00 2001 From: Leah Date: Tue, 29 Sep 2015 12:53:10 -0600 Subject: [PATCH 3/4] Update README.md --- IDE/WORKBENCH/README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/IDE/WORKBENCH/README.md b/IDE/WORKBENCH/README.md index 7e7f3e54c..a84731677 100644 --- a/IDE/WORKBENCH/README.md +++ b/IDE/WORKBENCH/README.md @@ -50,14 +50,12 @@ You will need the following files to replicate this build: * usrRtpAppInit.c (should be created when you create a new VxWorks image) Leave unchanged * This project was tested with a pre-built image in the VxWorks distribution -called vsb\_vxsim\_linux. $(VSB\_DIR) line in the .wpj file may need to be +called vsb\_vxsim\_linux. \ \$(VSB\_DIR) line in the .wpj file may need to be changed according to the VxWorks package being used. ###VXWORKS SIMULATOR: In "Open Connection Details" under VxWorks Simulator which is in the connections -dropdown. Choose IDE/WORKBENCH/wolfssl-vxworks-image/default/vxWorks as the -kernel image after building the project. Select simnetd from the dropdown and -enter 192.168.200.1 as the IP address. +dropdown. After the project has been build, choose the corresponding kernel image, typically called project/default/VxWorks. Select simnetd from the dropdown and enter 192.168.200.1 as the IP address. To connect to a server running on the VxWorks Simulator, enter these commands into the host terminal (for Ubuntu 14.04): From 350fe922b942aac473f66c8d2d44f0975d4d7a73 Mon Sep 17 00:00:00 2001 From: Leah Date: Tue, 29 Sep 2015 12:53:43 -0600 Subject: [PATCH 4/4] Update README.md --- IDE/WORKBENCH/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IDE/WORKBENCH/README.md b/IDE/WORKBENCH/README.md index a84731677..486b90b04 100644 --- a/IDE/WORKBENCH/README.md +++ b/IDE/WORKBENCH/README.md @@ -50,7 +50,7 @@ You will need the following files to replicate this build: * usrRtpAppInit.c (should be created when you create a new VxWorks image) Leave unchanged * This project was tested with a pre-built image in the VxWorks distribution -called vsb\_vxsim\_linux. \ \$(VSB\_DIR) line in the .wpj file may need to be +called vsb\_vxsim\_linux. \ $(VSB\_DIR) line in the .wpj file may need to be changed according to the VxWorks package being used. ###VXWORKS SIMULATOR: