This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432E411Y: MSP432E4 & SSL/TLS

Guru 39650 points
Part Number: MSP432E411Y
Other Parts Discussed in Thread: CC3220SF, CC3235SF

Hi,

In my projects I use CC32xx devices where is SSL/TLS stack integrated inside NWP. But I have a project with wired Ethernet. In this case looks MSP432E4 promising due to integrated Ethernet PHY. Secured sockets SSL/TLS (TLS 1.2 or TLS 1.3) are one of mandatory features.

Does TI provide own SSL stack or is mandatory to use 3rd party stack? Are examples of SSL usage available? There is many 3rd party SSL stacks, but how it looks with MSP432E4 integration? Some SSL stacks like a wolfSSL are not achievable due to high price, but some like emSSL, TLS stack from HCC looks have reasonable price. Finally is here mbed TLS but I am not sure about Apache license compatibility.

Thank you for any comment or link to proper documentation.

BTW ... it is possible to get privately route map of MSP432 devices with Ethernet PHY (I think ours NDA was updated to cover MCUs as well)?

Jan

  • I will ask my colleage to comment but more information can be found here in the Network Services User's Guide. Specifically, mbedtls, is used.

    dev.ti.com/.../

    Regards,
    Chris
  • Hi Chris,

    OK, after quick look to examples in MSP432E4 SDK, I understood what you want to say. But any additional comment will be welcome.

    But I still afraid about insufficient memory resources in MSP432E411. At CC3220SF/CC3235SF I have 256kB RAM and 1MB XIP flash and this is fine for my application. At MSP432E411 is same size of memory, but TCP/IP stack and SSL stack will consume this memory resource in MCU. CC3220/CC3235 have this all network features in dedicated core NWP. From this reason I am interesting about MCU with Ethernet PHY and higher memory capabilities

    Jan
  • Hello Jan,

    As Chris has pointed out,  mbedTLS is used in SimpleLink MSP432E4 SDK because of the user friendly Apache License. The mbedTLS is highly integrated into the Network Services layer; please  refer the link that Chris Sterzik (14446) has pointed out. Additional advantage of using the Network Services layer is it allows application code portability with the SimpleLink CC32xx SDK or the SimpleLink SDK Wi-Fi Plugin; there will still be minor modifications required but the porting effort should be fairly quick.

    As you have already noted, the MSP432E4 MCU does not have a separate networking core/memory. You could use one of the examples in the SDK (./examples/rtos/MSP_EXP432E401Y/ns/) to get an idea about how much memory the NDK Stack and Network Services layer consumes. Please note that the configuration of the examples and the Stacks is provided for a very generic case. By fine tuning as per your use case could allow savings in both the program and data memory.

    Thanks,

    Sai

  • Hi Sai,

    Thank you for a comment.

    At my CC32xx I use own network abstraction layer instead SlNetIf layer. But I understand structure of network layers. Portability at layer SlNetIf is slightly disputable, but that would be a longer discussion.

    Again thank you for your valuable support.

    Jan

**Attention** This is a public forum