Getting Started with the LPC54S018-EVK
Contents of this document
-
Plug It In
-
Get Software
-
Build, Run
-
Create
Sign in to save your progress. Don't have an account? Create one.
Purchase your LPCXpresso54S018 Development Board
1. Plug It In
Let's take your LPCXpresso54S018 board for a test drive You have the choice of watching the sequence in a short video or following the detailed actions list below.
1.1 Get Started With the LPCXpresso54S018 Development Board – Demo
1.2 Attach the USB Cable
1.3 Run the Out-of-Box Demo
Your LPCXpresso54S018 board comes preloaded with a “spirit level” demo. The user LEDs (LED1, LED2 and LED3) indicate if the board is level along the horizontal axis of the board. Tilt the board towards or away from you to see the LEDs change.
2. Get Software
2.1 Getting Started With the MCUXpresso SDK
The MCUXpresso Software Development Kit (SDK) is complimentary and includes full source code under a permissive open-source license for all hardware abstraction and peripheral driver software.
Click below to download a pre-configured SDK release for the LPCXpresso54S018, which includes versions for MCUXpresso IDE, Keil MDK and IAR EWArm. Use LPCXpresso54S018 as the target board.
You can also use the online MCUXpresso web tool to create a custom SDK package for the LPCXpresso54S018 using the SDK builder.
2.2 Install your Toolchain
NXP offers a free, GNU/Eclipse based toolchain called MCUXpresso IDE.
Want to use a different toolchain?
No problem, The MCUXpresso SDK includes support for other tools such as IAR and Keil.
To set up your LPCXpresso54S018 for use with 3rd party tools, first install LPCScrypt in order to install the board’s device drivers. The video below shows how to use LPCScrypt to program your board’s debug probe using this utility.
The video on this Getting Started section are for LPCXpresso54608, but the steps are the same for LPCXpresso54S018.
2.3 MCUXpresso Config Tools
The MCUXpresso Config Tool is an integrated suite of configuration tools that guides users in creating new MCUXpresso SDK projects, and provides pin and clock tools to generate initialization C code for custom board support.
2.4 Serial Terminal
Most of the MCUXpresso SDK examples set up for IAR and Keil tools use the MCU UART for printf output, and this is also an option for the MCUXpresso IDE. If you are not sure how to use a terminal application try one of these tutorials: Tera Term Tutorial, PuTTY Tutorial
3. Build, Run
3.1 Explore the MCUXpresso SDK Example Code
The MCUXpresso SDK comes with a long list of example applications code. To see what's available, browse to the SDK boards folder of your SDK installation and select LPCXpresso54S018 (<sdk_install_directory>/boards/LPCXpresso54S018</sdk_install_directory>).
To learn more about specific example code, open the readme.txt file in an example’s directory.
3.2 Build, Run
If one or more of the demo applications or driver examples sounds interesting, you're probably wanting to know how you can build and debug yourself. The Getting Started with SDK for LPC540xx guide provides easy, step-by-step instructions on how to configure, build, and debug demos for all toolchains supported by the SDK.
Use the guide below to learn how to open, build and debug an example application using the MCUXpresso IDE.
Using a different toolchain?
Running a Demo Using IAR or Keil.
4. Create
4.1 Get SDK Project Generator
Let's create our own project and make a simple SDK-based application. NXP provides an intuitive, simple project generation utility that allows creation of custom projects based on the Kinetis SDK.
4.2 Run the SDK Project Generator
After extracting the ZIP file, open the utility by clicking on the KSDK_Project_Generator executable for your computer's operating system. Point the tool to your SDK installation path, name your project, and select the board that it uses as a reference. Click on the Quick Generate button to finish.
4.3 Open Your Project
Your new project will be located in
<sdk_install_directory>/examples/frdmk64/user_apps</sdk_install_directory>. Open the project in your toolchain of choice by using the same process described in section 3.2.
4.4 Write Some Code
Now, let's make our new project do something other than spin in an infinite loop. The SDK examples provide a board support package (BSP) to do various things specific to the board, including macros and definitions for items such as LEDs, switches and peripheral instances. To keep things simple, lets make the LED blink using the BSP macros.
Update the main() function in your project's main.c file with the following code:
volatile int delay;
// Configure board specific pin muxingBOARD_InitPins();
// Configure clock sourceBOARD_BootClockRUN();
// Initialize the UART terminalBOARD_InitDebugConsole();PRINTF("\r\nRunning the myProject project.\n");
// Enable GPIO port for the red LEDCLOCK_EnableClock(kCLOCK_PortE);PORT_SetPinMux(BOARD_LED_RED_GPIO_PORT, BOARD_LED_RED_GPIO_PIN, kPORT_MuxAsGpio);LED_RED_INIT(LOGIC_LED_OFF);for (;;){LED_RED_TOGGLE();delay = 5000000;while(delay--);}4.5 Build, Download, Run
With the changes made to your main() function, build your application. Once the build is complete, download the application to your board.
If you need help figuring out how to build, download or run an application, reference your tool-specific guide from section 3.2.
4.6 Success
With the application downloaded, you will see the FRDM-KE15Z's red LED blinking. You can also view terminal output using PRINTF.
Demo not working?
Did your board come in a box that looks like this?
No problem! Your board simply came in the old packaging and has a different out-of-box demo loaded into the flash memory.
You should be seeing the RGB LED toggling between each of the three colors; red, blue and green. It's OK to move onto the next step when you're ready.
Still not working?
Try proceeding to the next steps to get other example applications running on your board. If you still have problems, try contacting us through the NXP Community.
Running a demo using Kinetis Design Studio IDE
1. Install KDS Updates
Before using KDS IDE with KSDK, it is recommended that you make sure that your tools are up-to-date. The steps discussed below are shown using the Windows version of KDS, but are identical for Mac and Linux users.
-
Select "Help" -> "Check for Updates".
-
Install all updates from Freescale/NXP – these are denoted by “com.NXP.xxx” or “com.nxp.xxx”. There may also be updates for things such as toolchain or debug interfaces. While these additional updates are typically OK to install, sometimes they may cause issues since they aren’t released as part of the KDS toolchain.
2. Build an Example Application
The following steps will guide you through opening the hello_world application. These steps may change slightly for other example applications as some of these applications may have additional layers of folders in their path.
NOTE
The steps required for Linux and Mac OS are identical to those for Windows.
-
Select File->Import from the KDS IDE menu. In the window that appears, expand the "Project of Projects" folder and select "Existing Project Sets". Then, click the "Next" button.
-
Click the "Browse" button next to the "Import from file:" option.
-
Point to the example application project, which can be found using this path:
/boards/ / / /kds For this guide, choose the specific location:
/boards/frdmke15z/demo_apps/hello_world/kds -
After pointing to the correct directory, your "Import Working Sets and Projects" window should look like the figure below. Click the "Finish" button.
-
There are two project configurations (build targets) supported for each KSDK project:
- Debug – Compiler optimization is set to low, and debug information is generated for the executable. This target should be selected for development and debug.
- Release – Compiler optimization is set to high, and debug information is not generated. This target should be selected for final application deployment.
-
Choose the appropriate build target, "Debug" or "Release", by clicking the downward facing arrow next to the hammer icon, as shown below. For this example, select the "Debug" target.
-
The library starts building after the build target is selected. To rebuild the library in the future, click the hammer icon (assuming the same build target is chosen).
3. Run an Example Application
The FRDM-KE15Z board comes loaded with the mbed/CMSIS-DAP debug interface from the factory. If you have changed the debug OpenSDA application on your board, visit http://www.nxp.com/opensda for information on updating or restoring your board to the factory state.
NOTE
Mac users must install the J-Link OpenSDA application in order to use the KDS IDE to download and debug their board.
-
Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.
-
Open the terminal application on the PC (such as PuTTY or TeraTerm) and connect to the debug COM port you determined earlier. Configure the terminal with these settings:
- 15200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
For Linux OS users only, run the following commands in your terminal. These install libudev onto your system, which is required by KDS IDE to launch the debugger.
user@ubuntu:~$ sudo apt-get install libudev-dev libudev1user@ubuntu:~$ sudo ln –s /usr/lib/x86_64-linux-gnu/libudev.so /usr/lib/x86_64-linux-gnu/libudev.so.0 -
Ensure that the debugger configuration is correct for the target you're attempting to connect to. This refers to the OpenSDA interface of your board. If you’re unsure what your board has, please consult Appendix B of the PDF linked in the top right hand corner of this dialog.
-
To check the available debugger configurations, click the small downward arrow next to the green "Debug" button and select "Debug Configurations".
-
In the Debug Configurations dialog box, select debug configuration that corresponds to the hardware platform you’re using. For Windows or Linux users, select is the mbed/CMSIS-DAP option under OpenOCD For Mac users, select J-Link.
After selecting the debugger interface, click the "Debug" button to launch the debugger.
-
-
The application is downloaded to the target and automatically run to main():
-
Start the application by clicking the "Resume" button:
-
The hello_world application is now running and a banner is displayed on the terminal. If this is not the case, check your terminal settings and connections.
Running a demo using Arm
1. Set Up Toolchain
This section contains the steps to install the necessary components required to build and run a KSDK demo application with the Arm GCC toolchain, as supported by the Kinetis SDK. There are many ways to use Arm GCC tools, but this example focuses on a Windows environment. Though not discussed here, GCC tools can also be used with both Linux OS and Mac OSX.
Install GCC Arm Embedded Toolchain
Download and run the installer from launchpad.net/gcc-arm-embedded. This is the actual toolchain (i.e., compiler, linker, etc.). The GCC toolchain should correspond to the latest supported version, as described in the Kinetis SDK Release Notes.
Install MinGW
The Minimalist GNU for Windows (MinGW) development tools provide a set of tools that are not dependent on third party C-Runtime DLLs (such as Cygwin). The build environment used by the KSDK does not utilize the MinGW build tools, but does leverage the base install of both MinGW and MSYS. MSYS provides a basic shell with a Unix-like interface and tools.
-
Download the latest MinGW mingw-get-setup installer from sourceforge.net/projects/mingw/files/Installer/.
-
Run the installer. The recommended installation path is C:\MinGW, however, you may install to any location.
-
Ensure that the "mingw32-base" and "msys-base" are selected under Basic Setup.
-
Click "Apply Changes" in the "Installation" menu and follow the remaining instructions to complete the installation.
-
Add the appropriate item to the Windows operating system Path environment variable. It can be found under Control Panel -> System and Security -> System -> Advanced System Settings in the "Environment Variables..." section. The path is:
\bin Assuming the default installation path, C:\MinGW, an example is shown below. If the path is not set correctly, the toolchain does not work.
NOTE
If you have "C:\MinGW\msys\x.x\bin" in your PATH variable (as required by KSDK 1.0.0), remove it to ensure that the new GCC build system works correctly.
-
Download CMake 3.0.x from www.cmake.org/cmake/resources/software.html.
-
Install CMake, ensuring that the option "Add CMake to system PATH" is selected when installing. It's up to the user to select whether it's installed into the PATH for all users or just the current user. In this example, the assumption is that it's installed for all users.
-
Follow the remaining instructions of the installer.
-
You may need to reboot your system for the PATH changes to take effect.
NOTE
The installation path cannot contain any spaces.
Add a New Environment Variable for ARMGCC_DIR
Create a new system environment variable and name it ArmGCC_DIR. The value of this variable should point to the Arm GCC Embedded tool chain installation path, which, for this example, is:
C:\Program Files (x86)\GNU Tools Arm Embedded\4.9 2015q3
Reference the installation folder of the GNU Arm GCC Embedded tools for the exact path name of your installation.
Install CMake
2. Build an Example Application
To build an example application, follow these steps.
-
1. If not already running, open a GCC Arm Embedded tool chain command window. To launch the window, from the Windows operating system Start menu, go to “Programs -> GNU Tools Arm Embedded
” and select “GCC Command Prompt”. 
-
Change the directory to the example application project directory, which has a path like this:
/boards/ / / /armgcc For this guide, the exact path is:
/boards/frdmke15z/demo_apps/hello_world/armgcc -
Type “build_debug.bat” on the command line or double click on the "build_debug.bat" file in Windows operating system Explorer to perform the build. The output is shown in this figure:
3. Run an Example Application
The GCC tools require a J-Link debug interface. To update the OpenSDA firmware on your board to the latest J-Link app, visit www.nxp.com/opensda. After installing the J-Link OpenSDA application, download the J-Link driver and software package from www.segger.com/downloads.html.
-
Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.
-
Open the terminal application on the PC (such as PuTTY or TeraTerm) and connect to the debug COM port you determined earlier. Configure the terminal with these settings:
- 15200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Open the J-Link GDB Server application. Assuming the J-Link software is installed, the application can be launched by going to the Windows operating system Start menu and selecting "Programs -> SEGGER -> J-Link
J-Link GDB Server". -
Modify the settings as shown below. The target device selection chosen for this example is the “MK64FN1M0xxx12” and use the SWD interface.
-
After it is connected, the screen should resemble this figure:
-
If not already running, open a GCC Arm Embedded tool chain command window. To launch the window, from the Windows operating system Start menu, go to "Programs -> GNU Tools Arm Embedded
" and select "GCC Command Prompt". 
-
Change to the directory that contains the demo application output. The output can be found in using one of these paths, depending on the build target selected:
/boards/ / / /armgcc/debug /boards/ / / /armgcc/release For this guide, the path is:
/boards/frdmke15z/demo_apps/hello_world/armgcc/debug -
Run the command "arm-none-eabi-gdb.exe
.elf". For this example, it is "arm-none-eabi-gdb.exe hello_world.elf". 
-
Run these commands:
- "target remote localhost:2331"
- "monitor reset"
- "monitor halt"
- "load"
- "monitor reset"
-
The application is now downloaded and halted at the reset vector. Execute the "monitor go" command to start the example application.
The hello_world application is now running and a banner is displayed in the terminal window.
Tera Term Tutorial
Tera Term Tutorial
Tera Term is a very popular open source terminal emulation application. This program can be used to display information sent from your NXP development platform's virtual serial port.
- Download Tera Term from SourceForge. After the download, run the installer and then return to this webpage to continue.
- Launch Tera Term. The first time it launches, it will show you the following dialog. Select the serial option. Assuming your board is plugged in, there should be a COM port automatically populated in the list.
- Configure the serial port settings (using the COM port number identified earlier) to 115200 baud rate, 8 data bits, no parity and 1 stop bit. To do this, go to Setup -> Serial Port and change the settings.
- Verify that the connection is open. If connected, Tera Term will show something like below in it's title bar.
- You're ready to go
PuTTY Tutorial
PuTTY Tutorial
PuTTY is a popular terminal emulation application. This program can be used to display information sent from your NXP development platform's virtual serial port.
- Download PuTTY using the button below. After the download, run the installer and then return to this webpage to continue
- Launch PuTTY by either double clicking on the *.exe file you downloaded or from the Start menu, depending on the type of download you selected
- Configure In the window that launches, select the Serial radio button and enter the COM port number that you determined earlier. Also enter the baud rate, in this case 115200
- Click Open to open the serial connection. Assuming the board is connected and you entered the correct COM port, the terminal window will open. If the configuration is not correct, PuTTY will alert you
- You're ready to go
Running a Demo Using IAR or Keil®
Learn how to build and run a simple example using IAR or Keil Third Party IDE toolchains.
Running a Demo Using IAR
Build an Example Application
The following steps will guide you through opening the led_output application. These steps may change slightly for other example applications as some of these applications may have additional layers of folders in their path.
-
If not already done, open the desired example application workspace. Most example application workspace files can be located using the following path:
<install_dir >/boards/<sdk_board_name >/<example_type>/<application_name>/iar</application_name></example_type></sdk_board_name ></install_dir >Using the hello_world demo as an example, the path is:
<install_dir>/boards/LPCXpresso54S018/driver_examples/gpio/led_output/iar</install_dir> -
Select the desired build target from the drop-down. For this example, select the “hello_world – Debug” target.
-
To build the application, click the “Make” button, highlighted in red below.
The build will complete without errors.:
Run an Example Application
The LPCXpresso54S018 board comes loaded with the CMSIS-DAP debug interface from the factory. Connect the development platform to your PC via USB cable to J8 “Debug Link”.
-
Click the "Download and Debug" button to download the application to the target.
-
The application is then downloaded to the target and automatically runs to the main() function.
-
Run the code by clicking the "Go" button to start the application.
Running a Demo Using Keil MDK/µVision®
Install CMSIS device pack
After the MDK tools are installed, Cortex® Microcontroller Software Interface Standard (CMSIS) device packs must be installed to fully support the device from a debug perspective. These packs include things such as memory map information, register definitions and flash programming algorithms. Follow these steps to install the appropriate CMSIS pack.
-
Open the MDK IDE, which is called µVision. In the IDE, select the "Pack Installer" icon.
-
2. In the Pack Installer window, navigate to the section with the LPC packs (they are in alphabetical order). The Kinetis packs start with "Keil::LPC" and are followed by the MCU family name, for example "Keil::LPC54000". Because this example uses the LPCXpresso54S018 platform, the LPC54000 family pack is selected. Click on the "Install" button next to the pack. This process requires an internet connection to successfully complete.
-
After the installation finishes, close the Pack Installer window and return to the µVision IDE.
Build the Example Application
The following steps will guide you through opening the gpio_led_output application. These steps may change slightly for other example applications as some of these applications may have additional layers of folders in their path.
-
If not already done, open the desired demo application workspace in:
<install_dir >/boards/<sdk_board_name >/<example_type>/<application_name>/mdk</application_name></example_type></sdk_board_name ></install_dir >The workspace file is named
<application_name>.uvmpw, so for this specific example, the actual path is:</application_name><install_dir>/boards/LPCXpresso54S018/driver_examples/gpio/led_output/mdk/gpio_led_output.uvmpw</install_dir> -
To build the demo project, select the "Rebuild" button, highlighted in red.
The build will complete without errors.
Run an Example Application
The LPCXpresso54S018 board comes loaded with CMSIS-DAP debug interface from the factory.
- After the application is properly built, click the "Download" button to download the application to the target
- After clicking the "Download" button, the application downloads to the target and should be running. To debug the application, click the "Start/Stop Debug Session" button, highlighted in red
- Run the code by clicking the "Run" button to start the application
Design Resources
Board Information
Support
Learn more about the LPC54S018-EVK with design tips, training documents, and the NXP Community. If you need additional help, contact NXP Support.
Troubleshooting
With the application downloaded, you will see the FRDM-KE15Z's red LED blinking. You can also view terminal output using PRINTF.
Demo not working?
Did your board come in a box that looks like this?
No problem, your board simply came in the old packaging and has a different out-of-box demo loaded into the flash memory.
You should be seeing the RGB LED toggling between each of the three colors; red, blue and green. It's OK to move onto the next step when you're ready.
Still not working?
Try proceeding to the next steps to get other example applications running on your board. If you still have problems, try contacting us through the NXP Community .
On this page
- 1.1
Get Started With the LPCXpresso54S018 Development Board – Demo
- 1.2
Attach the USB Cable
- 1.3
Run the Out-of-Box Demo
- 2.1
Getting Started With the MCUXpresso SDK
- 2.2
Install your Toolchain
- 2.3
MCUXpresso Config Tools
- 2.4
Serial Terminal