例MPC5744P SWT ロング・リセット GHS614 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *バージョン:1.0 * 日付: 2014 年 10 月 22 日 * 分類:一般ビジネス情報 * 概要:この例はSWTの機能を示しています * SWTタイムアウト時には、長いFCCUに信号を送りました * SWTタイムアウト時の機能リセット反応を設定 * FCCUはその後、RGMモジュールに信号を送り、これが長いトリガーになります *機能リセット。 ******************************************************************************** *テストHW:MPC57xx *マスクセット:1N65H *対象:internal_FLASH * Fsys:200MHz PLL、40MHz水晶リファレンス ******************************************************************************** 改訂履歴: 1.0 2014年10月22日 b21190(VLNA Peter) 初期バージョン 1.1 2015年3月24日 b21190(Vlna Peter) SWTロングリセットを追加 *******************************************************************************/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *バージョン:1.0 * 日付: 2014 年 10 月 22 日 * 分類:一般ビジネス情報 * 概要:この例はSWTの機能を示しています * SWTタイムアウト時には、長いFCCUに信号を送りました * SWTタイムアウト時の機能リセット反応を設定 * FCCUはその後、RGMモジュールに信号を送り、これが長いトリガーになります *機能リセット。 ******************************************************************************** *テストHW:MPC57xx *マスクセット:1N65H *対象:internal_FLASH * Fsys:200MHz PLL、40MHz水晶リファレンス ******************************************************************************** 改訂履歴: 1.0 2014年10月22日 b21190(VLNA Peter) 初期バージョン 1.1 2015年3月24日 b21190(Vlna Peter) SWTロングリセットを追加 *******************************************************************************/ 全般

IOH: Getting started with IOH in custom projects (LPCXpresso) Introduction This page gives more detailed information on how to use the IOH libraries in custom projects when using the LPCXpresso IDE. For more general information regarding using IOH libraries in custom project or for detailed instructions for Keil MDK and IAR EWARM, visit IOH: Getting started with IOH in custom projects. Ready-to-use examples can be found at the main I/O Handler page. Note: This guide assumes the IOH I2S library is to be added to a project, hence the 'I2S' references. For other IOH libraries, 'I2S' should be replaced with the library name. 1. Add the IOH library (libioh_*lpcxpresso.a) to the project The first step is to configure the LPCXpresso project to link against the IOH library. Open the project properties. Browse to 'Settings', then 'Libraries'. Add the library name (minus the 'lib' prefix) to the first box ('Libraries (-l)'), the library location to the second box ('Library search path (-L)'). 2. Add the path where the library's header file resides to the project’s include path The next step is to add the file location of the library's header file to the include path of the project. Still in the project properties, browse to 'Settings', then 'Includes'. Add the location to the 'Include paths (-I)' box. 3. #include the IOH header file in the source code of the application The IOH header file must be included in the source code of the project (e.g. main.c) by using the following preprocessor directive: #include "IOH_I2S.h" 4. Configure the linker to place the IOH related sections in the IOH SRAM All IOH parts have an SRAM region reserved for I/O Handler. When starting IOH, usually by calling the library's init() function, I/O Handler expects this memory region to be loaded with the IOH data provided by the IOH library. This means this data must be stored in Flash and copied to the IOH SRAM upon startup. A convenient way to do this, is by using scatter loading. With scatter loading, the linker and c-library are instructed to program certain data sections (IOH data) into Flash, and copy it to the specifed region (IOH SRAM) upon start up. This requires a linker script. When using LPCXpresso, this is taken care of automatically when selecting an IOH-enabled part and using the 'Manage Linker Script' option active 5. Enable the IOH SRAM (SRAM1) before C-library initialization The copying of data from the 'load region' to the 'execution region' when using scatter loading (explained above) is executed by the c-library just before main() gets called. It's important that both regions are enabled when the copying is initiated. After power-on, the IOH SRAM on the LPC11E/U37H is disabled (clock disabled in the SYSAHBCLKCTRL register), so it must be enabled before the scatter loading is initiated. The startup file included in LPCXpresso for IOH-enabled parts automatically enable the SRAM in time. 6. Interact with IOH via the library's API The final step is to interact from the application with IOH. This can be done through the library's API. Each library comes with an application note explaining how to use the library and what data structures and functions are available, and with one or more application examples showing how to use the library. This application note and application example provide an easy way to get started. They can be downloaded from the main I/O Handler page.

Session 5: Introduction to Drivers This video presentation is the fifth installment of the Essentials of MQX RTOS Application Development training course. In this session, you will be introduced to MQX driver architecture, how drivers are initialized and used, and walk through two very popular drivers - serial, and light-weight GPIO. This training was created by Embedded Access Inc., a Freescale sponsored training provider and proven partner. Session 5 Course Line Lab Outline Driver Architecture Block vs. Byte modes POSIX drivers Low level drivers Polled vs. Interrupt modes Driver Initialization I/O Subsystem (POSIX) Walkthrough of the Serial Driver Polled vs. Interrupt Walkthrough of the Light-weight GPIO Driver Lab Assignment Initializing GPIO Setting the functionality for the inputs Monitor the inputs Updating the user interface Configuring the outputs Controlling the outputs First, watch the video for Session 5: Introduction to Drivers​. Then, follow through with the interactive lab assignment below. SESSION 5: LAB ASSIGNMENT INTRODUCTION The lightweight GPIO (LWGPIO) driver is used for monitoring inputs and controlling inputs. Though the concept is quite straight forward there are a number of structures and functions you need to use with this driver. In part this is to keep your code easily portable should you change processors and in part because of the complexity of modern processors such as Kinetis. OBJECTIVE The objective of this lab is to implement the switch and LED functionality.This objective will be accomplished by: Adding code to the Input Task to poll inputs from switches On a change of state for one of the switches, sending a message to the health task who passes it on to the Display Task Adding code to the Display task to set the orange LED to reflect the state of sw1 and the yellow LED to reflect the state of sw2 Toggling the state of the green LED every second New functions/ structures you will use:      LWGPIO_STRUCT, LWGPIO_PIN_ID, lwgpio_init, lwgpio_set_functionality, lwgpio_set_attribute, lwgpio_get_value, lwgpio_set_value, lwgpio_toggle_value ASSIGNMENT INITIALIZING THE INPUTS We will be focusing on messages related to GPIO for the time being so to avoid confusing our results with extra messages we'll disable the messages from the Accel Task and the Temp Task. You can either comment out the sending of messages from these two tasks or after they print out a message to say that they've started permanently block the task. The job of the Input task is to monitor the inputs but so far the inputs have been simulated by periodically sending a place holder message. This can now be replaced by only sending a message when the state of either switch 1 or switch 2 on the K70 tower card changes state. If you recall, in the lab for another session we defined all of the message types in main.h in an enum. We added Input_Message as the message type from the Input Task but now that we'll have two types of messages, one for switch 1 (sw1) and one for switch 2 (sw2). Delete Input_Message from the list and add SW1_Message and SW2_Message. In the Input Task we'll need to declare a few variables of different structure types associated with LWGIO. At the top of the function where the variable declaration is done add variables sw1 and sw2 both of type LWGPIO_STRUCT. We also need to know the value of sw1 and sw2 so declare variables sw1_value and sw2_value of type LWGPIO_VALUE. Finally, to retain the previous value of each switch we'll need two more variables of type LWGPIO_VALUE called sw1_last_value and sw2_last_value. In order to use an I/O on the processor it has to first be initialized to define how you want to use it. In the initialization section of the Input_Task use the _lwgpio_init() function to initialize the input pin connected to sw1 and again to initialize the input pin associated with sw2. The ID for each pin is defined in the BSP for the card you are using, in this case twrk70f120m.h which can be found in the BSP_Files folder of the BSP project. Since these we are using these pins as inputs we can use an initialized value of LWGPIO_VALUE_NOCHANGE. We also have to set the functionality for each pin and _lwgpio_init() doesn't set the actual pin mux register, meaning that we haven't defined that the associated pins on the processor should actually be used as IO. Use the _lwgpio_set_functionality () function to define the associated pins as inputs. The defines for the different functionality options for the IO pins are defined in the same BSP file (towrk70f120m.h), ie BSP_SW1_MUX_GPIO is used to set pin D0 the internal signal for sw1 and BSP_SW1_MUX_GPIO associates pin E26 with the internal signal for sw2. Since the circuits on the tower board for the switches don't have pull up resistors you need to enable the internal pull up resistors using the lwgpio_set_attribute () function. MONITORING THE SWITCHES First thing to do in the endless loop of the Input Task is to read the value of the switches using the _lwgpio_get_value() function and store the result in sw1_value and sw2_value. If the read value is not the same as the previous value, it must have changed so this is when we send a message to the Health Task. Copy the code we had before for sending a message. Update the message type (either SW1_MESSAGE or SW2_MESSAGE) and instead of sending data of 0 like we did before we can send the switches value (sw1_value or sw2_value). We are detecting switch state changes by comparing the current value to the last value so now that we've detected a change the current value should be copied to the last value. If you haven't thought about this already we could get a false change of state detection on power up if sw1_last_value and sw2_last_value are not initialized. Since the read value will be a 1 when the switch is not pressed it would be a good idea to pre-initialize the last value to a 1 (LWGPIO_VALUE_HIGH). Change the time delay in the endless loop to 100 ms to make sure we catch every press of a switch. UPDATING THE DISPLAY Since we are now sending actual data in our messages it would be good to have the Display Task print out the switch state when an update is received. To do this update the printf in the Display Task to show this parameter as well which is being passed in the data field of our message. Compile and run the code. INITIALIZE THE LEDS As was done in the Input Task we will need to initialize the GPIOs that control the LEDs, but of course they will now be configured as outputs. In the Display Task declare a variable of type LWGPIO_STRUCT for each LED. Since we have 4 LEDs that we want to control it may be more convenient to use an array like this "LWGPIO_STRUCT leds[4];" We also need to keep track of the IDs (eg BSP_LED1) for each LED which are defined in the twrk70f120m.h file. If you using an array for the LWGPIO structures it would make sense to use an array for these as well. In the initialization section of Display Task we need to initialize the IO pins associated with the LEDs in a similar way to how it was done for the switches. However we now want to set the direction as being an output (LWGPIO_DIR_OUTPUT) and the initial value should be high with a value of high (LWGPIO_VALUE_HIGH) because we want the output of these pins to reflect the value of the corresponding switches and those are defaulted to high (remember the pull ups?). As was also done with the IO for the switches we need to set the functionality for the corresponding pins so they are configured as IO. You'll need the define from the BSP header file again (eg: BSP_LED1_MUX_GPIO) Since there are 4 LEDs to initialize you could consider using a for loop for the initialization to keep things cleaner. Compile and run the code. Our last requirement is to toggle the state of the green LED (LED2) every second. This can be accomplished with a 1000ms timeout to the msgq_receive()function in the Display Task. This function will return NULL when the timeout expires, otherwise it returns a pointer to the received message. Toggling an output can be done by keeping track of the current setting and using the lwgpio_set_value() function or more simply by using the lwgpio_toggle_value() function. Compile and run the code to verify that the switch processing still works and that the green LED is toggling. Need more help? The full source code for this lab can be found in the 'Lab Source Code' folder here​.

USB_TypeC_Portfolioプレゼンテーション(Tech Days Lyon & Strasboug - 2016年5月)......PDFファイル <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

AMF-AUT-T1944 - Design the Car of the Future: i.MX 8 Virtualization and Media Capabilities for Next Gen eCockpits The hottest topic in automotive design today is the concept of the eCockpit -- where all visual functions in the car are controlled across multiple screens and fully integrated for the driver’s convenience. The key technology that enables eCockpit to run on a single processor also offers new capabilities in industrial, embedded and consumer products such as drones, manufacturing HMI interfaces and smart displays. This class will cover the fundamental technologies and architectural techniques in the i.MX 8 processor which enables rich eCockpit functionality, how NXP has implemented the world’s most significant full chip virtualization capabilities in an ARM-based processor and breaks down the eCockpit demo from the Tech Lab. The hottest topic in automotive design today is the concept of the eCockpit -- where all visual functions in the car are controlled across multiple screens and fully integrated for the driver’s convenience. The key technology that enables eCockpit to run on a single processor also offers new capabilities in industrial, embedded and consumer products such as drones, manufacturing HMI interfaces and smart displays. This class will cover the fundamental technologies and architectural techniques in the i.MX 8 processor which enables rich eCockpit functionality, how NXP has implemented the world’s most significant full chip virtualization capabilities in an ARM-based processor and breaks down the eCockpit demo from the Tech Lab.

Explore NXP RF at IMS 2016: Highlights Watch the new NXP high power RF highlights from IMS 2016. With more than 50 years of technology development and innovation, NXP's new RF Power group enables our customers to develop cutting edge cellular infrastructure, industrial and commercial solutions. Catch the Wave! We hope to see you next year in Hawaii at IMS 2017!     Explore NXP RF at IMS 2016: Highlights - YouTube      NXP Recommends Digital Front End Processors Car radio Tuners Low Power TX/RX Discrete Transistors PLLs and Oscillators RF Mixers RF Power Transistors RF Amplifiers - Low / Medium Power Millimeter - Wave Solutions Control Circuits Low Power TX/RX ICs   For specific product on the RF portfolio per above, please click on this link: RF|NXP   Links to Video links Explore NXP RF at IMS 2016: Highlights Outdoor Small Cells for Cellular Infrastructure 4 New Cellular GaN Technology Doherty RF Power Transistors Wideband GaN Communications for Military Applications Different RF Low Power Devices, Different Line-Ups RF Powers Up Digital Front End Processor for Really Big Spaces Small Cell Doherty Evaluation Board: Richardson RFPD and NXP Smart Antenna Solutions for "Internet Everywhere" L-Band and S-Band Radar Devices for Aerospace Aerospace Communications with Highest Power LDMOS Narrowband Transistor Millimeter Wave Radar for Breakthrough Auto Designs Wayv Portable, Battery-Operated RF Cooking Appliance NXP’s 1500 W MRF1K50 RF Power Transistor Benchmark Small Cell Solution for MIMO Radios Industrial

DES-N2020 Mentor Graphics: ARM TrustZone – デバイスの安全性と安全性を高めるための使用方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPの新しい組み込みデバイスで複数のコアで実行されている複数のオペレーティングシステムを分離する際に、多くの人がハイパーバイザベースのソリューションを探しますが、より簡単なソリューションは見落とされがちです。このセッションでは、ARM TrustZoneについて、現在ARM Cortex Aファミリのデバイスに搭載されている技術ですが、ARMが他のバリアントにも導入している技術について説明します。Layerscape LS1021デバイスのセキュアゲートウェイや、i.MX6デュアルコアデバイス上の自動車インストルメントクラスターなど、いくつかのユースケースを紹介します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPの新しい組み込みデバイスで複数のコアで実行されている複数のオペレーティングシステムを分離する際に、多くの人がハイパーバイザベースのソリューションを探しますが、より簡単なソリューションは見落とされがちです。このセッションでは、ARM TrustZoneについて、現在ARM Cortex Aファミリのデバイスに搭載されている技術ですが、ARMが他のバリアントにも導入している技術について説明します。Layerscape LS1021デバイスのセキュアゲートウェイや、i.MX6デュアルコアデバイス上の自動車インストルメントクラスターなど、いくつかのユースケースを紹介します。 デザイン |ソフトウェア&サービス

HMB-N1758 GainSpan:NXPベースのIoT設計のためのワイヤレス接続が簡単に <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 組み込みシステム開発者は、デバイスにワイヤレス接続を追加することは「ブラックアート」であり、ハードウェアとソフトウェアのウィザードによってのみ実行されるのに適しているという印象をしばしば持っています。コネクテッドデバイスを構築する際に克服すべき課題の概要を説明します。GainSpanのウィザードにより、NXPベースのMCUにワイヤレス接続を簡単に追加できるようになった様子を、あらゆるマグルに適したタスクで紹介します。Kinetis SDK、i.MX アプリケーション・プロセッサ・プラットフォーム、LPCXpressoベースの開発ボードを使用したワイヤレス・コネクティビティのデモを行い、NXPマイコンを使用した組込み設計へのワイヤレス・コネクティビティの追加を困難にする、GainSpanの使いやすいWi-Fiモジュールとビルトイン・ネットワーキング・スタックおよびサービスの機能を紹介します。聴衆は、ワイヤレス接続を次のNXPベースの組み込み設計に統合するための知識とモチベーションを持ってセッションを終了します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 組み込みシステム開発者は、デバイスにワイヤレス接続を追加することは「ブラックアート」であり、ハードウェアとソフトウェアのウィザードによってのみ実行されるのに適しているという印象をしばしば持っています。コネクテッドデバイスを構築する際に克服すべき課題の概要を説明します。GainSpanのウィザードにより、NXPベースのMCUにワイヤレス接続を簡単に追加できるようになった様子を、あらゆるマグルに適したタスクで紹介します。Kinetis SDK、i.MX アプリケーション・プロセッサ・プラットフォーム、LPCXpressoベースの開発ボードを使用したワイヤレス・コネクティビティのデモを行い、NXPマイコンを使用した組込み設計へのワイヤレス・コネクティビティの追加を困難にする、GainSpanの使いやすいWi-Fiモジュールとビルトイン・ネットワーキング・スタックおよびサービスの機能を紹介します。聴衆は、ワイヤレス接続を次のNXPベースの組み込み設計に統合するための知識とモチベーションを持ってセッションを終了します。 スマートホーム&ビル

AUT-N1822 Battery Management Solutions for High Voltage, 48 V and 14 V Li-Ion Batteries The need to ensure electrical power availability is increasing. Batteries are spreading into automotive, electrical storage systems and uninterruptible power supplies. This session will present the benefits of NXP Battery Management Solutions for multiple battery architectures. Watch Video Presentation The need to ensure electrical power availability is increasing. Batteries are spreading into automotive, electrical storage systems and uninterruptible power supplies. This session will present the benefits of NXP Battery Management Solutions for multiple battery architectures. Watch Video Presentation Secure Connected & Automated Vehicles

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