Let’s take your MC56F80000-EVK for a test drive
There are two micro-USB connectors on the board. The bottom one (J12) is for on-board OpenSDA to support programming, debugging and virtual serial port. The upper one (J26) is used as virtual serial port realized by CP2012N. Both micro-USB connectors can supply power for the board. Plug the USB cable into the bottom one for OpenSDA.
Your MC56F80000-EVK board comes loaded with a simple switch LED demo. The green LED D2 lights up, indicating that the board is powered on. The LEDs D7, D8, D5 light up one by one, and then turn off one by one.
Installing software for the MC56F80000-EVK
NXP offers a complimentary toolchain called CodeWarrior IDE. There are many versions of this IDE, to support MC56F80xxx, the version of the CodeWarrior for MCUs should be v11.2 or later.
You can find the installation steps for CodeWarrior v11.2 below.
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.
Let's find out how to download the latest SDK release for the MC56F80000-EVK.
You will find all the 56F807xx series parts shown here. Due to the MC56F80748 that is used on the EVK, we select the MC56F80748 here. If the other parts are used on your side, please select the corresponding item to download the appropriate SDK package.
FreeMASTER is a user-friendly real-time debug monitor and data visualization tool that enables runtime configuration and tuning of embedded software applications. Click below to download the latest FreeMASTER.
The OpenSDA supports the virtual COM port communication on MC56F80000-EVK for FreeMASTER.
If using the CP210x USB to UART bridge virtual COM port communication on MC56F80000-EVK, you need to download and install the CP210x drivers. The CP210x Windows Drivers v6.7.6 works well here.
The MCUXpresso Config Tool is an integrated suite of configuration tools that guides users in creating new MCUXpresso SDK projects, and also provides pin and clock tools to generate initialization C code for custom board support. It’s recommended to install the latest version of the MCUXpresso Config Tools.
Many of the MCUXpresso SDK examples output data over the MCU UART. Make sure you install an terminal application.
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.
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.
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 mc56f80000evk(< SDK_Install_Directory >/boards/mc56f80000evk
).
To learn more about specific example code, open the readme.txt file in an example’s directory
If one or more of the demo application or driver examples sound interesting, you’re probably wanting to know how you can build and debug by yourself. The following guide provides easy, step-by-step instructions on how to open, build and debug an example code using the CodeWarrior IDE.
< SDK_Directory>/boards/ mc56f80000evk/demo_apps/hello_world
, select
codewarrior and click OK.
Note: Don’t modify the project here, otherwise the SDK package will be
changed. Don’t send this project to others, because it’s a linked project to your SDK package. See next
section about how to create a new standalone project.
Now the project appears in the CodeWarrior Project view of the Workbench window. The project has four build configurations with different optimization configuration and memory model.
‘flash_sdm_lpm_debug
and ‘‘flash_ldm_lpm_debug’
are configured as speed
optimization level 1, ‘flash_sdm_lpm_release’
and ‘flash_ldm_lpm_release’
are
configured as speed optimization level 4. ‘flash_sdm_lpm_debug’
and
‘flash_sdm_lpm_release’
are configured as small data and large program memory model,
‘flash_ldm_lpm_debug’
and ‘flash_ldm_lpm_release’
are configured as large data and
large program memory model.
Click on the configuration name and choose the desired build configuration.
Now the project has been compiled, you can now download it to the board and run it. Make sure the MC56F80000-EVK is plugged in.
When a bare-mental project is preferred, use the CodeWarrior new project wizard to create a new project. Now, let’s use CodeWarrior to show how to create a bareboard project and edit on it.
There are three files in the new project that are most in need of modification: main.c, Flash_config.c and Cpu.c.
Use the MCUXpresso Config Tool to create a new project based on the SDK.
The following steps will guide you through creating a project with MCUXpresso Config Tool.
Now, let’s use the clocks tool that’s part of the MCUXpresso Config Tool to change the clock settings.
Next use the Pins tool that is part of the MCUXpresso Config Tool to show how to add a new GPIO pin to your project to blink an LED
Option A: Find GPIOF in Peripherals signals window, then click the box next to the GPIOF. And select GPIO6 in the pop-up window, then click Done. The pin will then appear in the Routing details window.
Option B: Add a new row directly in Routing details window, click the peripheral box and select GPIOF, then select GPIO,6 in the signal box.
Next use the Peripherals tool that is part of the MCUXpresso Config Tool to show how to configure a PIT for LED blinking frequency control.
With the template modified, you will see the MC56F80000-EVK’s red LED blinking.
Explore beyond the MC56F80000-EVK by integrating other NXP solutions and software to your project and interact with our worldwide design community.
MC56F80000-EVK form-factor compatible with the LVPMSM and LVBLDC motor control platform, adds the motor control capabilities. Find out more at nxp.com/FRDM-MC-LVPMSM and nxp.com/FRDM-MC-LVBLDC.
Connect with other engineers and get expert advice on designing with DSC and MCUXpresso Software and Tools. Join the community discussion in one of our two dedicated communities: