4.2. Import MCUXPresso projects from SDK¶
With Plug & Trust middleware, MCUXPresso SDKs are supplied for supported boards. Projects can be imported/executed from these SDKs.
For more details refer - https://www.nxp.com/docs/en/application-note/AN12396-Quick_start_guide_kinetis_k64.pdf
4.2.1. Prerequisite¶
MCUXpresso installed. Refer to Setting up MCUXPresso IDE for details on installation
Plug & Trust Middleware SE050 MCUXPresso SDK Package is downloaded and available
4.2.2. Importing an example¶
Drag and drop SDK to “Install SDKs” windows of MCUXPresso. Even if you have older SDK, you can drag and drop. MCUXPresso will take the latest SDK based on version number.

Accept the request to import the SDK.

You should see a new / updated entry. In this case version 2.6.5. Based on the release, this version may change. If you have Newer version of SDK, and you would like to use this version, you must delete the old SDK.

From the “Quickstart Panel” –> “Import SDK Example(s)”

You must see K64F with SE050 marked. For other SDKs, same convention follows. If you do not see SE050 there, it means you have newer version of the SDK and you must delete them.

When you import and click next, you will see support examples for that board.
Select the example you would like to run/test. In this case, we go for “minimal”

You can choose different settings if you like to as supported by MCUXPresso

Now the examples are ready to be tested.

4.2.3. Running / Debugging example¶
Click on Build to compile and generate the executables

Click on debug to program the binary into the device

Select J-Link OpenSDA and click on OK. For more details on OpenSDA, refer to

Click on the Resume button to start program execution

4.2.4. Logging on console¶
For UART, a serial terminal application(for e.g Tera Term) on PC for
serial device needs to be configured as follows ( in Tera Term goto Setup
–> Serial port
)
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Once the program execution begins, logs are printed on the terminal(e.g. Tera Term) indicating the status of execution and test results. The ATR and the various module versions are printed followed by a SELECT-DONE after which the respective test logs are printed.