# MCUXpresso ## Installing MCUXpresso We will install MCUXpresso inside the virtual machine (or native Linux environment). This allows us to let MCUXpresso build the PX4 firmware, flash it to the FMUK66 and debug the code while it is running on the board. You can also install MCUXpresso on your host operating system, but we recommend to keep everything in a Linux environment unless you know what you are doing. It will save you a lot of headache. The MCUXpresso IDE is available free of charge and can be downloaded from the NXP website, but you will need to create a (free) NXP account: {% embed url="" %} Click on the download button and login to your NXP account. The next page will show the current available releases. There is also a tab for previous releases. You should download the current release (11.1.1 as of June 2020), click on "MCUXpresso IDE" to continue. You will have to agree with some terms and conditions before you can download the software. Download the `.deb.bin` file for Linux. You can directly download it using the Firefox browser in the virtual machine or you can download it on your host operating system and move it into the [shared folder](https://nxp.gitbook.io/nxp-cup/developer-guide/development-tools/rddrone-fmuk66-development/installing-ubuntu#shared-folders). Assuming you have the file stored in the `~/Downloads` folder, you should first enter the command below to allow the package to be executed and installed. You should replace the last part of the filename with the right version number for your download! You can use the auto-complete feature for this by pressing the tab key. Just start typing the command below and press tab when you get to the version number in the file name. ```bash chmod +x ~/Downloads/mcuxpressoide-xx.x.x_xxxx.x86_64.deb.bin ``` Now you can install MCUXpresso by executing the installer package, for which you again have to modify the filename to match the right version: ```bash sudo ~/Downloads/mcuxpressoide-xx.x.x_xxxx.x86_64.deb.bin ``` You might get asked to accept an agreement (use the arrow keys to select "Yes" and press enter). Then wait for the installation to finish. After everything is completed, you can find the MCUXpresso application through the launcher. Look for the blue icon with the "X", or search for "MCUXpresso". ## Building and installing the Kinetis K66 SDK The MCUXpresso IDE by default only contains SDK support for a few microcontrollers. You must install additional SDK packages for most micocontrollers. The Kinetis K66 that is found on the FMUK66 board is not available by default, so we will have to install its SDK package. Go to the MCUXpresso SDK Builder linked below. If you **click on "Select Development Board"** you will be taken to a page where you can select the Kinetis K66 microcontroller and put together an SDK package. You might need to **login** again to your NXP account. {% embed url="" %} You have to select the processor for which you want to build the SDK. The easiest is to use the search field. Just start typing **"MK66FN"** and select **"MK66FN2M0xxx18"** under processors. Then, **press the green "Build MCUXpresso SDK" button on the right**. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LY7bAebzqBNwUpovqra%2F-LY7dqyuk8m-xZ_tXlwS%2Fimage.png?alt=media\&token=4f82ca7b-da6d-4148-987c-13793e76985a) On the next page, select **Linux as the host operating system**, and make sure the toolchain / IDE selection is set to **"MCUXpresso"** (or "All toolchains" if you want to use the SDK also with other tools). You can leave the other settings at their default values, but feel free to include additional features if you want to. **Press the "Download SDK" button** when you are done. You might have to accept another agreement. The download should start immediately after that, but in some cases you might need to click on "Download SDK Archive". Download the SDK directly from your VM, or use the shared folder feature. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LY7bAebzqBNwUpovqra%2F-LY7eeeH79JaXX1czPiH%2Fimage.png?alt=media\&token=101a66f3-f655-4831-bcf5-d3dd60ff79ba) Now, start MCUXpresso within your VM. You can find it in Ubuntu's **launcher menu**. MCUXpresso will immediately ask at what location the **workspace** should be saved. You can chose your own directory, or leave the default as is. You can also create additional workspaces if you want. You will be greeted by a welcome screen. You can **close the "Welcome" tab** or **press the "IDE" button on the top right** to continue. Once you are in the main view of the IDE, find the location were you stored the Kinetis K66 SDK .zip file, and **drag the archive** into the area of the IDE window that says "Installed SDKs". It's usually located at the bottom. It will ask you to confirm that you want to import the SDK. Just press "OK". It might take a few seconds to install. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpYVXXJm9mLbKMDsa1L%2F-LpYVnQ_KFBy4qZMLjrO%2F30_VM_MCU_SDK.PNG?alt=media\&token=b7131a2d-bb66-4c62-aeeb-90185a8853fa) ## Create a new project for PX4 Now that MCUXpresso and the Kinetis K66 SDK are installed, we can continue and create a PX4 project. You can create a new project in MCUXpresso by going to **"File", "New", and then "Project"**. A list with different project types will appear, from which you should select **"Makefile Project with Existing Code"** under "C/C++". You can use any project name, but for clarity we will call it "HoverGames PX4". You should select `/home/hovergames/src/px4-firmware` as the **existing code location**. This is the folder where we cloned the PX4 firmware code. Make sure that both the C and C++ languages are selected. For "Toolchain for Indexer Settings", select **"NXP MCU Tools"**. Click "Finish" to create the project. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccIPJzTGHxQawC7FM%2F31_VM_MCU_Project.PNG?alt=media\&token=5216ded7-f2e4-4b05-ab7e-0b4e7dc80ffc) ## Project Properties Before we continue we should change some project properties. **Select the project** we just created on the left side of the screen, go to **"Project"** in the menu at the top and then select **"Properties"**. Go to **"MCU Settings"** under "C/C++ Build". An error *might* pop up, complaining about invalid values. If this happens you can close the error, switch to another tab and switch back again. You should now see the same screen as shown in the image below. On this "MCU Settings" screen, select the **MK66FN2M0xxx18** under the K6x family of MCUs. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccKjOAO42MbbfrMN-%2F32_VM_MCU_Projectsettings.PNG?alt=media\&token=a8ceb6db-cf2b-4479-8458-c92da55a19ac) Now go to the main "C/C++ Build" tab. Uncheck "Use default build command" and change the build command to just `make`. The PX4 build scripts will take care of the specifics, we should not supply any additional arguments here. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccOK8voGYJEZhHEfM%2F33_VM_MCU_Project_debug.PNG?alt=media\&token=08ccab4a-10d9-424a-92d4-33869ddd2c54) Then switch to the "Behavior" tab. Uncheck "Enable parallel build", because the PX4 build tools also already takes care of this. Set the "Build (incremental build)" target to `nxp_fmuk66-v3_default` and change the "Clean" target to `distclean`. Click "Apply" to apply all changed settings. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccQQOwbOemDTVwH_D%2F34_VM_MCU_Project_settings3.PNG?alt=media\&token=47a171a6-7f39-4c08-92d3-9a61359ac585) At the top of the window, you can press the button "Manage Configurations...". Create a new configuration named "Default", make it a copy of "Debug". Select the newly created configuration, and make it active using the "Set Active" button. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccSku_4jJQfvHADqu%2F35_VM_MCU_Project_settings4.PNG?alt=media\&token=4a24c083-b9a0-4f13-bea5-bcd6e598bd3a) You can press "Apply and Close" to apply the changes and close the window. In the properties window, make sure "Debug" is still selected as the profile of which you are editing. Now switch to the "Environment" tab under "C/C++ Build". Add a variable named "CFLAGS" with value `O0` (the capital letter O and a zero). Make sure you DO NOT select the checkbox to add the variable to all configurations. After you have done this, you can press "Apply and Close", we are done in this window. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccUxYwvhwlAWhqeuh%2F36_VM_MCU_Project_settings5.PNG?alt=media\&token=cb7ef693-0ce3-4f1b-9995-478046204fc9) ## Run Configurations At the top of the screen, you have a green "Run" icon. Click on the small arrow next to it, and select "Run Configurations...". In the window that opens, select "C/C++ Application" and click the "New" button above it. Name the newly created configuration "Upload", and change the "C/C++ Application" to `/usr/bin/make`. Also select "Disable auto build". ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LY7qul7a7mV1hecZj_x%2F-LY7raHz8YEXW9ThUAKn%2Fimage.png?alt=media\&token=d77a45fc-2a45-41d4-9646-0a8f2396f497) ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccYfWxSfYt4iLrqrr%2F38_VM_MCU_Runconfig2.PNG?alt=media\&token=633a9a9f-7322-48cf-beb9-7e98e5eb7528) Also go into the "Arguments" tab and add `nxp_fmuk66-v3_default upload` into "Program arguments". ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-LpccammFZS2CeEQXJRA%2F39_VM_MCU_Runconfig3.PNG?alt=media\&token=be329dbb-1ef8-4450-81e8-958bc24ab124) Finally, go into the "Common" tab. Tick the checkbox in front of "Run" under "DIsplay in favorites menu". Press apply and close the window. ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-Lpccf1H5vHcmjFvGtIP%2F40_VM_MCU_Runconfig4.PNG?alt=media\&token=8e80f9ce-02d2-4747-88c9-298fb3fe20f3) ## Debug Configurations Make sure you still have the right project selected on the left. Also make sure your J-Link debugger is plugged in and correctly passed through to your VM ([verify that you added the J-Link debugger in the USB tab of the VM settings](https://nxp.gitbook.io/hovergames/developerguide/tools/virtual-machine#virtual-machine-settings)). Now in the bottom left of your screen, in the quickstart panel, press the blue bug icon with the label "Debug". ![](https://2412084329-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9GLtaxrQtBdBRsFIJB%2F-LpccBTSw26T4R9hYmEg%2F-Lpcci_0HtRT5mLh8fL9%2F41_VM_MCU_Debugconfig.PNG?alt=media\&token=c94aa58d-144f-4435-869d-dd01efba3f2a) A new window opens and should show the attached J-Link debugger. Select it and press "OK". ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYRds_uVanWl5fphSqj%2F-LYRkii8HOjxJUNw6C5h%2Fimage.png?alt=media\&token=f53cdd8f-9bb9-44d1-8244-045e3d9ac578) In the next screen, you should make the "Name" column a bit wider and select "nxp\_fmuk66-v3\_default.elf". Then, press "OK". It might start building the code and start a debug session. Wait for it to finish (there is an indicator at the bottom), and then press the button in the top bar with the two red squares, to stop all debugging sessions. It might also give an error and stop by itself. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYRds_uVanWl5fphSqj%2F-LYRzi6VpPC3BBlEh9CQ%2Fimage.png?alt=media\&token=37d19a1e-da8e-4281-8dcc-d8f64a4efcaf) We first need to change the configuration. Click on the small arrow between the green debug icon and the green run button. Go to "Debug Configurations...". ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYQqoxt5TWXtl2F3udL%2F-LYQqq_mepZF7aZz8uUo%2Fimage.png?alt=media\&token=f5ec523d-95de-4736-911f-d5fb26ef7827) Under "GDB SEGGER Interface Debugging", select the generated JLink configuration. Rename it to "NXPCup PX4 JLink Debug". In this same screen, make sure "nxp\_fmuk66-v3\_default.elf" is selected in the field under "C/C++ Application". Then, under "Build Configuration", select "Debug" from the dropdown menu. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYS0nA22AfgPMTGji-P%2F-LYS2Ayw1QzNpnk5aMAw%2Fimage.png?alt=media\&token=f3ffea04-0917-4604-9057-a0fe3f2ba16e) Switch to the "Common" tab, and tick the checkbox in front of "Debug" under "Display in favorites menu". Press "Apply" and close the window. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYRds_uVanWl5fphSqj%2F-LYRf0nNb9v4x1ZXYw6W%2Fimage.png?alt=media\&token=be9a3353-c459-4be5-be6c-035fc0865702) ## ## Upload PX4 firmware to FMUK66 using USB If you want to do a clean build, press the clean button on the right side first. Then, click the hammer button to build to build the PX4 firmware for the FMUK66. You can check that the build configuration is set to "Default" by clicking on the dropdown menu next to the hammer icon. After you start the build process, the progress will be shown in the console at the bottom of the screen. You can upload the firmware with the green "run" icon (not to be confused with the "resume" icon that you can use during debugging). You can again check that you have the right run configuration selected by clicking on the dropdown menu next to the run icon. Keep in mind that the FMUK66 needs to be connected via USB for this to work! {% hint style="info" %} If this does not work, make sure you have the FMUK66 plugged in to your computer and that there are two FMUK66 devices "passed through" to the virtual machine. One for the bootloader, and one for "normal operation". Also make sure that the board actually has a [bootloader installed](https://nxp.gitbook.io/nxp-cup/developer-guide/development-tools/rddrone-fmuk66-development/commissioning-the-rddrone-fmuk66/programming-fmuk66-for-first-use#programming-the-bootloader). {% endhint %} ## Upload non-optimized firmware and start debugging session You can start debugging by clicking the green bug icon, or click on the small arrow to the right of it and select the "NXPCup PX4 JLink Debug" configuration. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYS6666ODV_Dr5g8fH0%2F-LYS6CUyrE1D6Q8PFLBu%2Fimage.png?alt=media\&token=8116a998-062c-48a6-b90f-65fa5f2480b9) You can stop all debug sessions with the button with the two red squares. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-L9GLtb-Tz_XaKbQu-Al%2F-LYS6666ODV_Dr5g8fH0%2F-LYS6S9h-2qlT4AhjEyv%2Fimage.png?alt=media\&token=4d0d130f-33be-4ad7-82ae-582e29b85650) ## Learn more about MCUXpresso Further [documentation](https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE?\&tab=Documentation_Tab) and [videos](https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE?tab=Design_Support_Tab) about MCUXpresso are available on the NXP website. You will probably have to login to access some files and videos. You can [create an account for free](https://www.nxp.com/webapp-signup/register). The "Advanced Debugging with MCUXpresso IDE" series provides a great introduction to the debugging tools in MCUXpresso. Most of the tools shown in these videos can be directly applied to debugging an FMUK66 board running PX4 Autopilot. **Advanced Debugging with MCUXpresso IDE** * [Part 1: Building Debugging and Direct Flashing](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-1-building-debugging-and-direct-flashing:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-1) * [Part 2: Accessing Data and Peripherals](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-2-accessing-data-and-peripherals:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-2) * [Part 3: Code & Data Breakpoints](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-3-code-data-breakpoints:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-3) * [Additional ](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-4-instruction-trace:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-4)[videos](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-5-freertos-task-aware-debug:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-5) are [available](https://www.nxp.com/design/training/advanced-debugging-with-mcuxpresso-ide-part-6-swo-trace:TIP-ADVANCED-DEBUG-MCUXPRESSO-IDE-6) in this series, but are outside the scope of the NXP Cup. [
](https://nxp.gitbook.io/hovergames/developerguide/tools/px4-toolchain) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nxp.gitbook.io/nxp-cup/2019-dfrobot-chassis-developer-guide/development-tools/rddrone-fmuk66-development/setting-up-mcuxpresso.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.