<![CDATA[wolfSSL - Embedded SSL Library — Chip maker support]]> https://www.wolfssl.com/forums/topic674-chip-maker-support.html Tue, 14 Jul 2015 19:16:10 +0000 PunBB <![CDATA[Re: Chip maker support]]> https://www.wolfssl.com/forums/post2065.html#p2065 Hi Fred,

NXP isn't necessarily harder, we just haven't put together specific instructions for it yet.  In general, you should be able to follow the steps outlined in Section 2.4 of the wolfSSL Manual:

http://wolfssl.com/wolfSSL/Docs-wolfssl … lfssl.html

Best Regards,
Chris

]]> Tue, 14 Jul 2015 19:16:10 +0000 https://www.wolfssl.com/forums/post2065.html#p2065 <![CDATA[Chip maker support]]> https://www.wolfssl.com/forums/post2064.html#p2064 Hello,

I'm looking information about running wolfCrypt on an embedded device (I mean C code running on a MCU).

The web page of wolfCrypt (and wolfssl too) says:

wolfCrypt has support for chipsets including ARM, Intel, Motorola, mbed, Freescale, Microchip (PIC32), ST (STM32F2/F4), NXP, Analog Devices, Texas Instruments, and more

Reading the manual there are some specific instructions for building the code to run in a Microchip and ST MCU. However, there is no information about, for example, NXP MCU.

Are NXP MCU harder to support or are they supported out of the box? does the same applies to the others chipmaker that have not specific instructions?

Thanks for your comments.

- Fred

]]> Tue, 14 Jul 2015 14:44:45 +0000 https://www.wolfssl.com/forums/post2064.html#p2064