Getting Started with the LPC845-BRK Breakout 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. In the Pack Installer window, search for “LPC845” to bring up the LPC845 family. Click on the name, and then in the right-hand side you’ll see the NXP::LPC845 _DFP pack. 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 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. If not already done, open the desired demo application workspace in:
   
   /folder_name//mdk
   
   The workspace file is named .uvprojx, so for this specific example, the actual path is:
   
   > LPC845BRK_Examples_Keil> LPC845_Breakout_led_blinky_Keil > _led_blinky_KEIL. uvprojx
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

1. Connect the development platform to your PC via USB cable to CN3 “Debug Link”. Ensure the DFULink jumper (JP1) is removed when powering the board to boot the debug probe from internal flash.
2. After the application is properly built, click the "Download" button to download the application to the target.
   

3. After the application is properly built, click the "Download" button to download the application to the target.

   
4. Click on “Start/Stop Debug Session” to open the debug view.
   
5. Run the code by clicking the "Run" button to start the application.
   
6. The application is now running, you are going to see the RGB blue led Blinky every second.

1. Import the MCUXpresso SDK

1. Open the MCUXpresso IDE
   
2. Switch to the Installed SDKs view within the MCUXpresso IDE window
   
3. Drag and drop the LPC845 SDK (zipped) file (that we downloaded in the previous section) into the Installed SDKs view.
4. You will get the following pop-up. Click on OK to continue the import:
   
5. The installed SDK will appear in the Installed SDKs view as shown below:
   

2. Build an Example Application

The following steps will guide you through opening the led_blinky example that the release package include.

1. Find the Quickstart Panel in the lower left-hand corner
   

2. Then click on Import project(s) from file system…

   

3. Then browse the examples packages archive file:

   

4. Press next, and see that are a selection of projects to import, in this case, only keep select the LPC845-Breakout_led_blinky_MCU how it looks in the picture below:

   

5. Now build the project by clicking on the project name and then in the Quickstart Panel click on Build or press “Ctrl + b.”

   

6. You can see the status of the build in the console tab.

   

3. Run an Example Application

1. Now that the project has been compiled, you can now flash it to the board and run it, make sure the LPC845 Breakout Board is plugged in, and click on Debug in the Quickstart Panel.
   
2. MCUXpresso IDE will probe for connected boards and should find the CMSIS-DAP debug probe that is part of the integrated LPC11U35 circuit on the LPC845 Breakout Board. Click on OK to continue.
   
3. The firmware will be downloaded to the board and the debugger started.
   
4. Start the application by clicking the "Resume" button:
   
5. The application is now running, you are going to see the RGB blue led Blinky every second.
6. Use the controls in the menu bar to pause, step into, and step over instructions, and then stop the debugging session by click on the Terminate icon:
   

*Note: Previously, you had to clone a SDK project like in the past step.

1. Convert IDE project to correct Package (Note, the IDE doesn’t really care, this just helps avoid other conflicts).

1. Expand lpcxpresso845max_hello_world >> Project Setting >> MCU, note chip a package values.
   
2. Right-click “lpcxpresso845max_hello_world” project and select Utilities >> Open directory browser here.
   
3. Drag-and-Drop. cproject file into the IDE text editor (to use the build-in XML editor)
   
4. Locate the package variable (should be in the “storageModule” from the bottom but if is not there search in all the others storageModule).
   
5. Edit package to: LPC845M301JBD48 and save the .cproject file.
   
6. Right-click “lpcxpesso845max_hello_world” project and select refresh (F5).
   

2. Convert the SDK drivers to use the correct header declarations.

1. Expand lpcxpresso835max_hello_world >> Project Settings >> Options. Right-click in Options and select “Edit Options.
   
2. Select MCU C Compiler >> Preprocessor Folder.
   
3. Change both instances of LPC845M301JBD64 to LPC845M301JBD48.
   
4. Click on “Apply and Close”

3. Enable Config Tools and apply the previously create configuration to this new project.

1. Use the project Explore menu bar to launch Config Tools and Open Pins.
   
2. Ensure the correct project is from the drop-down menu in the tool bar.
   
3. Click on the Switch Package button is on the toolbar in the top right corner of the package window.
   
4. In the Pop-up Window Select LPC845M301JBD48- LQFP 48 package and click on OK.
   
5. Now we are going to import the .mex file that we download before. Go to File >> Import.
   
6. Inside the MCUXpresso Config Tools Folder Select “Import Configuration(*.mex)” and click on Next.
   
7. Select the. mex file downloaded previously as the Existing configuration, and the name of the current project as Target Project and click on Finish
   
8. Observe the pins that are activated and notice that the configuration is the same as in the previous case. Open the Clock Tool to see that the System clock has also been update to 30 MHz.
9. Now it’s time to implement these changes into the GPIO project by exporting the new updated pin_mux.c and pin_mux.h files that are generated by the Pins tool. Click on Update Project in the menu bar.
   
10. The screen that pops up will show the files that are changing, and you can click on “diff” to see the difference between the current file and the new file generated by the Pins tool. Click on “OK” to overwrite the new files into your project.
    
11. Now inside the IDE, open the hello_world.c file.
    
12. Replace the BOARD_BootClockFRO30M function for BOARD_InitBootClocks.
    
13. Open a terminal program and connect to the COM port the board enumerated as. Configure the terminal with these settings:
    • 115200 baud rate
    • No parity
    • 8 data bits
    • 1 stop bit
14. Build and Run the application like in the previous step. 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.
    
15. Terminate the debug session.

1. Open the MCUXpresso Config Tool.
   
2. In the wizard that comes up, select the “Open existing configuration” radio button, then select the project that you had clone and click on Next.
   *Note: Previously, you had to clone a SDK project like in the past step, in case that you didn’t had, choose the option Clone SDK example and create a new configuration.
   
3. Open the pins tool by selecting Tools->Pins from the toolbar
   
4. Click on the Switch Package button is on the toolbar in the top right corner of the package window.
   
5. In the Pop-up Window Select LPC845M301JBD48- LQFP 48 package and click on OK.
   
6. Now we are going to import the .mex file downloaded in the past step. Go to File >> Import.
   
7. Select “Import Configuration(*.mex)” and click on Next.
   
8. Select the .mex file downloaded previously as the Existing configuration and click on Finish.
   
9. Observe the pins that are activated and notice that the configuration is the same as in the previous case. Open the Clock Tool to see that the System clock has also been update to 30 MHz
10. Now it’s time to implement these changes into the GPIO project by exporting the new updated pin_mux.c and pin_mux.h files that are generated by the Pins tool. Click on Update Project in the menu bar.
    
11. The screen that pops up will show the files that are changing, and you can click on “diff” to see the difference between the current file and the new file generated by the Pins tool. Click on “OK” to overwrite the new files into your project.
    
12. Now open the project, build and run like in the previous section.

1. Clone an Example Application

The following steps will guide you through opening the hello_world example. The Hello World demo application provides a sanity check for the new SDK build environments and board bring up. The Hello World demo prints the "hello world." string to the terminal using the SDK UART drivers. The purpose of this demo is to show how to use the UART, and to provide a simple project for debugging and further development.

1. Find the Quickstart Panel in the lower left-hand corner
   
   
   Then click on Import SDK examples(s)…
   
2. Click on the LPCXpresso845max board to select that you want to import an example that can run on that board, and then click on Next.
   
3. Use the arrow button to expand the demo_apps category, and then select the hello_world project. To use the UART for printing (instead of the default semihosting), Select UART as the SDK Debug Console checkbox under the project options. Then, click on Finish
   
4. Now you can see the example in the projects windows
   
5. Go to the next section to see how use a .mex file configuration to modify this example and running in your LPC845 Breakout Board.

1. Open the MCUXpresso Config Tool.
   
2. In the wizard that comes up, select the “Create a new configuration based on an SDK example or hello world project” radio button and click on Next.
   
3. On the next screen, select the location of the MCUXpresso SDK that you had unzipped earlier. Then select the IDE that is being used. Note that only IDEs that were selected in the online SDK builder when the SDK was built will be available.
   Then select the project to clone. For this example, we want to use the hello world project. You can filter for this by typing “hello_world” in the filter box and then selecting the “hello_world” project. You can then also specify where to clone the project and the name. Then click on Finish.
   
4. Go to the next section to see how use a .mex file configuration to modify this example and running in your LPC845 Breakout Board.

The most recent versions of MCUXpresso IDE count with a terminal emulation application. This tool can be used to display information sent from your NXP development platform's virtual serial port.

1. Open the MCUXpresso IDE.
   
2. Launch the MCUXpresso IDE terminal by clicking on the “Open a Terminal” button on the top of the IDE or press “Ctrl + Alt + Shift + T.”
   
3. Select Serial Terminal.
   
4. Configure the serial port settings (using the LPCXpresso COM port number) to 115200 baud rate, 8 data bits, no parity and 1 stop bit, then press “OK” button.
   
5. Verify that the connection is open. If connected, MCUXpresso IDE will look like the figure below at the Terminal view.
   
6. You're ready to go.

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

    

1. Open MCUXpresso Config Tools.
2. Open the Clocks tool from the toolbar: Tools->Clocks.
3. The clock configuration for the “led_output” project will appear in the clocks tool:
4. Switch to the Clocks Diagram view by clicking the tab in the upper left corner, and ensure that the BOARD_BootClockRUN clock mode is being displayed by clicking the tab in the lower left corner.
5. Change the core clock frequency by clicking in the Core Clock field and typing “12 MHz”. You’ll see all the associated clock frequencies automatically change as well then.
6. Now open the “Sources” tab and export the clock_config.c and clock_config.h files.

7. Select the directory to export the clock_config.c and clock_config.h files. In this example export to the “board” folder in the led_output project in the workspace.

   (i.e. C:\MCUXpressoIDE_Lab\frdmk64f_driver_examples_gpio_led_output\board). Select Finish.

   
8. Press Yes to replace the existing clock_config.c and clock_config.h files.
9. Now open the led project in your IDE, and build, download, and run the project as you did before.
10. The blue LED should now be blinking at a much slower rate