MSP432E411Y: Features implemented in TivaWare but not in SimpleLink?

Hello Sven,

Sven Probst said:

I'm not sure which one to choose, because I read a lot about TivaWare, but got the impression that SimpleLink might fit better to our needs (mainly due to more fitting example code for TI-RTOS).

If you are starting a new project and require Ethernet, we would recommend using the MSP432E4 device and the SimpleLink MSP432E4 SDK.

You might already be aware that the MSP432E4 device is part of the SimpleLink Platform, which allows you to seamlessly add wireless protocols, in case you anticipate needing the wireless capabilities in the future. For example, using the MSP432E4 and a CC32xx device (for building a WiFi-Ethernet gateway) is much easier since SimpleLink SDK Plugins that support various stacks are readily available.

SimpleLink SDK also greatly simplifies porting (or writing new) code to other (wireless) devices in the family.

TI-RTOS is integrated into the SimpleLink SDK along with the NDK TCP/IP stack and the Network Services layer. With the SimpleLink SDK, you can use industry standard APIs like POSIX and BSD-Sockets.

Sven Probst said:

What about the documentation

Most of the SimpleLink SDK documentation is included with the SDK installer. This documentation can also be  accessed through the cloud using the Documentation Overview Page on dev.ti.com.

Sven Probst said:

How did you realize project specific .cfg files? (Many example projects reference to a TI-RTOS build project, which contains the .cfg file.)

You could rename the TI-RTOS project and update the example's dependencies to point to this renamed TI-RTOS project.

For example, if you import "tcpecho" (from the folder ./examples/rtos/MSP_EXP432E401Y/ns/tcpecho), the TI-RTOS project "tirtos_builds_MSP_EXP432E401Y_release_ccs" also gets imported. Rename this TI-RTOS project. Then in the "tcpecho" Project Settings, under Build->Dependencies,  remove the project "tirtos_builds_MSP_EXP432E401Y_release_ccs" and add the renamed TI-RTOS project. This has to be done for both the configurations - Debug and Release.

Hope this information helps you!

Thanks,

Sai

Sven,

Please note in the SimpleLink SDK and when you are using TI-RTOS, both methods for .cfg placement are supported. Here's a quick pros/cons of the two methods

1. App project + kernel project: The majority of the examples use this approach. Many customers like sharing a single kernel configuration across multiple applications. Some customers like the isolation of the kernel with this approach also (e.g. easier source control). Also, rebuilds (clean/build) are faster for the application project since the kernel project is only built once (and when the kernel project is changed).

2. App project with .cfg in the project: This is more the traditional way (i.e. in the TI-RTOS for TivaC product examples). It allows you to customize the kernel specifically for the application if needed.

You can add a .cfg into an application project to convert a method 1 setup to a method 2 setup. Careful though, you can remove the .cfg then! Here's a write-up on how to do that: dev.ti.com/.../

Todd