Getting Started with the LPCXpresso54628 Development Board

1. 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.

1. Open the MDK IDE, which is called µVision. In the IDE, select the "Pack Installer" icon.

   

2. 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 LPCXpresso54628 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.

   

3. After the installation finishes, close the Pack Installer window and return to the µVision IDE.

2. 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.

1. If not already done, open the desired demo application workspace in:

   /boards////mdk

   The workspace file is named .uvmpw, so for this specific example, the actual path is:

   /boards/LPCXpresso54628/driver_examples/gpio/led_output/mdk/gpio_led_output.uvmpw

2. To build the demo project, select the "Rebuild" button, highlighted in red.

   

3. The build will complete without errors.

3. Run an Example Application

The LPCXpresso54628 board comes loaded with CMSIS-DAP debug interface from the factory.

1. After the application is properly built, click the "Download" button to download the application to the target.
   
   
2. 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.
   
   
3. Run the code by clicking the "Run" button to start the application.
   
   

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.

1. Select "Help" -> "Check for Updates".

   

2. 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.

1. 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.

   

2. Click the "Browse" button next to the "Import from file:" option.

   

3. 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

4. After pointing to the correct directory, your "Import Working Sets and Projects" window should look like the figure below. Click the "Finish" button.

   

5. 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.

6. 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.

   

7. 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.

1. Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.

2. 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

3. 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 libudev1

   user@ubuntu:~$ sudo ln –s /usr/lib/x86_64-linux-gnu/libudev.so /usr/lib/x86_64-linux-gnu/libudev.so.0

4. 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.

     

5. The application is downloaded to the target and automatically run to main():

   

6. Start the application by clicking the "Resume" button:

   

7. 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.

   

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.

1. Download the latest MinGW mingw-get-setup installer from sourceforge.net/projects/mingw/files/Installer/.

2. Run the installer. The recommended installation path is C:\MinGW, however, you may install to any location.

NOTE

The installation path cannot contain any spaces.

3. Ensure that the "mingw32-base" and "msys-base" are selected under Basic Setup.

   

4. Click "Apply Changes" in the "Installation" menu and follow the remaining instructions to complete the installation.

   

5. 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.

   

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

1. Download CMake 3.0.x from www.cmake.org/cmake/resources/software.html.

2. 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.

   

3. Follow the remaining instructions of the installer.

4. You may need to reboot your system for the PATH changes to take effect.

2. Build an Example Application

To build an example application, follow these steps.

1. 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”.

   

2. 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

3. 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.

1. Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.

2. 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

3. 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".

4. Modify the settings as shown below. The target device selection chosen for this example is the “MK64FN1M0xxx12” and use the SWD interface.

   

5. After it is connected, the screen should resemble this figure:

   

6. 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".

   

7. 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

8. Run the command "arm-none-eabi-gdb.exe .elf". For this example, it is "arm-none-eabi-gdb.exe hello_world.elf".

   

9. Run these commands:

   • "target remote localhost:2331"
   • "monitor reset"
   • "monitor halt"
   • "load"
   • "monitor reset"

10. 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.