Expose the i3c device to the linux /dev directory   Some customers want to expose their i3c device on the /dev, In order to develop their i3c APP or operation the i3c device like I2C. But in our default BSP code, we do not support this feature for I3C device, This article will introduce how to make the i3c device expose to the user space. Board : i.MX 93 EVK BSP Version : lf-6.1.55-2.2.0 I3C device : LSM6DSOXTR Step 1 : Rework the i.MX93 EVK Board, Install the R1010.  Step 2 : Apply the add_i3c_device_to_dev.patch file to the linux kernel code              Command : git apply add_i3c_device_to_dev.patch Step 3 : Re-compile the kernel Image file.              Command : make imx_v8_defconfig                                  make Step 4 : Boot your board with "imx93-11x11-evk-i3c.dtb" file and see if you can see the I3C device on the /dev directory. Result : We can see the i3c device is appeared in /dev directory, The i2c-8 is an i2c device mounted to the i3c bus. The i3c is backward compatible with i2c device. It will simulate the I2C signal loading i2c device.               PS : You can also use the i2ctool detect i2c-8 device. As shown in the following picture: Note : If you need the patch file, Please contact me any time for free. Linux Re: Expose the i3c device to the linux /dev directory I am also interested for the patch. Re: Expose the i3c device to the linux /dev directory Hello, can you send me the patch file add_i3c_device_to_dev.patch?

示例 S32K144 CMP 窗口模式使用 PDB S32DS3.4RTM4.0.3 **************************************************************************************************************************** 详细描述： 示例展示了使用 S32 SDK API 实现 S32K1XXRM 的模拟比较器“45.7.5 窗口模式（#s 5A 和 5B）”。 比较器配置为将模拟输入 0（AIN0）与内部 DAC 产生的参考电压的一半进行比较。 PDB 用于生成脉冲输出，通过 TRGMUX 用作 CMP 块的采样窗口。PDB周期为5ms，前2.5ms WINDOW=1，后2.5ms WINDOW=0。 Pdb0PulseOut 不仅可以 TRGMUX 到 Cmp0Sample，还可以到 TrgmuxOut0，这样我们就可以在 TRGMUX_OUT0(PTA1) 引脚上观察 WINDOW。 根据来自 CMP0_IN0（1kHz 外部三角波）的输入，LED 按照以下规则亮起： 1) Vin < DAC 电压：红色亮，绿色灭 2）Vin > DAC电压：红色熄灭，绿色亮起 3）未知状态：红灯亮，绿灯亮 EVB连接： 信号功能引脚S32K144EVB-Q100 窗口 TRGMUX_OUT0 PTA1 J5.5 2.5ms 窗口=1 和 2.5ms 窗口=0 加输入 CMP0_IN0 PTA0 J5.7 需要接外部1khz三角波 COUTA CMP0_OUT PTE3 J1.16 方波 PTC1 PTC1 J5.13 如果没有外部三角波，则产生方波（PTC1）并输出到 CMP0（PTA1） * * ---------------------------------------------------------------------------------------------------------------------------------------- *测试硬件：S32K144EVB-Q100 * 微控制器：S32K144UAVLL 0N47T * 目标：Debug_FLASH *编译器：S32DS3.4 *SDK版本：S32SDK_S32K1XX_RTM_4.0.3 * 调试器：PEMicro OpenSDA * ---------------------------------------------------------------------------------------------------------------------------------------- 修订历史： 版本 日期 作者 变更描述 1.0 2023年11月9日 Robin Shen 初始版本，基于 cmp_dac_s32k144 和 pdb_periodic_interrupt_s32k144 ****************************************************************************************************************************

Video- Power management on i.MX6 Sabre SDP with WEC7 by iWave Systems Windows Embedded Compact 7 (WEC7) BSP customizations by iWave Systems for Freescale’s SABRE SDP/B platform now supports power management. Power management was successfully developed for the i.MX6 multicore platform and tested for the standard suspend and resume functionalities. The processor enters into dormant mode and consumes the least power. As of now, iWave has reduced it to consume as much power as it is currently uses in Linux and Android. i.MX6Q has four CPU cores. The suspend power state not only turns off 3 CPU cores, but also puts the primary CPU on low power mode. On resuming, all 4 cores restart successfully.The process of Power management is being intelligently handled in order to reduce the power consumption to a greater extent. The Power consumption in the idle mode is 800mA whereas in the deep sleep mode it is 380mA, which is very much lesser than in the idle mode. Power Management for multicore processors can be used in a wide variety of handheld devices like tablets, video cameras, mobile phones and other entertainment solutions.  http://www.youtube.com/watch?v=5vED0_U20Cc General

如何注册 CodeWarrior？~ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 那么，您是CodeWarrior的新手，不知道如何注册您获得的开发套件？这并不复杂，我会简单解释一下   您无需携带额外的信息或文件，只需携带您已经熟悉的信息，例如您的帐户用户名和密码、您购买的 CodeWarrior 套件以及可以在产品背面的标签上（以物理方式）或主页的“查看我的订单”部分（以数字方式）找到的产品 ID。   接下来的步骤基本上就是按照网页上的注册流程，提供产品信息并提交请求。   其中还有一部分过程需要在cmd中输入信息，但是不要慌！这只是定位和同步文件的问题，因此您在使用 IDE 时不会遇到任何复杂情况。   此视频可以向您展示完整的详细信息，并逐步指导您完成注册过程   本文档由以下讨论生成： 如何注册 CodeWarrior？~ 概述

EGLFS 上的 QT5 演示错误 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为了在 i.MX6 上运行 QT5 演示，您应该按照此链接上的说明进行操作： 为 i.MX6 构建 QT 该版本中的某些演示（例如 /examples/opengl/hellogl_es2）由一组出现在屏幕上的多个小部件组成。通常这些演示应该可以在 Wayland 或 X11 等窗口环境中正常运行。 在仅限 Linux 环境下，绘制到屏幕的插件称为 EGLFS。该插件有一个限制，即它在屏幕表面上一次仅支持一个小部件。那么诸如 hellogl_es2 之类的演示就*不打算*与该插件一起工作，而且它永远不会工作。 使用 EGLFS 时发现的错误包括： 这些问题可以在 Qt OpenGL 示例中看到。“hellogl_es2”和“2dpaint”似乎显示一个渲染帧然后中断—— “hellogl_es2”显示QT字和气泡，并且GUI被隐藏，而“2dpaint”仅显示没有标签的openGL版本。 看起来，当在表单上包含 QGLWidget 时，QGLWidget 可以正常工作，但表单的其余部分不会出现。我无法点击任何按钮或做任何事情。 除了这些问题之外，我还会在输出中看到一个或多个以下错误消息： * 此插件不支持setParent！ * 此插件不支持 propagateSizeHints() * 使用非 OpenGL 表面调用 QOpenGLContext::swapBuffers() 然而其他演示（例如 hellowindow）可以与 EGLFS 很好地配合，因为它们是单个小部件。此外，使用 qtquick 创建的所有演示都可以正常工作，因为所有可视化 QML 项目都使用场景图（一种低级、高性能渲染堆栈，与 OpenGL 紧密相关）呈现为单个小部件。这里有更好的解释： Qt5 QPainter vs. QML & Scene Graph。

A socket programming demo for MQX / RTCS (Socket.zip) A pair of TCP server & client and a pair UDP server & client are implemented to demo socket API in RTCS. It supports K60N512 and K70F120M on IAR EWARM 6.50 at this moment. You can port it to other boards and IDE easily. 1) Copy Freescale_MQX_4_0 folder and override the default MQX folder 2) RTCS Socket Example Guide.doc can be found in ..\Freescale_MQX_4_0\rtcs\examples\socket A pair of TCP server & client and a pair UDP server & client are implemented to demo socket API in RTCS. It supports K60N512 and K70F120M on IAR EWARM 6.50 at this moment. You can port it to other boards and IDE easily. 1) Copy Freescale_MQX_4_0 folder and override the default MQX folder 2) RTCS Socket Example Guide.doc can be found in ..\Freescale_MQX_4_0\rtcs\examples\socket Real-Time TCPIP Communications Suite Re: A socket programming demo for MQX / RTCS (Socket.zip) Thanks! I really(!) have missed this type of simple examples from Freescale. I adapted for my K60 tower. Was running directly.

Installing and Configuring QT Creator (Ubuntu) Qt Creator can be a very good IDE in order to develop great QT applications. This IDE does not only helps with syntax highlighting, access to examples and tutorials, but also helps you to configure different toolchains Qt binary versions and target options. First download the binary installer from: For 32 bits: $ wget http://releases.qt-project.org/qtcreator/2.6.2/qt-creator-linux-x86-opensource-2.6.2.bin For 64 bits: $ wget http://releases.qt-project.org/qtcreator/2.6.2/qt-creator-linux-x86_64-opensource-2.6.2.bin execute the binary $ ./qt-creator-linux-x86_64-opensource-2.6.2.bin Follow the Installer GUI and choose a location. Default options should be OK. in my case the installation was done here: $ /home/b35153/qtcreator-2.6.2/bin Open Qt Creator (in my case from command line, use "&" to regain control of the terminal) $./qtcreator & Open Tools -> Options Choose Build & Run  on the menu of the left. and Select the Compilers Tab Here you can add the toolchain GCC compiler of your convenience. It will appear in the "Manual"  section. Now click on Qt Version Tab.  Here you can add the Qmake that you had created with your Qt installation; for example, the Qt5 installation described here: Building QT for i.MX6 It will appear in the Manual section. In my case I have Qmake for PC and Qmake for i.MX6. Now click on Kits Tab Here you can create combinations of Compilers and Qmake, and also specify where do you want the executables to go. In my case here I combined the i.MX6 toolchain and the Qmake for I.MX6 i had created. I did not set up device configuration since the sysroot is already shared to my device via NFS, but you can configure it so the files are sent via ssh to your device. And that's It! Next time you load a project you can choose which Kit you want to work on, and it will be compiled just as you need. i.MX53 i.MX6_All Multimedia Re: Installing and Configuring QT Creator (Ubuntu) That's the link which I've already seen earlier Setup QT Creator with Yocto Build I already was a bit confused that the link has changed. Ok thank you, it's clear now for me. Re: Installing and Configuring QT Creator (Ubuntu) Have a look for this Setup QT Creator with Yocto Build  Re: Installing and Configuring QT Creator (Ubuntu) The links are working, but is still 2.8   Choose You need here: http://download.qt-project.org/official_releases/qtcreator/2.8/2.8.0/ Re: Installing and Configuring QT Creator (Ubuntu) Hi, I followed your instructions but already stumbled by downloading QTCreator. Seems like QT have changed the folder structure. Files can be found with bellow Links now. x86 http://download.qt-project.org/official_releases/qtcreator/2.6/2.6.2/qt-creator-linux-x86-opensource-2.6.2.bin x64 http://download.qt-project.org/official_releases/qtcreator/2.6/2.6.2/qt-creator-linux-x86_64-opensource-2.6.2.bin All other steps was working fine for me. Regards Re: Installing and Configuring QT Creator (Ubuntu) The examples are installed when you insstall   Qt5.   you can install Qt5 for the PC  to try the examples first from here Download Qt, the cross-platform application framework | Qt Project, and then compile Qt5 for i.MX  with the guide here in the community. https://community.freescale.com/docs/DOC-94066 If you install the version for PC (ubuntu linux)   you can find the examples at:  /Home/Qt/5.1.0/gcc_64/examples If you download and compile i.MX Qt5  you can find the examples at: /opt/qt5/examples Re: Installing and Configuring QT Creator (Ubuntu) Followed your instructions.  Program ran, but there are no examples.  Do you know where I can find them? Re: Installing and Configuring QT Creator (Ubuntu) Well I can give you a consulting service if you wish, otherwise you'll need to read the docs 😉 Re: Installing and Configuring QT Creator (Ubuntu) I'm sorry to say this but to follow these instructions is the sheer horror. You start with a tab in the browser and ends after a short time at 7 tabs open and completely lose track! Any guidance expects the exact execution of another instruction, which again presupposes the execution of another instruction. :smileyconfused: Re: Installing and Configuring QT Creator (Ubuntu) You should take a look in Yocto's documentatation: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-an-existing-toolchain-tarball" title="http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-an-existing-toolchain-tarball Re: Installing and Configuring QT Creator (Ubuntu) I do "bitbake meta-toolchain-qt" Results are joerg@ubuntu1204:~/yocto/rootfs_builder/build/tmp/deploy/images$ ls modules--3.0.35-r0-nitrogen6x-20130629065000.tgz    uImage--3.0.35-r0-nitrogen6x-20130629065000.bin README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt  uImage-nitrogen6x.bin uImage iḿ not sure what to do with that? Re: Installing and Configuring QT Creator (Ubuntu) meta-toolchain-qt Re: Installing and Configuring QT Creator (Ubuntu) Hello Otavio, QT4 should be good for me. I have to build a special image with yocto? Re: Installing and Configuring QT Creator (Ubuntu) Yocto currently is able to build a Qt toolchain for Qt4 but not yet for Qt5.     Re: Installing and Configuring QT Creator (Ubuntu) You need the qmake compiled for i.MX6 in order to create Qt5 programs that run in the i.MX6 processor. Otherwise you will create programs that run on the PC. I dont remember if the yocto build also creates this special qmake.  It should be in /opt/qt5/bin  or something similar Re: Installing and Configuring QT Creator (Ubuntu) Isn't it possible to set up QT Creator without building own make for I.MX6? It is really complicated to build it while using things building with ltib and ltib is horror !!! Qt is build on Yocto image. regards Joerg

[RT1170 Hardware Important] RT1170 HDUG important update NXP Updated the Hardware Development Guide for the MIMXRT1160/1170 Processor (MIMXRT1170HDUG) The main difference is： Updated capacitance value of VDDA_1P8_IN in Table 1 and Table 2 From 0.1uF to 1uF This will help improve the robustness of the circuit at low temperatures.

Embedded Image Processing - Color Segmentation on i.MX51 Freescale's ARM Processor General

[i.MX8MP/Linux 5.4.70.2.3.0]Display abnormal during HDMI hot-plug Platform: i.MX8MP EVK BSP: Linux 5.4.70.2.3.0 Customer reported UI on HDMI monitor is abnormal and has more line on left side when doing HDMI hot-plug on i.MX8MP running with L5.4.70.2.3.0. This issue can’t be reproduced on latest BSP such as 5.10 and above, several patch for HDMI from latest BSP can fix this issue. Graphics & Display

CTとMEXファイルのメカニズムと回避策を調査/MEX文件研究与RTD版本兼容性方案 症状 最近、互換性の問題は、特に異なるバージョンのRTDをサポートしている場合に厄介な問題であることがわかりました。 RTD SDKとプラグを取り外してインストールしますが、RTDを再インストールすると多くの時間がかかり、信頼性が低い場合があるため、完全な方法ではありません。 診断 CTとMEXファイルの仕組みを調査し、古いプロジェクトを新しいバージョンのRTDベースで実行できるようにするための回避策を見つけました。 解決策 すでにいくつかの参照コードとRTDの例でテストされていますが、機能します。ドキュメントが添付されています。

Investigated the mechanism of CT vs MEX file and workaround/MEX文件研究与RTD版本兼容性方案 Symptoms Recently found the compatibility issue is a troublesome problem especially when we are supporting different version of RTD. Remove/install the RTD SDK and plug, but it is not a perfect way because reinstall the RTD would cause a lot of time, sometimes it is unreliable. Diagnosis After investigated the mechanism of CT and MEX file, and found a work around to let the old project can be run in new version of RTD basis. Solution Already tested it with several reference code and examples of RTD, it can work. Attached is the document.

FreeMASTER 3.2 - リリースのお知らせ NXP FreeMASTERツールのバージョン3.2がオンラインで公開されました。 これは、新しい 3.2.x の最初のバージョンですリリースライン。以前の 3.x および 2.x バージョンと下位互換性があります (以前のリリース お知らせを参照)。最新バージョンでは、この記事で説明されている新機能とバグ修正が提供されます。 更新されたインストーラーは、ドキュメントやその他のリソースと共に http://www.nxp.com/freemaster で入手できます。   リリース説明 FreeMASTERは、NXPが開発および提供した強力なデータ視覚化ツールであり、ユーザーがNXPのターゲットで実行されている組み込みアプリケーションを監視および制御するのに役立ちます。エッジプロセッシングとオートモーティブの両方のビジネスラインのほぼすべてのNXP Arm ® Cortex-M®マイクロコントローラ、およびDSCおよびレガシーPower Architecture、ColdFire、HCS12/Zプラットフォームで動作します。ライセンス条件では、FreeMASTERを他のベンダーの許可されていないシステムで使用することは許可されていないことに注意してください。 バージョン 3.2.0 は、新しい 3.2.x の最初のバージョンですリリースライン。インストーラーは、システム内の古いインストールを置き換えるものではなく、バージョン 3.2 は古いバージョンと同時に共存する可能性があります。 バージョン 3.2 は、以前のすべてのバージョンと完全に下位互換性があり、ここで説明する新機能が追加されています。従来、組み込みアプリケーションのランタイム監視をサポートし、変数値の表示、オシロスコープのリアルタイムグラフ、高速トランジェントレコーダーグラフをサポートし、サードパーティアプリケーションへの接続を可能にします。このバージョンで導入された主要な新機能は、FreeMASTERのメインアプリケーションウィンドウに埋め込まれて実行されているダッシュボードやその他の制御アプリケーションをレンダリングするために使用できるMicrosoft Edge WebView2ブラウザコンポーネントのサポートです。 FreeMASTER内でアクティブなHTMLコンテンツをホストするには、合計で3つのオプションがあります。バージョン1.xおよび2.xで導入された従来のMicrosoft Internet Explorerコンポーネントです。バージョン 3.0 で導入された Chromium CEF コンポーネントと 新しい Microsoft Edge WebView2 コンポーネント。 新しいEdge WebView2もChromiumエンジンに基づいているため、FreeMASTERのJSON-RPCクライアントインターフェイスと完全に互換性があります。さらに、EdgeはCOM+ホストオブジェクトの埋め込みも部分的にサポートしており、「レガシー」なFreeMASTER ActiveXインターフェースにアクセスすることができます。このような汎用性により、もともとInternet Explorer用に作成された古いダッシュボードと制御ページを最新のブラウザフレームワークにスムーズに移行できます。Internet Explorer ブラウザおよび関連テクノロジは Microsoft によって段階的に廃止されており、IE ベースのアプリケーションは近い将来、適切に動作しなくなる可能性があることに注意してください。 詳細については、FreeMASTERのウェルカムページからアクセスできるIE移行のホワイトペーパーをお読みください。 FreeMASTERインストールパッケージの一部であるFreeMASTER Liteサービスは、WindowsおよびLinuxシステムの通信コアを提供します。FreeMASTERデスクトップアプリケーションと同様に、JSON-RPCインターフェースを介してアクセスできます。FreeMASTER Lite には、グラフィカル プログラミング用の一般的な Node-RED フレームワークも組み込まれており、FreeMASTER ツールの使用例が多数用意されています。Node-REDに関連する詳細については、専用のトレーニングビデオをご覧ください。 注:FreeMASTER Liteをインストールするには、アクティベーションコードを入力する必要があります。ライセンス情報ページの 「ライセンスキー 」タブで無料コードを入手してください。 FreeMASTER Node.js Installable Modulesは、'npm'パッケージマネージャーによって管理されるNode.jsアプリケーションでFreeMASTER JSON-RPCコンポーネントを便利に使用できるようにします。 新機能 主な新機能は、Microsoft Edge WebView2ブラウザコンポーネントのサポートであり、HTMLおよびJScriptコードの変更を最小限に抑えて、FreeMASTERで実行されている古いダッシュボードやその他のHTMLアプリケーションをInternet Explorerから最新のブラウザに移行するために使用できます。 さらに、ActiveX および JSON-RPC インターフェイスが新しいメソッドによって拡張され、スクリプト環境からプログラムによってプロジェクト コンテンツとプロジェクト オプションにアクセスできるようになりました。 リリース対象ユーザー FreeMASTERとFreeMASTER Liteはどちらも、主に、実行時にアプリケーションを監視および制御したい産業、IoT、および自動車分野のNXP組み込みアプリケーションのお客様、エンジニア、および開発者を対象としています。FreeMASTERは、インタラクティブなデモやユーザーインターフェースを作成するために使用できる強力なフレームワークでもあり、より幅広いターゲットオーディエンスが組み込みアプリケーションを使用するのに役立ちます。 前提条件 FreeMASTERツールはホストコンピュータ上で実行され、シリアル、CAN、イーサネット/WiFiネットワーク、JTAG、BDM、またはその他の物理インターフェースを使用してターゲットマイクロコントローラアプリケーションと通信します。マイクロコントローラ通信ドライバは、MCUXpresso SDK、S32 Design Studioの一部として、またはスタンドアロンのインストールパッケージとして利用できます。FreeMASTERツールを使用する前に、通信プロトコルとマイクロコントローラドライバAPIに慣れてください。 ライセンス契約の条項により、FreeMASTERの使用はNXPのマイクロプロセッサまたはマイクロコントローラを搭載したシステムに限定されます。 パッケージ FreeMASTERデスクトップアプリケーションと新しいFreeMASTER Liteサービスの両方を含む単一の自己解凍インストールパッケージがWindowsプラットフォームで利用できます。FreeMASTER Liteサービス付きのパッケージは、Linuxでも利用できます。 https://www.nxp.com/freemaster の FreeMASTER ホームページからインストールとドキュメントにアクセスします。

FreeMASTER 3.2 - Release Announcement Version 3.2 of the NXP FreeMASTER tool has just been published online.  This is the first version of the new 3.2.x release line. It is backward compatible with previous 3.x and 2.x versions (see previous release announcements). The latest version brings new features and bugfixes described in this article. The updated installer is available along with documentation and other resources at http://www.nxp.com/freemaster.   Release description FreeMASTER is a powerful data visualization tool developed and provided by NXP to help users monitor and control embedded applications running on NXP’s targets. It works with almost all NXP Arm ® Cortex®-M microcontrollers from both Edge Processing and Automotive business lines as well as with DSC and legacy Power Architecture, ColdFire and HCS12/Z platforms. Note that the license terms and conditions does not allow using FreeMASTER with non-authorized systems from other vendors. Version 3.2.0 is the first version of the new 3.2.x release line. The installer does not replace the older installations in the system, version 3.2 it may co-exist simultaneously with the older versions.  Version 3.2 is fully backward compatible with all previous versions and it adds new features described here. Traditionally, it supports runtime monitoring of embedded applications, displaying variable values, oscilloscope real time graphs, fast transient recorder graphs and enables connectivity to 3rd party applications. The major new feature introduced by this version is a support of Microsoft Edge WebView2 browser component which can be used to render dashboard and other control applications running embedded in the FreeMASTER main application window. In total, there are now three options of hosting the active HTML content inside the FreeMASTER: the legacy Microsoft Internet Explorer component introduced in versions 1.x and 2.x; Chromium CEF component introduced in version 3.0 and the new Microsoft Edge WebView2 component. The new Edge WebView2 is also based on a Chromium engine so it is fully compatible with the FreeMASTER's JSON-RPC client interface. Additionally the Edge also partially supports the COM+ host object embedding which enables to access the "legacy" FreeMASTER ActiveX interface. Such versatility enables a smooth migration path for old dashboards and control pages created originally for Internet Explorer into the modern browser framework. Note that the Internet Explorer browser and related technology is being phased out by Microsoft and the IE-based applications may no longer operate properly in near future. Please read more in the IE migration whitepaper accessible at the FreeMASTER Welcome page. FreeMASTER Lite service which is a part of the FreeMASTER installation package provides the communication core for Windows and Linux systems. It is accessible similarly as the FreeMASTER desktop application over the JSON-RPC interface. FreeMASTER Lite also embeds the popular Node-RED framework for graphical programming and provides many examples of use with the FreeMASTER tool. Find more information related to Node-RED in the dedicated training video.  Note: Installing FreeMASTER Lite will require you to enter an activation code. Get your free code on the License Keys tab at the license information page. FreeMASTER Node.js Installable Modules enable convenient use of the FreeMASTER JSON-RPC components in a Node.js applications managed by the ‘npm’ package manager. New Features The key new feature is a support of Microsoft Edge WebView2 browser component which can be used to migrate old dashboards and other HTML applications running in FreeMASTER from Internet Explorer to the modern browser with minimal changes in the HTML and JScript code. Additionally, the ActiveX and JSON-RPC interface has been extended by new methods enabling to access project content and project options programmatically from a script environment. Release target audience Both FreeMASTER and FreeMASTER Lite are primarily targeted to our customers, engineers and developers of NXP embedded applications from Industrial, IoT and Automotive areas who want to monitor and control their applications at runtime. FreeMASTER is also a strong framework which can be used to create interactive demos and user interfaces helping to use the embedded applications by yet wider target audience. Prerequisites FreeMASTER tools run on the host computer and communicate with the target microcontroller application using Serial, CAN, Ethernet/WiFi network, JTAG, BDM or other physical interface. The microcontroller communication drivers are available as part of MCUXpresso SDK, S32 Design Studio or as a standalone installation package. Get familiar with the communication protocol and the microcontroller driver API before using the FreeMASTER tool. License terms and conditions permit use of FreeMASTER solely with systems based on NXP microprocessor or microcontroller systems. Packages A single self-extracting installation package which contains both FreeMASTER desktop application and the new FreeMASTER Lite service is available for Windows platforms. A package with the FreeMASTER Lite service is also available for Linux. Access the installation and documentation at the FreeMASTER home page at https://www.nxp.com/freemaster.

Fast boot for lx2160 in adas FAST BOOT FOR lx2160 IN adas •Objective To speed ​​​​up bringup of LX2 chip-based systems •Pain Points to Address The bringup time is much longer than 3s, which is very sensitive in ADAS systems or time-sensitive systems. •Value Proposition / Key Features The guide can help customers shorten uboot time from 5s to less than 1.5s, saving more than 70% bootup time. •Deliverables Demo based on LX2160ARDB board. Reference codes and patches. Guide for Fast boot document. Fast boot 广泛用于嵌入式设备，现以lx2160ardb板为例进行相关探索。 启动流程： 优化思路： 1.适当提高FSPI时钟速率 diff --git a/lx2160asi/flexspi_divisor_32.rcw b/lx2160asi/flexspi_divisor_32.rcw index 422139c..0f8d5c9 100644 --- a/lx2160asi/flexspi_divisor_32.rcw +++ b/lx2160asi/flexspi_divisor_32.rcw @@ -7,8 +7,10 @@ * Modify FlexSPICR1 register, to increase FlexSPI clock closer to 50MHz, * with divisor value as 32. * => 750 * 2 / 32 ==> 46.875MHz + *write 0x1e00900,0x00000013 + * 0f -12 =125M */ .pbi -write 0x1e00900,0x00000013 +write 0x1e00900,0x0f .end ​ 2.关键路径优化 固化spd参数 固化ddrc参数 BL33 裁剪 详细patch和测试结果参考附件。 Automotive Communications Infrastructure Technologies

QT demo on Freescale i.MX51 EVK General Re: QT demo on Freescale i.MX51 EVK Congratulations, but a bit of documentation would go a long way. ltib version? qt version? how to(s) would really be appreciated!

Freescaleのi.Mx6q Sabre SDでのOpenGLアプリケーションの高速ブート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Adeneo Embeddedのエンジニアの能力は次のとおりです。 Freescaleのi.Mx6q Sabre SDでのOpenGLアプリケーションの高速ブート (マイビデオで視聴)

How to enable the Debug (print) Viewer in Keil uVision4 IDE console It took me a while, plus a few contradicting and confusing answers from ARM support until I managed to make this work. Therefore, I do want to share with you the easiest method in order to save you some precious time (tested with MQX 4.0): 1. Make sure to install keil's TAD plugin during the MQX installation (it can also be installed separately from MQX\tools\keil_extensions\uVision4). 2. Make the following changes in the MQX configuration file "user_config.h": #define BSPCFG_ENABLE_IODEBUG   1 #define BSP_DEFAULT_IO_CHANNEL  "iodebug:" 3. Rebuild BSP debug library. 4. Configure Debugger as detailed in your MQX release documentation, which can be found in the following folder: MQX\doc\tools\uv4\MQX-uVision4-Getting-Started.pdf That's it, you're good to go - now you can see printf's using your uVision4 IDE console!

TWR-TFC-K20 Kinetis K20 Freescale Cup Tower Card Overview: The TWR-TFC-K20  is an all-in-one tower CPU card that can be used to create an autonomous race vehicle for the the Freescale Cup.   It has all the interfaces necessary for the car to sense the track and control the vehicle    This card is also a great platform for teaching embedded systems.   The TWR-TFC-K20 uses a Freescale Kinetis K20 MCU and has some really cool I/O to keep students interested. Features: Servo Outputs 3-pin Header to connector directly to steering Servo 1 Extra Servo header. Camera Interfaces 1. 5-pin header to connect directly to a Freescale Line Scan Camera 2. Header for 2nd linescan camera (optional) 3. RCA Camera Interface. Includes an LMH1981 Sync Extraction chip and connection to MCU to allow for low resolution (64x64) image capture at 60FPS Power Accepts direct battery power – onboard switching regulator 5-18v All circuitry except for motor controller can be optionally powered over USB Connector DC Motor Drivers QTY 2 MC33887APVW : Dual, Independent 5A Motor Driving Circuit. Supports forward, reverse and braking. Independent control over each drive motor allows for an active differential implementation Current Feedback to MCU ADC to allow for closed loop torque control CPU/ Programming Integrated Kinetis MK20DN512ZVLL10MCU with OSJTAG Additional I/O Some basic I/O for debugging. 4-poistion DIP Switch + 4 LEDs + 2 pushbuttons. Inputs for Tach Signal/Speed Sensor Design Files Rev Beta [B] (Current Production version) Schematics, Assembly Prints, BOM, etc. - Includes 3d view Rev B Errata: None known! Example Code: All software relating to the TWR-TFC-K20 is held in an Google Code Subversion repository.   This is the only way the source is distributed.   Never used a version control system yet?   Now is the time to learn (Google is your friend)!   All "real" software development processes use some form of version control.  TortoiseSVN is a nice client for SVN! Google Code Repository: https://code.google.com/p/tfc-twr/ This code works with Rev B of the board. All major interfaces & peripherals have been tested. At some point we will make a video going through the code. By default, the Linescan camera code is enabled. The code in main.c is pretty easy to follow. There is also code for the NTSC camera but must enabled in the TFC_Config.h file via a pre-processor directive. There is also code used for the OSTAG interface, Labview demo applications and drivers for the USB Videos: Freescale Cup Content

Route the ACOMP output and CTimer0 Cap0 input to the same pin via SWM For the LPC8xx family, the peripheral module input or output signals are not connected to external pads fixedly as most processor does . With SWM module, the peripheral module input or output signals can be routed to any external GPIO pins via software configuration There is special requirement that one peripheral output signal functions as the input signal of another peripheral, in the case, the peripheral output signal and the peripheral input signal can be routed to the same pad via SWM so that the input and output signals are connected internally without external cable. The LPC802 has ACOMP module, CTimer module and SWM module, per customer requirement, the ACOMP output signal and CTimer0 capture 0 input signal can be routed to the same GPIO pin without external connection so that the ACOMP output signal can trigger CTimer0 capture 0 event internally. In the doc, I give the code to configure the CTimer, ACOMP and the SWM, explain the configuration,introduce the tools, board and result. LPC800 Peripherals