C07 NXQ1TXH5 Wireless Charging Demo NXQ1TXH5 One-Chip Qi Low Power Wireless Charging Transmitter     Demo Owner: Rick Dumont   The NXQ1TXH5 is a one-chip low power Qi transmitter, and it enables an ultra-low cost wireless charging transmitter dramatically reducing application cost while still providing latest WPC version 1.2 Qi compliant performance. The NXQ1TXH5 demo is provided in a small form-factor on which Qi enabled phones can be charged. The demonstration shows the extremely low component count, which is interesting for professionals to understand, and at the same time showing a real-life eye-catching form-factor that draws non-technically skilled person attention. The demonstration challenges people to actually charge their phone and experience charging without wires.   Features: Ultra low component count solution. Reducing application cost by 30-50% compared to other solutions Easy to layout on 2-sided PCB Excellent EMI behaviour without additional external filtering Ultra low standby power of 10 mW meeting 5-start smartphone charger standby rating High efficiency of 75% Excellent thermal behaviour due to NXPs proprietary low RDSon power silicon technology _________________________________________________________________________________________________________________________________________   Featured NXP Products: Product Link NXQ1TXH5: One-chip 5 V Qi wireless transmitter https://www.nxp.com/products/power-management/wireless-power/one-chip-5-v-qi-wireless-transmitter:NXQ1TXH5?&lang_cd=en NXQ1TXL5: Low-cost one-chip 5 V Qi wireless transmitter NXQ1TXL5: Low-cost one-chip 5 V Qi wireless transmitter | NXP  NXQ1TXH5 WPC 1.2 Qi-compliant wireless charger demo board NXQ1TXH5 WPC 1.2 Qi-compliant wireless charger demo board | NXP    _________________________________________________________________________________________________________________________________________     Mobile

Workshop_day3.jpg Check out some photos from last week Linux Embedded Programming Workshop. Check out some photos from last week Linux Embedded Programming Workshop.

FRDM-K82F FlexIO Camera Demo One of the new features that can be found on the FRDM-K82F is the FlexIO header. It’s be specifically designed to interface with the very cost-efficient OV7670 camera, and uses 8 FlexIO lines to read data from the camera. By using the FlexIO feature, it makes it easy to connect a camera to a Kinetis MCU. A demo is included with Kinetis SDK 1.3 which streams the video data from the camera to a host computer over USB. FlexIO: The FlexIO is a highly configurable module found on select Kinetis devices which provides a wide range of functionality including: • Emulation of a variety of serial/parallel communication protocols • Flexible 16-bit timers with support for a variety of trigger, reset, enable and disable conditions • Programmable logic blocks allowing the implementation of digital logic functions on-chip and configurable interaction of internal and external modules • Programmable state machine for offloading basic system control functions from CPU All with less overhead than software bit-banging, while allowing for more flexibility than dedicated IP. Running the Demo: First you’ll need to setup the hardware. An 18 pin header needs to be installed on the *back* of the board. The camera is oriented this way to allow for use of shields on the top, even if the camera is being used. This way the functionality could be extended with WiFi or LCD shields. After the header is soldered on, plug in the camera. It will look like the following when complete: Next we need to program the K82 device with the example firmware. The software can be found in the Kinetis SDK FRDM-K82F stand-alone release, in the C:\Freescale\KSDK_1.3.0_K82\examples\frdmk82f\demo_apps\usb\device\video\flexio_ov7670 folder. Open the project, compile, and program the example specific for your compiler like done for other examples. Make sure you also compile the USB Device library as well. After programming the K82, unplug the USB cable from J5 (OpenSDA) and plug it into J11 (K82 USB). The board will enumerate as a generic USB video device called “USB VIDEO DEMO”. You can then use this device with any video capture software, like Skype or Lync.  Here's a shot of the clock in my cube: The resolution is 160*120, the video image format is RGB565. You may need to manually adjust the focus by rotating the lens on the camera. The frame rate can also be sped up by modifying line 342 in usb_descriptor.c: 5fps: 0x80,0x84,0x1E,0x00, /* Default frame interval is 5fps */ 10fps:  0x40,0x42,0x0F,0x00, 15fps:  0x2A,0x2C,0x0A,0x00, 20fps:  0x20,0xA1,0x07,0x00, The 160*120 max resolution was determined by the amount internal SRAM of the device, as there is not external RAM on the FRDM-K82F board. More Information: One of many places to buy the OV7670 camera module​ OV7670 Reference Manual​ FlexIO Overview ​ FlexIO Training presented at FTF Freedom Development Platform Kinetis K Series MCUs Re: FRDM-K82F FlexIO Camera Demo Hello Anthony, Could you tell me if it's possible take a picture and identify some letters or numbers with this microcontroller? I need to take a picture, format in a valid format(like jpeg, bmp etc) and send that image from another interface, like uart etc.. Best regards Bruno. Re: FRDM-K82F FlexIO Camera Demo I got it working using GraphEdit Great demo, Anthony! Re: FRDM-K82F FlexIO Camera Demo Hello, thanks for sharing this great demo! I've soldered my OV7670 module in FRDM-K82F, builded the project and all the libs in KDS, flashed it to target and I can see the USB VIDEO DEMO device on my Window's device manager, but when I open Skype, It shows that it canot find a webcam.Seem that it tries to get frames from the USB VIDEO DEMO device, but as it don't get any, it shows this message: I tried it in 2 Windows machines (one with Windows 7 and other with Windows 10) Debugging a little bit more, I can see activity in PCLK, XCLK, HREF, VSYNC and data pins. The RESET pin is in 3.3V and the PWDN pin is in 1V ( I had to modify the software initialization to put it in 0V, as it was not initialized in the demo software). Seems that everything is correctly soldered. Do you know what can be wrong? Thank you!

ProjectsPresentation.pptx <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プロジェクトプレゼンテーションと採点ルール <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プロジェクトプレゼンテーションと採点ルール ワークショップファイル

IoT_2016.pptx IoT presentation IoT presentation Workshop Files

i.MX アプリケーション、プロセッサ、ロードマップ、およびカーインフォテインメントおよびネットワーキング向けアプリケーション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本セッションでは、車載アプリケーション向けの i.MX シリーズ製品について、ロードマップや生産機能などについて紹介します。また、サラウンドビュー、バーチャルクラスターなどの i.MX 車載ソリューションも含まれます。 2015年3月31日、鄭州で開催されたDwF MCU Solutionsで発表 セッションID: APF-ACC-T0990 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本セッションでは、車載アプリケーション向けの i.MX シリーズ製品について、ロードマップや生産機能などについて紹介します。また、サラウンドビュー、バーチャルクラスターなどの i.MX 車載ソリューションも含まれます。 2015年3月31日、鄭州で開催されたDwF MCU Solutionsで発表 セッションID: APF-ACC-T0990 i.MXアプリケーション・プロセッサ

安全嵌入式处理概述 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

KSDK SPI 主从控制器，带 FRDM-K64F <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 各位 Kinetis 爱好者，大家好！   飞思卡尔已经推出了Kinetis SDK ，我相信这对我们来说是一个很好的机会，可以利用这些驱动程序启动我们的新应用程序。这篇文章中包含的信息将向您展示如何根据简单的主从示例使用 SPI 驱动程序。   此处附加的示例是使用 KSDK 为KDS IDE开发的。要构建和运行示例，您可能需要考虑以下几点： 安装KSDK：您需要KSDK v1.1.0安装在您的机器上。您可以在此处找到它。 构建 KSDK 库并导入示例：在 KSDK 安装文件夹中，转到 doc 文件夹并查找 Kinetis SDK (KSDK) 入门文档。按照第5 节使用 Kinetis Design Studio IDE 运行演示的说明进行操作。了解如何构建和导入项目。 如果您还有其他问题，您可以在此帖子中找到有用的信息： OpenSDAv2 OpenSDA v2 的完整信息。 在 KDS3.0 中编写我的第一个 KSDK1.2 应用程序 - Hello World 和使用 GPIO 中断切换 LED，来自同事Carlos_Musich 的精彩帖子   我希望您能从这篇文章中受益。   如果您有任何疑问，请告诉我   如果这篇文章对您有用，请毫不犹豫地点击“赞”按钮。   顺祝商祺！ 阿德里安·桑切斯·卡诺 技术支持工程师   概述 回复：KSDK SPI 主从控制器与 FRDM-K64F <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，Adrian，这个样本非常有用。但是，我使用的是SDK3.0+KDSK1.2.0，无法声明‘configure_spi_pins’。KDSK1.1.0 和 KDSK1.1.0 有区别吗？和 KDSK1.2.0？包含哪个文件“configure_spi_pins”？ 非常感谢！ 回复：KSDK SPI 主从控制器与 FRDM-K64F <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，艾德里安 对于这个例子，我该如何操纵时钟相位的配置？ 谢谢 回复：KSDK SPI 主从控制器与 FRDM-K64F <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，Adrian， 很好的例子， 我对具有 SPI 通信的应用程序有疑问，需要在主模式下传输一个字节并接收 4 个字节，到目前为止我还没有遇到很多问题，但是当我获得字节时，我可以访问其中一个。我如何访问所有接收到的字节。 谢谢 回复：KSDK SPI 主从控制器与 FRDM-K64F <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，Adrian， 很好的样本。您是否有类似的示例程序，但 SPI-Slave 使用 DMA 传输而不仅仅是 IRS？ 谢谢！

Sub-GHz Protocol Sniffing with KW01 Using Test Tool 12. Sniffing is the process of capturing any information from the surrounding environment. In this process, addressing or any other information is ignored, and no interpretation is given to the received data. Freescale provides both means and hardware to create devices capable of performing this kind of operation. For example, a KW01 board can be easily turned into a Sub-GHz sniffer using Test Tool 12.2.0 which can be found at https://www.freescale.com/webapp/sps/download/license.jsp?colCode=TESTTOOL_SETUP&appType=file2&location=null&DOWNLOAD_ID=null After downloading and installing Test Tool 12.2.0 there are several easy steps to create your own sniffer for Sub-GHz bands. 1) How to download the sniffer image file onto KW01.      a) Connect KW01 to PC using the mini-usb cable      b) Connect the J-Link to the PC      c) Open Test Tool 12.2 and go to the Firmware Loaders tab      d) Select Kinetis Firmware Loader. A new tab will pop-up.      e) J-Link will appear under the J-Link devices tab.      f) Select the KW01Z128_Sniffer.srec file and press the upload button.     g) From the Development Board Option menu select KW01Z128.      h) Follow the on-screen instruction and unplug the board. Then plug it back in.      i) Close the Kinetis Firmware Loader tab and open the Protocol Analyzer Tab 2) How to use the Protocol Analyzer feature. Basics.     a) The Protocol Analyzer should automatically detect the KW01 sniffer. If not, close the tab, unplug the board, plug it back and re-open the tab. If this doesn’t work, try restarting Test Tool.     b) To start “sniffing” the desired channel, click the arrow down button from Devices: KW01 (COMx) Off and select the desired mode and channel.     c) The tab will change to ON meaning that KW01 will "sniff" on the specified channel. To select another channel, click the tab again and it will switch back to Off. Then select a new channel.      d) Regarding other configurations, please note that you can specify what decoding will be applied to the received data. Additional information: The sniffer image found in Test Tool is compiled for the 920-928MHz frequency band. Because of this, the present document will have attached to it two sniffer images, for the 863-870MHz and the 902-928MHz frequency bands. To upload a custom image perform the steps described at the beginning of this document, but instead of selecting a *.srec file from the list in Kinetis Firmware Loader click the Browse button and locate the file on disk. After selecting it, redo the steps for uploading an image file. A potential outcome: sometimes, if you load a different frequency band sniffer image, the Protocol Analyzer will display the previously used frequency band. To fix this, close Test Tool, re-open it and go to the Protocol Analyzer tab again. The new frequency band should be displayed. More information on this topic can be found in Test Tool User Guide (..\Freescale\Test Tool 12\Documentation\TTUG.pdf), under Chapter 5 (Protocol Analyzer, page 87). Thread Software Re: Sub-GHz Protocol Sniffing with KW01 Using Test Tool 12. I found this sniffering function support 802.15.4 MAC based. Do we support SMAC based ?

i.MX8MNano (m815S) DDRレジスタプログラミング支援 (RPA) これは、i.MX 8MNano (m815S) DDR初期化に関連するレジスタの詳細なプログラミング支援資料です。詳細については、mScale DDRツールのメインページをご参照ください。 https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8M-Family-DDR-Tool-Release/ta-p/1104467 このページは、RPAスプレッドシートの保存のみを目的としていることに注意してください。ご不明な点がございましたら、新しいコミュニティスレッドを作成してください。 Re: i.MX8MNano (m815S) DDRレジスタプログラミング支援 (RPA) こんにちは、@Rodrigueさん mScaleプロセッサでは、各周波数ポイントでトレーニングが実施されます。各周波数のキャリブレーション値を保持する個別のレジスタ・セットがあります。 このページの目的はRPAの保存に限定されることにご注意ください。RPAに関する今後の質問については、別のコミュニティ・スレッドを作成してください。 よろしくお願いいたします。 Jan Re: i.MX8MNano (m815S) DDR Register Programming Aid (RPA) こんにちは@jan_spurek 、 2番目の周波数ポイントに関して詳細を教えていただけますか？ DDRストレステストでは、これはどのように処理されますか？ 私が知る限り、このツールは一般的なDDRレジスタ設定のみを検証するため、確認するのは1つの周波数ポイント付近のキャリブレーションに限られます。 それとも、vTSAツールを使用して、低いバス周波数での設計をさらに検証するためにお手伝いが必要ですか？ お返事をよろしくお願いいたします。

MCX W Series Training MCX W series are secure, wireless MCUs designed to enable more compact, scalable and innovative designs for the next generation of smart and secure connected devices. The MCX W series, based on the Arm® Cortex®-M33, offers a unified range of pin-compatible multiprotocol wireless MCUs for Matter™, Thread®, Bluetooth® Low Energy and Zigbee®. MCX W enables interoperable and innovative smart home devices, building automation sensors and controls and smart energy products.   MCX W72 Hands on Training  FRDM-MCXW72: Hands-On pre-requisites This document is intended to guide you in the installation of the tools and let you know the material required for the FRDM-MCXW72 Hands On  FRDM-MCXW72: NBU and User Firmware Update Using ISP:   This hands-on describes how to update the code in NBU and the User firmware using the ISP. FRDM-MXCW72: Recognize NBU Incompatible Versions            The objective in this hands-on, is to learn how to recognize when the NBU firmware does not match with the SDK version. FRDM-MCXW72: Run Wireless UART IoT Toolbox Demo Goal of this lab is to show the SDK example implementing the wireless UART profile and we will move forward in making some meaningful modifications to the example itself with the goal to show where in the code the end user should enter the relevant application software for the application FRDM-MCXW72: Low Power Reference Desing SDK Demo          This hands-on describes how to run the Low Power Reference Design demo on FRDM-MCXW72. Two low-power reference design applications are provided in the SDK reference_design folder, these applications aim at providing: • A reference design application for low power/timing optimization on a Bluetooth Low Energy application. These can be used in first intent for porting a new application on low power. • A way for measuring the power consumption, wake-up time, and active time in various power modes. FRDM-MCXW72: Run Hello World SDK Demo           In this lab we will first import the MCUXpresso SDK for the MCX W72 Freedom board into MCUXpresso IDE and then we will build, flash and debug the hello world project to make sure the environment is set for the following Labs. FRDM-MCXW72: Run Blinky LED SDK Demo          In this lab we make some experience with the FRDM-MCXW72 board using the SDK project to implement a simple LED blinking. Once we will get familiar with the example project, we will integrate simple modifications FRDM-MCXW72 Channel Sounding board to board This hands-on guide offers an overview of the features and procedures for deploying and operating Bluetooth LE localization applications with Channel Sounding functionality on the NXP FRDM-MCXW72 hardware platform. FRDM-MCXW72 Channel Sounding FRDM to Phone Goal of this lab is to show the SDK example implementing the Bluetooth LE Ranging profile, how to flash it and run it, as well as looking into the code to extract meaningful information for applications that use ranging FRDM-MCXW72 Getting Started with Matter: This document is intended to guide you in the installation of the necessary tools and repository for start running Matter examples and development. FRDM-MCXW72 Getting Started with Zephyr: This document is intended to guide you in the installation of the necessary tools and repository for start running Zephyr examples and development. FRDM-MCXW72 Open NBU programming: Unlike MCXW 71 MCU, MCXW 72 supports an Open NBU. This means that NBU firmware source code is exposed to user. On MCXW 71 MCU, NBU firmware is NXP proprietary; it is not user customizable. MCX W72 Lifecycle and Debug Authentication: This MCXW72 training video talk about the Lifecycle state model, explain in detail the purpose, and security recommendations for each state.    MCX W23 Hands on Training  FRDM-MCXW23: LED Blinky In this lab we make some experience with the FRDM-MCXW23 board using the SDK project to implement a simple LED blinking. Once we will get familiar with the example project, we will integrate simple modifications. FRDM-MCXW23: Wireless UART IoT ToolBox the Goal of this lab is to show the SDK example implementing the wireless UART profile and we will move forward in making some meaningful modifications to the example itself with the goal to show where in the code the end user should enter the relevant application software for the application. FRDM-MCXW23: Hello World In this lab we will first import the MCUXpresso for Visual Studio Code SDK for the MCX W23 Freedom board into the MCUXpresso extension for Visual Studio Code and then we will build, flash and debug the hello world project to make sure the environment is set for the following Labs. FRDM-MCCXW23: Low Power Reference Design This hands-on describes how to run the Low Power Reference Design demo on FRDM-MCXW23. Two low-power reference design applications are provided in the reference design folder for the MCXW23: Low power peripheral application demonstrating the low power feature on an advertiser peripheral Bluetooth LE device. Low power central application demonstrating the low power feature on a scanner central Bluetooth LE device. Wireless Connectivity Trainings Bluetooth Low Energy  Introduction to Thread Network FRDM-MCXW23 FRDM-Training Hands-On Training MCU MCX W23 Wireless

HOWTO: GNU ビルドツールを使用して RAM メモリからライブラリ関数を実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このドキュメントでは、GNU ビルドツールを使用してカスタムメモリセクション（通常はRAM）からライブラリ関数を配置して実行するために必要な手順について説明しています。この手順は、どのGNUツールチェーンにも適用できます。S32 Design Studio for ARM で作成した新規S32DSプロジェクトでデモを行います。 標準ライブラリ（NewLib）のmemcpy()関数を実行したいと仮定しましょう。 1) 最初のステップは、特定のライブラリオブジェクトファイルを入力セクションから除外し（EXCLUDE_FILE を使用）、標準の.text*フラッシュセクションにリンクされないようにすることです。 EXCLUDE_FILEに関連付けられた入力セクションは、セクションリストの後半で使用される同じ入力セクションと干渉してはなりません（例：以下のリストから *(.text*) 入力セクションが削除されている場合）。EXCLUDE_FILEは *.(text*) ルールと同様に動作します。選択したファイルのみを除外し、残りの（除外されていない）入力データはすべて配置されます。 /* The program code and other data goes into internal flash */ .text : { . = ALIGN(4); *(.text) /* .text sections (code) */ /* Exclude file(s) from NewLib libc.a from .text.* section */ *(EXCLUDE_FILE (*libc.a:lib_a-memcpy-stub.o) .text*) *(.rodata) /* .rodata sections (constants, strings, etc.) */ *(.rodata*) /* .rodata* sections (constants, strings, etc.) */ *(.glue_7) /* glue arm to thumb code */ *(.glue_7t) /* glue thumb to arm code */ *(.eh_frame) KEEP (*(.init)) KEEP (*(.fini)) . = ALIGN(4); } > m_text‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 2)次に、 memcpyオブジェクトをプロジェクトの.ldファイルですでに定義されているcode_ramセクションに配置しましょう。このセクションは、RAM から実行されるコード専用です（起動ルーチンはこのセクションを初期化します）。詳細については、「HOWTO: S32 Design Studio で RAM からルーチンを実行する方法」をご覧ください。 次の行は、標準のNewLib（libc.a）に含まれるオブジェクトファイル（lib_a-memcpy-stub.o）のコード（.text* セクション）を配置します。 *libc.a:lib_a-memcpy-stub.o (.text*)‍ .code セクションに配置： .code : AT(__CODE_ROM) { . = ALIGN(4); __CODE_RAM = .; __code_start__ = .; /* Create a global symbol at code start. */ __code_ram_start__ = .; *(.code_ram) /* Custom section for storing code in RAM */ *libc.a:lib_a-memcpy-stub.o (.text*) /* add memcpy from the NewLib library here*/ . = ALIGN(4); __code_end__ = .; /* Define a global symbol at code end. */ __code_ram_end__ = .; } > m_data‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ プロジェクトをビルドした後、マップファイルをチェックして、memcpyが実際にRAMメモリの.codeセクションに配置されていることを確認できます。 .code 0x1fff881c 0x18 load address 0x00000d90 0x1fff881c . = ALIGN (0x4) 0x1fff881c __CODE_RAM = . 0x1fff881c __code_start__ = . 0x1fff881c __code_ram_start__ = . *(.code_ram) *libc.a:lib_a-memcpy-stub.o(.text*) .text.memcpy 0x1fff881c 0x16 C:/NXP/S32DS_ARM_v2018.R1/Cross_Tools/gcc-6.3-arm32-eabi/arm-none-eabi/newlib/lib/thumb/v7e-m\libc.a(lib_a-memcpy-stub.o) 0x1fff881c memcpy 0x1fff8834 . = ALIGN (0x4) *fill* 0x1fff8832 0x2 0x1fff8834 __code_end__ = . 0x1fff8834 __code_ram_end__ = . 0x00000da8 __CODE_END = (__CODE_ROM + (__code_end__ - __code_start__)) 0x00000da8 __CUSTOM_ROM = __CODE_END‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 注 関数をRAMに配置する場合は、その関数によって呼び出されるサブ関数（通常は別のオブジェクトファイルにあります）を追加することを常に検討してください。 CC++ ライブラリ コンパイラ・アセンブラ・リンカ

Adding a non-secure region in TF-M based in Zephyr on FRDM-RW612 Introduction Trusted Firmware-M (TF-M) divides memory into secure and non-secure regions. This guide explains how to add a custom non-secure flash region for data import purposes. This is useful for testing or extending TF-M functionality on platforms like FRDM-RW612. This guide is using el2go_import_blob on frdmrw612//ns as a base example. You may use any TFM based example.  Imported as a freestanding application using VSCode.  The initial two steps add a macro in order to easily add a #ifdef statement in the code in case you'd like to toggle the region on/off. TFM does not use the traditional Zephyr kConfig, so it is necessary to follow the steps to ensure the macro is defined correctly. If you want to add the region without the #if statement, skip steps 1-2. Make sure to remove #ifdef TFM_CUSTOM_DATA_IMPORT_REGION #endif from steps 3-5. 1. Enable the Feature via Configuration File: el2go_import_blob/Kconfig config TFM_CUSTOM_DATA_IMPORT_REGION bool "Enable custom flash area for testing" help Validate non-secure region in flash. File: el2go_import_blob/prj.conf CONFIG_TFM_CUSTOM_DATA_IMPORT_REGION=y 2. Update Build System to Pass the Flag File: el2go_import_blob/CMakeLists.txt Append the CMake option: if(CONFIG_TFM_CUSTOM_DATA_IMPORT_REGION) set_property(TARGET zephyr_property_target APPEND PROPERTY TFM_CMAKE_OPTIONS -DUSE_TFM_CUSTOM_DATA_IMPORT_REGION=ON ) endif() File: platform/ext/target/nxp/frdmrw612/config.cmake Add the flag: set(USE_TFM_CUSTOM_DATA_IMPORT_REGION OFF CACHE BOOL "") File: platform/ext/target/nxp/frdmrw612/CMakeLists.txt Add compile definition: if (USE_TFM_CUSTOM_DATA_IMPORT_REGION) set(TFM_CUSTOM_DATA_IMPORT_REGION_COMPILE_DEFINITION "TFM_CUSTOM_DATA_IMPORT_REGION") endif() target_compile_definitions(psa_interface INTERFACE ${TFM_CUSTOM_DATA_IMPORT_REGION_COMPILE_DEFINITION} ) 3. Define the Flash Region File: platform/ext/target/nxp/frdmrw612/partition/flash_layout.h Define address and size: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION #define TFM_CUSTOM_NS_REGION_ADDR (0x08500000) #define TFM_CUSTOM_NS_REGION_SIZE (0x00001000) // 4KB #endif File: platform/ext/target/nxp/frdmrw612/partition/region_defs.h Map the region: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION #define CUSTOM_NS_DATA_REGION_START (TFM_CUSTOM_NS_REGION_ADDR) #define CUSTOM_NS_DATA_REGION_SIZE (TFM_CUSTOM_NS_REGION_SIZE) #endif 4. Update Linker Script File: platform/ext/target/nxp/common/gcc/tfm_common_s.ld Add region base declaration: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION Load$$LR$$LR_CUSTOM_DATA_IMPORT_REGION$$Base = CUSTOM_NS_DATA_REGION_START; #endif 5. Declare and Initialize Region in Code File: platform/ext/target/nxp/common/target_cfg_common.h Add to memory region struct: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION uint32_t custom_ns_data_region_base; uint32_t custom_ns_data_region_limit; #endif File: platform/ext/target/nxp/common/tfm_hal_platform.c Initialize region limits: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION REGION_DECLARE(Load$$LR$$, LR_CUSTOM_DATA_IMPORT_REGION, $$Base); #endif // TFM_CUSTOM_DATA_IMPORT_REGION #ifdef TFM_CUSTOM_DATA_IMPORT_REGION .custom_ns_data_region_base = (uint32_t)&REGION_NAME(Load$$LR$$, LR_CUSTOM_DATA_IMPORT_REGION, $$Base), .custom_ns_data_region_limit = (uint32_t)&REGION_NAME(Load$$LR$$, LR_CUSTOM_DATA_IMPORT_REGION, $$Base) + CUSTOM_NS_DATA_REGION_SIZE - 1, #endif // TFM_CUSTOM_DATA_IMPORT_REGION File: platform/ext/target/nxp/common/tfm_hal_isolation.c Configure SAU: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION SECURE_WRITE_REGISTER(&(SAU->RNR), 7U); SAU->RBAR = (memory_regions.custom_ns_data_region_base & SAU_RBAR_BADDR_Msk); SAU->RLAR = (memory_regions.custom_ns_data_region_limit & SAU_RLAR_LADDR_Msk) | SAU_RLAR_ENABLE_Msk; #endif File: platform/ext/target/nxp/frdmrw612/target_cfg.c Configure MPC: #ifdef TFM_CUSTOM_DATA_IMPORT_REGION enable_mem_rule_for_partition(memory_regions.custom_ns_data_region_base, memory_regions.custom_ns_data_region_limit); #endif 6. Update Device Tree Overlay File: zephyr/samples/el2go_import_blob/frdm_rw612_rw612_ns.overlay Add partition: custom_ns_data: partition@500000 { label = "custom_ns_data"; reg = <0x500000 0x1000>; }; Let's test the region by erasing, writing and reading. 1. Enable the Zephyr flash File: el2go_import_blob/prj.conf CONFIG_FLASH=y 2. Add some test code to the main source file of the project.  #include const struct device *flash_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_flash_controller)); static int test_flash_region(void) { uint32_t offset = 0x500000; uint32_t test_data = 0xDEADBEEF; uint32_t read_data; // 1. Erase flash (required before write) flash_erase(flash_dev, offset, 4096); // 2. Write data flash_write(flash_dev, offset, &test_data, sizeof(test_data)); // 3. Read data (this can use memcpy function) memcpy(&read_data, (void *)0x08500000, sizeof(read_data)); if (read_data == test_data) { LOG("✓ Flash test passed with memcpy: 0x%08x\n", read_data); } else { LOG("✗ Flash test failed\n"); } //Flash read operation will have fix to correctly calculate address next release /*flash_read(flash_dev, offset, &read_data, sizeof(read_data)); if (read_data == test_data) { LOG("✓ Flash test passed with flash_read: 0x%08x\n", read_data); } else { LOG("✗ Flash test failed\n"); } */ return 0; } 3. Call the  test_flash_region() function from the main() .

<video> CHN L8 : S32G2 XRDC CHN L8 - S32G XRDC, by Danny(EN)/Peter(CHN) reference doc - AN13024: S32G2 Extended Resource Domain Controller (XRDC) – Application Note part 1 : XRDC Summary (view in My Videos) part 2 : XRDC MDAC (view in My Videos) part 3 : XRDC MRC and PAC (view in My Videos) part 4 : XRDC error handling (view in My Videos) part 5 : XRDC software enablement (view in My Videos) part 6 : XRDC wrap up questions (view in My Videos)

Q&A: Can i.MX6Solo LDB/LVDS & LCD Ports be active simultaneously Q: Some background; this instrument has one display connected to the LVDS output of the i.MX6Solo and the SVGA monitor is using the IPU port with an external Analog Devices ADV7125 DAC to actually drive the monitor (or projector).  From Tektronix: We got our kernel logo to show up on an external SVGA monitor as well as on the internal LVDS display so we now at least know that the hardware is functional. However, when our application starts running and writing to the fb0 (background) and fb1 (foreground/overlay) frame buffers, the external monitor (fb2 frame buffer) doesn't get updated. We need to know how to get the same data going to the external monitor as goes to the internal LVDS display.  the external monitor is 800x600 and the internal is 800x480 so we'd further like those 480 lines to show up centered in the 600 line monitor. We are also hoping that this can be down without having to write/DMA all of the data twice. The answer given is SR #1122663812 was "If the customer is using Linux, fb2 should also be drawed by their application."  This was considered in adequate and Tek replied: I would like to know if they are saying that the IPU absolutely cannot automatically do what we want and if not, why not?  I would like to have some detailed information to at least convince us that they've looked into this and it really isn't possible. A: In our Linux BSP we don't support such feature. And in android BSP it was already supported. The customer must draw the fb2 by their application, ipu doesn't have the feature that combining the fb0 and overlay fb1, then resize it to fb2 automatically. The customer application can drawing their UI into a memory, then use v4l2 output to draw this buffer to both fb0 and fb2, in this case, resizing will be implemented in V4l2 output driver with IPU hardware. And if the customer needs overlay on fb2, they must combine the two layer into memory with IPU task first, then using V4l2 output to render it to display fb2. For how to use IPU task, the customer can reference to BSP unit test code: imx-test-1.1.0\test\mxc_ipudev_test The summary: for dual display case, the fb0 and fb2 are just two framebuffer memory, they must be filled before rendering to display, on iMX6S/DL, only the fb0 has the hardware overlay (fb1); if the customer wants to show same contents on two displays in Linux, their application must draw the two framebuffers, but we had some hardware method to improve the performace, using GPU or IPU task. In Android, the application will not draw frame buffer directly, it will use Android surface flinger middleware to draw, so this feature was implemnted in surface flinger; but in Linux, there is no such middleware, and application draws the framebuffer directly, so the application should handle it. This document was generated from the following discussion: i.MX6Solo LDB/LVDS & LCD Ports Active Simultaneously

Lab Tutorial_TPM_Output Compare Find the complete material at: https://community.freescale.com/docs/DOC-95205 This video has been deleted (view in My Videos)

Length of connection line for Kinetis L series debugging and programming Recently, some customers have provided us with feedback stating they have been experiencing difficulties when connecting  Kinetis L series  microcontrollers using Multilink Universal probes, after checking the connection and software settings no obvious errors could be found. This recurrent problem has been confirmed by several customers, the  problem is caused by a long connection line. My suggestion is to keep connection line length to 10cm or less; otherwise, the IDE may not be able to establish the connection through the Multilink Universal. Kinetis L Series MCUs Re: Length of connection line for Kinetis L series debugging and programming Thank you! I was facing this problem days and had found no solution, in my case, I could eventually write the microcontroller in use and other times not. Now I made a cable 5 cm and not used the USB MULTIKINK connector and I'm getting program the microcontroller without problems. Microcotnrolador used: MKL15Z128VLH4

19-iMX_Serial_Download_Protocol.py <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 19-iMX_Serial_Download_Protocol.py zip ファイル <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 19-iMX_Serial_Download_Protocol.py zip ファイル

フリーダムボード --- Crystal / PLL搭載に関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 警告（WARNING） 「はじめに」ページに出くわした場合は、 FREEDOM BOARD / CORTEX M0 +はじめに 注意してください。 コースで多数の Freedom ボードを使用していると、Init Clock Routines が機能しないことが観察されました。フリーダムボードのクリスタルの*いくつか*は、「HIGH_GAIN」モードを好みません。 行を変更する pll_init(8000000、HIGH_GAIN、クリスタル、4、24、マクガウト); ～ pll_init(8000000、LOW_POWER、クリスタル、4、24、マクガウト); フリースケール・カップの内容 学生プロジェクト Re:フリーダムボード --- オンボードクリスタル/ PLLに関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> すべての場合において、R25は削除されました。 また、R25を2つのボードに実装してみましたが、それでも同じ結果(1M)が得られました。通常、*直列*抵抗は、ドライブレベルを制限するためにEXTALパスに配置されます。 Re:フリーダムボード --- オンボードクリスタル/ PLLに関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> これは、抵抗R25が大部分のボードにまだ実装されていないためであり、それを持っている人はこの問題を示していません。

congatec QMX6 Adeneo Embedded Solution Of The Month Adeneo's entry for solution of the month in collaboration with Congatec Adeneo's entry for solution of the month in collaboration with Congatec General