Hey everyone! If you are looking for concise steps to create and apply a patch in a yocto build, this article will serve you well. The reference taken in this article is of iMX93EVK yocto build. For this exercise, we are modifying a lpspi dts file in the BSP and creating a patch file but you may apply the same steps to other files in the BSP as well. Step-1 Make changes to the dts file in your directory example - arch/arm64/boot/dts/freescale/imx93-11x11-evk-lpspi.dts Step-2 In your yocto build, go to the git folder  cd imx-yocto-bsp-home/build_11x11/tmp/work/imx93_11x11_lpddr4x_evk-poky-linux/linux-imx/6.1.36+gitAUTOINC+04b05c5527-r0/git Step-3 Execute 'git diff' to check the difference between your changes and the default ones    Check the status by executing 'git status'     Step-4 Execute 'git add <file>'  , 'git commit -m <message>', and 'git format-patch -1' to add a file and create a git format patch file for your changes.   copy the generated patch file to a location which yocto build look for the patches Example- My yocto build looks for the patch in various locations, one of them is this one :- sources/meta-imx/meta-bsp/recipes-kernel/linux/files, so after creating the directory 'files', we can move the patch file to this folder    Step-5 Edit the .bb file for linux recipes-kernel for example - Open  /home/nxg06361/imx-yocto-bsp-home/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_6.1.bb  for editing Append the patch file name to the SRC_URI variable     You can also verify that your patch has been successfully applied or not by doing 'git log'   Voila ! that's all you need to do in order to create and apply a git patch for your yocto build.

Since I want to use some settings of the provious project, I find there are two ways which both don't work. I select the "The LCD"  example project which locals in"\\\Freescale\CW MCU v10.3\MCU\CodeWarrior_Examples\Processor_Expert\Kinetis\TWR-K40X256\LCD". First gererate code,  build and run the project with success. Then I save the processor setting as template and add  it in a empty PE project from the "Component Library", Generate Processor Export code with error "Incorrect Tool Chain Select", I check the new project propeties and change the "Current toolchain" as "ARM  toolchain"  in correpondence with the previous project.  Regenerate the code , there still exit 9 errors in the _arm_start.cfile . Description Resource Path Location Type Undefined : "exit" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 287 C/C++ Problem Link failed. PE_use_template C/C++ Problem mingw32-make: *** [PE_use_template.elf] Error 1 PE_use_template C/C++ Problem Undefined : "__aeabi_unwind_cpp_pr1" PE_use_template line 0, external location: E:\CW_workspace\PE_use_template\RAM\Cpu_c.obj C/C++ Problem Undefined : "__call_static_initializers" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 251 C/C++ Problem Undefined : "__copy_rom_sections_to_ram" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 231 C/C++ Problem Undefined : "__init_registers" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 179 C/C++ Problem Undefined : "__init_user" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 257 C/C++ Problem Undefined : "memset" __arm_start.c /PE_use_template/Project_Settings/Startup_Code line 229 C/C++ Problem Second, when I use export "Component Setting"  there still exist the same problems. Can anyone give some hints or advice to this problem?:D

Step by step instructions for how to use Processor Expert inside CodeWarrior to create a bare board (no RTOS) application to use GPIO and Timers to blink LEDs on the TWR-K60N512 board, from scratch.

When you get a good answer, it is extremely helpful to everyone if you mark it as a correct answer. A hundred people may look at a hot topic, and when there is an answer, they can jump straight to it. So for everyone's benefit, when you get a good answer, mark it! It's part of being a good community member. As well, but much less importantly, one of the things we're going to measure is how quickly the community answers questions. But we're far more interested in people being able to find the right answer. So from time to time, if it looks like people forget to mark answers, we may go through and do it for you. But we aren't your mom. Help your colleagues, and mark the good answers. In fact, you know better than us what's right.

The whole idea of a community is sharing, and the component exchange is the focus for that. Processor Expert Software is all about reusable components. You can use the Component Development Environment to create complete components, typically as .upd files. You may package these up with documentation or other ancillary files in a zip file. You can use the PEx tools to export components or sets of components configured for particular hardware or use cases. Some components have dozens if not hundreds of properties, and preconfiguring them for particular situations can be extraordinarily useful, save a lot of work, and help someone avoid a lot of pain. You can export these as .pef files. You can save entire board configurations this way as .peb files. All of these - .upd, .pef, and .peb files are excellent contributions to the Component Exchange. We have created a category within the community for this purpose, and this purpose only. When you upload a component, categorize it as belonging in the Component Exchange category. Please limit items categorized this way to actual Processor Expert components (.upd, .pef, .peb files packaged up as you see fit). It's as easy as 1, 2, 3. 1: Upload a file 2: Describe, categorize, and tag it In the description, provide useful information - if there are architectural or distribution limitations for example. Remember, we reserve this category for the sole purpose of identifying components we share in the exchange. You can set tags to assist others who are searching. Other members can narrow their search by simply picking the Component Exchange category, and then search based on tags. It's that easy. 3: Publish it Click the publish button at the bottom, and you're done. Your contribution to the community is greatly appreciated. Note that all of the components can be rated and reviewed. PLEASE DO! The more we tell each other what's good, the better off we all are. THANKS!