@dizgah,

Can you tell us a bit about your use case and project goals?

It would depend on the use-case. wolfSSL is transport level agnostic meaning if it can send and receive we can do a TLS handshake over that medium. If you are planning on using Wifi/Ethernet then yes you would want a TCP/IP stack (like LWIP). If however it would better fit your use-case to do a TLS connection of USB/Serial then you could just register custom I/O callbacks with wolfSSL that read/write over USB serial instead. Again the use-case matters.

We do provide an LPCExpresso example in our download wolfssl-4.0.0/IDE/LPCEXPRESSO/ The example was setup and tested on an LPC43S37 but you should be able to use and retarget for your LPC1768. That example only runs the wolfCrypt tests and benchmark but could be extended to a client/server example by referencing our examples in https://github.com/wolfSSL/wolfssl-exam … master/tls

Warm Regards,

K

@dizgah,

If you add the setting #define WOLFCRYPT_ONLY to the wolfssl-4.0.0/IDE/LPCEXPRESSO/lib_wolfssl/user_settings.h header that will turn off the SSL/TLS layer leaving you with just the wolfCrypt solution in that example. You can build and use the crypto library without the TLS library but the TLS library has a dependency on the crypto library and can not be built without the crypto.

Warm Regards,

K

Dear Kaleb,
As I said before I have no success in building example by MCUXPRESSO.
Also because project file includes all supported ISE configs and this confusing me, then I try to make a simple minimal project in MCUXPRESSO with just adding wolfCrypt sources.
I have Some question:

1- As I understand core crypto operations are written in assembly, then is at&t syntax correct choice for cross compiling for LPC1768 ?
2- If yes, why Assembler return "bad instruction

movq    %rcx, %r10

aes_asm.S as I said in my last post?
3- whats function of ksdk_port.c file in wolfcrypt\src\port\nxp files ?why crypto functions does not implemented in general wolfcrypt directory(I could not find any NXP specific function in this file)
4- what are *.i & *.am files?
5- why wlofcrypt headers are not located beside sources and are located in wolfssl/wolfcrpy directory ?

WBR,
Dizgah.

Dear Kaleb,

Thank to your helps, Wolfssl project was built successfully but there is linker problem in building wolf-ssl example project yet.
As you can find in attached below picture and based on read-me file I just added wolfssl & wolfssl_example beside lpc-chip & lpc board reference projects.
but seems there is a setting for lib-wolfssl project in compiler & linker include sections which i could not find.
Also based on below command line output you can see that is a linker problem which could not find lib-wolfssl.a library in

"${workspace_loc:/lib_wolfssl/Debug}"

,Although as I said before wolfssl was built successfully and there is a

libwolfssl.a

file in

"${workspace_loc:/wolfssl/Debug}"

Do you have any suggestion how could I fix it ?

WBR,
Dizgah.

make -r -j4 all 
Building target: wolf_example.axf
Invoking: MCU Linker
arm-none-eabi-gcc -nostdlib -L"D:\workspace\MCUXpresso\wolfssl\Debug" -L"D:\workspace\MCUXpresso\wolfssl\Debug" -L"D:\workspace\MCUXpresso\lpc_chip_18xx\Debug" -L"D:\workspace\MCUXpresso\lpc_board_nxp_lpcxpresso_1837\Debug" -Xlinker -Map="wolf_example.map" -Xlinker --gc-sections -mcpu=cortex-m3 -mthumb -T "wolf_example_Debug.ld" -o "wolf_example.axf"  ./src/lpc_18xx_startup.o ./src/wolfssl_example.o   -llib_wolfssl -lwolfssl -llpc_chip_18xx -llpc_board_nxp_lpcxpresso_1837
c:/nxp/mcuxpressoide_10.3.0_2200/ide/plugins/com.nxp.mcuxpresso.tools.win32_10.3.0.201811011841/tools/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -llib_wolfssl
collect2.exe: error: ld returned 1 exit status
make: *** [makefile:37: wolf_example.axf] Error 1