NXPのFRDMボード「FRDM-MCXA156」を使用して、モーター制御について分かりやすく解説していきます。基礎編と実践編に分かれていますので、興味のある内容から参考いただければ幸いです。

・基礎編①～⑦、実践編①～③

今回は実践編②として、ソフトウェアのセットアップから、実際にモータ制御のサンプル・コードを動かすまでをご紹介します。

NXPのFRDMボード「FRDM-MCXA156」を使用して、モーター制御について分かりやすく解説していきます。基礎編と実践編に分かれていますので、興味のある内容から参考いただければ幸いです。
・基礎編①～⑦、実践編①～③

今回は基礎編③として、NXPマイコンで、永久磁石同期モータの仕組みと制御方法について解説します。

NXPのFRDMボード「FRDM-MCXA156」を使用して、モーター制御について分かりやすく解説していきます。基礎編と実践編に分かれていますので、興味のある内容から参考いただければ幸いです。
・基礎編①～⑦、実践編①～③

今回は実践編①として、NXPマイコンで、実際にモータ制御を実施するための環境を準備していきたいと思います。

NXPのFRDMボード「FRDM-MCXA156」を使用して、モーター制御について分かりやすく解説していきます。基礎編と実践編に分かれていますので、興味のある内容から参考いただければ幸いです。
・基礎編①～⑦、実践編①～③

今回は基礎編②として、永久磁石モータの仕組みと制御方法について分かりやすく解説します。
(読了：5分)

NXPのFRDMボード「FRDM-MCXA156」を使用して、モーター制御について分かりやすく解説していきます。基礎編と実践編に分かれていますので、興味のある内容から参考いただければ幸いです。

・基礎編①～⑦、実践編①～③

今回は基礎編①として、NXPマイコンで、モータ制御を実施するための開発環境をご紹介します。

(読了：5分)

NXPのモーター制御に関わる記事をまとめたページです。

MCXマイコンをベースに、モーター制御の基礎から、実際の動かし方まで丁寧に解説しています。

是非、ブックマークを！

NXPのマイコン：MCXシリーズのソフトウェア開発にはMCUXpresso for VSC (Visual Studio Code)が無料で使えます．
またさまざまなMCUXpresso for Visual Studio Codeで使えるサンプル・コードも提供されており，動作検証だけでなく，さまざまなプロジェクトのベースにも使えます．

この記事を読めば，誰でも簡単にVSC開発環境&SDKをインストールできて，サンプル・コードまで動かすことができます！

組み込みデバイスの限られたリソースの中でLLMを使用するためには、RAGが必要となります。

本稿では、NXPの LLM ＋ RAG ソリューション 「eIQ GenAI Flow」についてハンズオン形式で紹介します。

こどもパソコンIchigoJamは，LPC1114で動作する最初のバージョンが2014年に登場以来，教育の場だけに留まらず，様々な応用が広がっています．
2024年にはオープンソース化．さらに2025年にはNXPの最新マイコン：MCXシリーズのMCX-A153に対応．現在，GitHubで公開されているこのコードをMCX-A153を搭載した評価基板：FRDM-MCXA153で動作させてみるまでを解説します．

I3C温度センサ：P3T1755をMCXマイコンで動作させるサンプルコードが，NXPアプリケーション・コード・ハブで公開されています．この記事では，このサンプルコードを動作させるための手順を紹介．
必要となる機材はMCXマイコンの評価基板：FRDM-MCXN947，またはFRDM-MCXA153．これらの評価基板上にはP3T1755を搭載しているので，そのままの状態でI3Cの動作を試せます．同サンプルコードではP3T1755の単体評価基板：P3T1755DP-ARDを接続しての動作評価も可能．複数のP3T1755を接続しての動的アドレス割り当てやIBI(In-band interrupt:インバンド割込)機能も試せます．

NXPの「MCX N947」マイコンをベースに、ハンズオン形式で、画像認識サンプルコードの実装を紹介します。

Step by step: load fusion fw to 8ulp flash

In this article, I'd like to share the steps to run fusion dsp fw in 8ulp, including all the issues I have encountered.

Pre-steps

To follow the steps, you will need:

• An 8ULP A1 EVK board
• 8ULP L5.15.52 image https://www.nxp.com/webapp/Download?colCode=L5.15.52_2.1.0_MX8ULP-BETA4&appType=license
• uboot and imx-mkimage
• SDK_2_12_1_EVK-MIMX8ULP_PRC4 - https://mcuxpresso.nxp.com/download/3b8a2df3ddcfce9bbe402722d28c85d9
• IAR IDE 9.30.1 - https://www.iar.com/
• Jlink V7.50 - https://www.segger.com/downloads/jlink/
• Access to Tensilica Tools - https://tensilicatools.com/download/i-mx-8ulp-fusion-dsp-sdk

The RT685-AUD-EVK allowed me to validate my custom frontend circuitry and get started on other critical DSP software development.  I was able to connect the piezoelectric saddle pickups on my engineering guitar into the test bed via the custom daughtercard. From here I can focus on firmware in the MCU and DSP cores in the RT685. 

Please find document which is missing in the latest SDK bundle location for RT devices \docs\wireless\Release Notes.

NXP's free UI design tool for the open source LVGL graphics library continues to add great new features and capabilities. GUI Guider 1.3.0 was released on January 24th 2022 and includes exciting new widgets, more host platform support, Keil project output and Micropython.

An interactive tutorial on how to create your own MATLAB Simulink temperature sensor application by applying the model-based design approach, how to configure and use the i.MXRT1060 EVK using NXP MCUXpresso, a thermistor module and the IMXRT Toolbox.

Please find attached a document detailing various features related to using the IMXRT1170-EVK(B) evaluation board with MCUXpresso IDE v11.x.x and SDK v2.x.x, including details of multicore debugging and how to enable SWO trace on this MCU.

Ázure RTOS ThreadX and other middleware components have now been released for i.MX RT1050/1060/1064 families. This highly optimized, safety-certified software can now be use for free in your projects.

There is a wiki page describing the way hot create the SCR entry for the SDK component here.

It is referenced from the MCUX SDK wiki space.

Feel free to put your comments and questions directly on the wiki page. 

The sdk data schema and validation has been merged to SDK dev branch and sync to SDK mainline.

The schemas are located in bin\generator\sdk_generator\data\sdk_data_schema.

Now the data validation will be the first and mandatory steps for most generator cmds run. For the time being, data record which violates the schemas will be reported as “warning”, because there are many warnings, generator won’t log them into screen but recorded in stage1 yml log. Please open the stage1 yml log fix the warnings.

New features update:

•  SDKGEN-1390The SDK yml data schema and validation task[In Progress]

The aim of this task is to provide a solution(schema + validation) for SDK data annotation and validation. It is an integral part of SDK generator solution.

We expect that with this all developers should be able to

• Figure out how to config yml data by referring schemas with some typical examples
• Read out the error log for wrong data record and fix them accordingly(Easily check and find out typos in data record).
• With correct data, there won’t be any “no xxx for nil class” related run abort.

New features update:

•  SDKGEN-1389Support Periodic Window Update feature for Keil

        Variables will update periodically if View – Periodic Window Update is selected when debugging. To enable or disable this option, a tag named "periodic_update" should be set in yml. Besides, a .uvoptx template file must be set, or this setting can not take effect.

davidjurajda‌:

Yes, it is mandatory. Because the internal SDK repository structure is not same as public package structure you have to support -r.  “-r” is basically transformation between internal repository and external package (file merging, changing folder structure). If you would like to produce public package you have to support also –production, which introduce strict testing.

Our MCUXpresso SDK is expanding to include more and more graphics examples, including LittleVGL and emWIN support for SPI-based LCDs. The examples we provide can be ported to different controllers, but are based/tested on a shield from Adafruit (product ID:1947) with an ILI9341 TFT controller and FT6206 cap touch controller. Adafruit have released different versions of this shield; early ones (marked as v2.3) work out of the box with NXP's boards, but later versions (that don't have a version number!) need a couple of simple modifications.

NXP provides MCUXpresso SDKs that are configured for use with our standard evaluation boards. These can be used when carrying out your initial evaluation of our MCUs and early development work. However, in most cases you will reach the point of having your own development or production board. This will mean modifying the pins, clocks and other configuration settings from the evaluation board originally used, generally using the MCUXpresso Config Tools, to match your own board. This will initially be done on a per-project basis.

Dear MCUXpresso user,

We have decided to remove “Configurations” page from MCUXpresso SDK Builder website (http://mcuxpresso.nxp.com) with the December update this year.

Details are summarized below about the existing Configurations page and how page’s functionality will replaced.

In March of 2017, NXP released the debut version of the MCUXpresso SDK along with an IDE and set of Config Tools under the same MCUXpresso name.  Since that time we have seen an amazing response from developers downloading and using this suite of software and tools.  The number of MCUXpresso SDK downloads recently surpassed 100,000 unique downloads.

As the NXP and former Freescale microcontrollers were unified under one company, we knew we needed to provide a consistent and efficient software development platform – one that would allow you  the flexibility to develop on a wide range on NXP microcontrollers without the need to relearn a new software architecture or re-invent basic enablement functionality.

In my previous articles I have used the command line on Linux to build and debug NXP MCUXpresso SDK applications. In this article I'm running code on NXP i.MX RT1064 in RAM or FLASH.

In “Tutorial: MCUXpresso SDK with Linux, Part 1: Installation and Build with Maked” I used cmake and make to build the SDK application. In this part I’m going to use the command line gdb to debug the application on the board.

I admit: my work laptop machine is running a Windows 10 OS by default. But this does not prevent me running Linux in a Virtual Machine (VM). Each host platform has its benefits, and I don’t feel biased to one or the other, but I have started using Ubuntu more and more, simply because I have worked more on Embedded Linux projects. While I have used mostly Windows with Eclipse for NXP LPC, Kinetis and i.MX platforms in the past, I started using Ubuntu too from last year with the NXP MCUXpresso SDK. I did not find much documentation about this on the web, so I thought it might be a good idea to write a tutorial about it. So here we go…