MCUXpresso Training Hub

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

MCUXpresso Training Hub

ディスカッション

ソート順:
Installation The installation process is fairly simple when using the MCUXpresso Installer. The installer automates most of the installation process by installing the following dependencies: Python West CMake Ninja Kconfig Toolchain The MCUXpresso installer can be obtained from MCUXpresso Installer or the MCUXpresso for VS Code extension.  For users that prefer to complete the installation manually, the entire steps can be followed on the MCUXpresso SDK Documentation.   Obtaining the MCUXpresso SDK The SDK is entirely available on GitHub. To obtain the SDK, clone the manifest repository and initialize a west workspace. To do this, open a Command Line Interface(CLI) and run: west init -m https://github.com/nxp-mcuxpresso/mcuxsdk-manifests Once the west workspace has been initialized, update the west projects by running in your designated directory: west update   Exploring The MCUXpresso SDK Once the clone is complete in your designated directory, you will notice two distinct folders besides the .west folder.   The first is the manifests folder. This is the manifest repo which contains the manifest file to initialize and update the west workspace.     The second mcuxsdk folder contains the MCUXpresso SDK source code, examples, middleware integration and script files.     The SDK example projects are found in examples folder within the mcuxsdk folder. Here you will also find all of the other components included in the SDK such as drivers, middleware, and rtos folders.
記事全体を表示
MCUXpresso SDK The MCUXpresso SDK has been reengineered to make use of CMake and Kconfig.   CMake is a software build system that allows easier access and customization of projects obtained from the MCUXpresso SDK. The decision to use CMake was taken with the aim to improve consistency and readability across SDK examples. The MCUXpresso SDK is a comprehensive product including hundreds of boards and devices, thousands of components and examples, for all mainstream toolchains. The MCUXpresso CMake extensions aims to greatly reduce build data development and maintenance efforts. The image below shows the cmakelists.txt file for a sample project in the SDK.   Kconfig is a selection-based configuration system originally developed for the Linux kernel. In MCUXpresso SDK, Kconfig is used to configure the build in run time. This includes component selection with dependency resolve, component configuration with feature enable/disable and customization.    Follow this link for a quick overview exercise that demonstrates how to obtain the SDK and a brief overview on folder structure.
記事全体を表示
Documentation MCUXpresso SDK Documentation  This training currently covers the following areas: MCUXpresso SDK - Intro to CMake and Kconfig  MCUXpresso SDK - CMake and Kconfig: Getting Started MCUXpresso SDK: CMake Usage - Part I   MCUXpresso SDK: CMake Usage - Part II MCUXpresso SDK: CMake Usage - Build Options MCUXpresso SDK: Kconfig Usage MCUXpresso SDK: Kconfig - Exercise MCUXpresso SDK: GitHub + VS Code MCUXpresso SDK: Custom Manifests MCUXpresso SDK: CI/CD Pipelines  MCUXpresso SDK: Migration Guide - Archive SDK to MCUXpresso SDK 24.12 or Newer  MCUXpresso for VS Code: Importing Projects from the MCUXpresso SDK  MCUXpresso for VS Code: Using Kconfig GUI with MCUXpresso SDK Projects Using west explore from CLI to browse MCUXpresso SDK examples     
記事全体を表示
GOAL Learn how to import CMSIS packs into existing projects. In this particular project, CMSIS packs from Crank will be used alongside the freertos_hello example obtained from the MIMXRT1060-EVKB SDK. Note: This walkthrough was adapted from Crank Software's guide included with their CMSIS Pack.   ENVIRONMENT This guide requires MCUXpresso IDE v11.9.1 or latest. MIMXRT1060-EVK SDK version 2.16 or latest.   PROCEDURE 1. Import the freertos_hello example into the workspace. Be sure to set the library type to Newlib (semihost).     2. Rename the project to freertos_sbengine.     3. Add drivers to the project. Right click on the project and select SDK Management -> Manage SDK Components. NOTE: Select Keep Existing and do not replace the FreeRTOSConfig.h file when prompted after adding the following components: Under Drivers -> Device -> SDK Drivers, select: cache elcdif pxp Under Board Components -> Device -> SDK Drivers, select: ft5406_rt Under Software Components -> Device -> SDK Drivers, select: video-common     4. Add additional components to the project. Add the gt911 driver if required by your display. This driver can be found in the MIMXRT1060-EVKB SDK.   Navigate to components/gt911:   Copy the fsl_gt911.c and fsl_gt911.h into the touchpanel directory in the project:     Change the memory manager configuration from the default used by FreeRTOS.   Remove the heap_4.c from the project folder. This is found in freertos/freertos-kernel/portable/MemMang.   Add the heap_3.c into the project folder freertos/FreeRTOS/portable/MemMang. This file can be found in the MIMXRT1060-EVKB SDK.     5. Download the Crank Software pack from Arm Keil | CMSIS Packs.     6. Import the Crank Software pack into MCUXpresso IDE.       7. The Crank Software pack is a graphics bundle that contains six components: Board Display Memory Runtime Libraries Runtime Source Task For this walkthrough, we will add all the components except the Runtime Source component. This component is intended for custom changes. To add the components, right click on the project and select SDK Management -> Add Open-CMSIS Components: Once the components are selected press Ctrl + s to save the components in the project.   8. Resolve conflicts from the previous freertos_hello project configuration. The Board component from the Crank Software pack includes a rewrite of pin_mux.c. Navigate to the board directory of the project and remove the pin_mux.c and pin_mux.h files.   MCUXPresso will automatically add the libraries from the runtime engine into the linker settings. In the project settings remove all the Storyboard engine libraries and plugins. To do this, right click on the project and select Properties. Remove all of the items found under C/C++ Build -> Settings -> Miscellaneous -> Other Objects.   Switch from a managed linker configuration to using the linker file included in the CMSIS pack. In the project settings, navigate to the MCU Linker -> Managed Linker Script. Uncheck the Manage Linker Script option and change the Linker script and Script path. Linker script = MIMXRT1062xxxxx_flexspi_nor.ld Script path= ${cmsis_pack_root}/CrankSoftware/iMXRT10xx/8.1.0/configuration/rt1060/ Note: The path will vary depending on where the user saved the pack.   Copy sbengine_task_pxp_template.c and sbengine_plugins_template.h from the RTE -> Graphics folder into the source folder of the project. Rename these files to remove template  from the name. The project source folder should now look like this:   Exclude the sbengine_task_pxp_template.c and sbengine_plugins_template.h files in the RTE -> Graphics folder from the build.      9. Configure and export a Model C/C++ Header from Storyboard Designer. Create a new project and name it sbengine_model. For this example, I will use a display size of 480x272, color depth RGB 565, and Freetype font manager.   Once the model has been exported, add the header file to the source directory of the project.   Note: For more information about exporting models from Storyboard Designer visit: Crank Storyboard - Exporting and Running on your Embedded Target.     10. Integrating the Storyboard Engine requires modifications to the following: FreeRTOSConfig.h file Locate this file in the source folder of the project and make the following changes: #define configFRTOS_MEMORY_SCHEME 4 #define configUSE_TIME_SLICING 0 #define configENABLE_BACKWARD_COMPATIBILITY 0 #define configTICK_RATE_HZ ((TickType_t)200) #define configUSE_NEWLIB_REENTRANT 0 To this: #define configFRTOS_MEMORY_SCHEME 3 #define configUSE_TIME_SLICING 1 #define configENABLE_BACKWARD_COMPATIBILITY 1 #define configTICK_RATE_HZ ((TickType_t)1000) #define configUSE_NEWLIB_REENTRANT 1   Preprocessor Defines Right click on the project and select Properties -> C/C++ Build -> Settings -> MCU C Compiler. Add the following defines to the “Defined symbols (-D)” pane: SKIP_SYSCLK_INIT XIP_BOOT_HEADER_DCD_ENABLE=1 GRE_TARGET_OS_freertos GRE_TARGET_CPU_cortexm7 GRE_TARGET_TOOLCHAIN_mcuxpresso GRE_FEATURE_VFS_RESOURCES   Change the SDK_DEBUGCONSOLE define from: SDK_DEBUGCONSOLE=0 to SDK_DEBUGCONSOLE=1   If you are using the gt911 touch driver, you will also need to add the following preprocessor define: SDK_I2C_BASED_COMPONENT_USED=1   Library paths. Right click on the project and select Properties -> C/C++ Build -> Settings -> MCU Linker -> Libraries.   In the Library Search path (-L) pane add: "${cmsis_pack_root}/CrankSoftware/iMXRT10xx/8.1.0/storyboard/runtime/freertos-mcuxpresso-cortexm7-swrender-DFP-obj/lib" "${cmsis_pack_root}/CrankSoftware/iMXRT10xx/8.1.0/storyboard/runtime/freertos-mcuxpresso-cortexm7-swrender-DFP-obj/plugins” Note: The path will vary depending on where the user saved the pack. This guide uses the complete configuration of the engine. Therefore, all of the following libraries need to be added in the Libraries pane (-l).  gre greal sbimage sbvfs gre-plugin-animation gre-plugin-lua gre-plugin-poly gre-plugin-circle gre-plugin-timer gre-plugin-logger gre-plugin-screen-path gre-plugin-greio gre-plugin-sbimage-soil gre-plugin-fio_vfs render-plugin-swrender logging-util greio sblua soil swrmgr swrender font-plugin-freetype sbfreetype sbpng sbz   Note: The library order matters. Add the libraries in the order listed above and click Apply and Close     11. Recall that this project was originally the freertos_hello example from the SDK. Therefore, modifications need to be made to the freertos_hello.c file to support the changes for this application. Ensure that the following headers are included: #include "board.h" #include "peripherals.h"   The define for the hello_task_priority is no longer needed and can be removed.    Place the following definitions outside of the main function: void sbengine_main_task(void *argument); void sbengine_input_task(void *argument);   Add the following two additional functions to the initialization sequence in the main() function: BOARD_InitSemcPins() BOARD_InitBootPeripherals().   Replace the hello_task code: if (xTaskCreate(hello_task, "Hello_task", configMINIMAL_STACK_SIZE + 10, NULL, hello_task_PRIORITY, NULL) != pdPASS) with: if (xTaskCreate(sbengine_main_task, "sbengine", 8192, NULL, configMAX_PRIORITIES / 2, NULL) != pdPASS)   Add the Storyboard Input handling task creation code block before the call to VTaskStartScheduler: if (xTaskCreate(sbengine_input_task, "StoryboardInput", 2048, NULL, configMAX_PRIORITIES / 2, NULL) != pdPASS) { PRINTF("Task creation failed!.\r\n"); while (1); }       The source code should now look like this: /* FreeRTOS kernel includes. */   #include "FreeRTOS.h" #include "task.h" #include "queue.h" #include "timers.h"   /* Freescale includes. */ #include "fsl_device_registers.h" #include "fsl_debug_console.h" #include "pin_mux.h" #include "clock_config.h" #include "board.h" #include "peripherals.h"     /******************************************************************************* * Definitions ******************************************************************************/ void sbengine_main_task(void *argument);   void sbengine_input_task(void *argument);   /******************************************************************************* * Code ******************************************************************************/ /*! * @brief Application entry point. */ int main(void) { /* Init board hardware. */ BOARD_ConfigMPU(); BOARD_InitBootPins(); BOARD_InitSemcPins(); BOARD_InitBootPeripherals(); BOARD_InitBootClocks(); BOARD_InitDebugConsole();   if (xTaskCreate(sbengine_main_task, "sbengine", 8192, NULL, configMAX_PRIORITIES / 2, NULL) != pdPASS) { PRINTF("Task creation failed!.\r\n"); while (1) ; }   if(xTaskCreate(sbengine_input_task, "StoryboardInput", 2048, NULL, configMAX_PRIORITIES / 2, NULL) != pdPASS) { PRINTF("Task creation failed!.\r\n"); while(1); }   vTaskStartScheduler(); for (;;) ; }     NOTE: Check that the line: #include sbengine_model.h in the sbengine_task_pxp.c  file matches the name of the exported header file from Storyboard.   The project should now build:    
記事全体を表示
Documentation eIQ Machine Learning (ML) Software Development Environment Fact Sheet eIQ Toolkit User Guide-This link takes you to the eIQ web page on nxp.com. Once there, click on the Documentation tab or scroll down to the Documentation section   This training currently covers the following areas: Getting Started with eIQ Includes in depth guides on how to get started on i.MX Applications Processors and Microcontrollers FAQs
記事全体を表示
This guide covers: How to import example projects from standalone SDKs How to build, flash and debug How to use the serial monitor
記事全体を表示
The Application Code Hub (ACH) is a repository that contains software examples, code snippets, application software packs and demos developed by NXP experts. ACH provides filter and search options to quickly find specific applications. With the support of Git capabilities, there is an easy way to import and use applications within IDE and tool environments. The Application Code Hub is accessible directly from MCUXpresso for Visual Studio Code and MCUXpresso IDE.    MCUXpresso for Visual Studio Code To access the Application Code Hub, navigate to the QUICKSTART PANEL.     You can use the search bar and the filters to help you find a specific example for your application or hardware.     Once an example is selected the attached README file will open. This file will contain a description of the project as well as technical details.  To import the project, the name field will automatically populate with the example project's name. Designate a location to save the project and click the Import Project(s) button. After, confirm the project and the toolchain at the top of the window as prompted.     If you are prompted to associate a repository, navigate to the PROJECTS section and add the device's SDK to the project. To do this: right click on the project and select Configure > Associate Repository. A dropdown menu will appear on the screen. Select the device's SDK from there. See the Getting Started guide if you have not yet imported the SDK.     You can now build the project. Navigate to the PROJECTS section and click the build button. The project should build successfully.      MCUXpresso IDE To access the Application Code Hub, navigate to the QUICKSTART PANEL.     You'll notice that the UI is slightly different from MCUXpresso for VS Code. However, the search and filtering mechanisms are relatively similar.     To import an example project, simply click on GitHub Link and then the Next button. In the following window click Next to keep the default settings. After, select a destination to store the project and click Next. On the following window, select to import as an existing Eclipse project and click Next. Last verify the project and click Finish.     The project will be added to the Project Explorer view. To build simply select the project in the Project Explorer view and click build.  **Note** The build button can be found in the toolbar at the top, in the Quickstart Panel, or by right-clicking on the project.  
記事全体を表示
FreeMASTER User Guide  This document provides in-depth information about FreeMASTER'S features and usage.    
記事全体を表示
Visual Studio Code Documentation  This link leads to the documentation for Visual Studio Code. An overview of VS Code is provided as well as in-depth instructions for all its features.   MCUXpresso for VS Code Wiki  This is a link to the complete MCUXpresso for VS Code documentation. Installation as well as extension settings are covered. An overview of features is also provided.    
記事全体を表示
Open-CMSIS-Pack project  This is a link to the Open-CMSIS-Pack project website. This resource provides all the technical details behind CMSIS-Packs.   Working with Open-CMSIS-Packs  This is a link to documentation for MCUXpresso for VS Code that shows the user how to get started with Open-CMSIS-Packs.      
記事全体を表示
Documentation MCUXpresso for VS Code Documentation    This training currently covers the following areas: General Usage Getting Started - Step by step [video series] Getting Started - Installation and importing SDKs Importing Projects from the MCUXpresso SDK  Working with SDK examples Debugging with the RTOS DETAILS view  How to import a GUI Guider project to VS Code Reference Guides for specific hardware Getting started with MIMXrt1060-EVK Trustzone Examples on LPC55S6x Multicore Examples on LPC55S6x  SDRAM Examples on RT1060 AN14120: Debugging Cortex-M on i.MX 8M, i.MX 8ULP, and i.MX 93   Zephyr Zephyr: Getting Started in VS Code Zephyr: Hello World Zephyr: Kconfig Zephyr: Debug Zephyr: Devicetree  Zephyr: Revert Workspace Zephyr: Custom Board 
記事全体を表示
This getting started guide covers: Installation of the MCUXpresso for VS Code extension Dependency installations using the MCUXpresso Installler How to import SDKs
記事全体を表示
This guide covers: How to create a basic gui for your FreeMASTER project using Gui Guider Connection to FreeMASTER How to import FreeMASTER project file How sync the FreeMASTER project variables into a gui
記事全体を表示
This getting started guide covers: Preparation of project variables for visualization with FreeMASTER FreeMASTER communication with target Importing symbol files Adding variables to the FreeMASTER Variable Watch Creating visual components to visualize data for variables
記事全体を表示
Documentation FreeMASTER Documentation    This training currently covers the following areas: Getting started - Variables, communication with target, and project configuration Gui Guider integration   Other resources NXP Community - FreeMASTER 
記事全体を表示
This guide covers how to work with example projects obtained from an Open-CMSIS-Pack.
記事全体を表示
This video demonstrates how to quickly get started with Open-CMSIS-Packs  
記事全体を表示
Documentation Open-CMSIS-Packs Documentation    This training currently covers the following areas: Getting started - Installation and environment setup Build, Flash, and Debug Using partner packs - EmSA walkthrough Using partner packs - Crank Software walkthrough 
記事全体を表示