Compiling MQX Libraries and Demos for the KDS Toolchain. Introduction Official support for MQX in KDS is slated for August of this year (2014), but what if you want to start building up your libraries now? Through Mingw and the files included in MQX 4.1, we can compile libraries and programs using KDS’ gcc_arm compiler. This is essentially a modification of the process used to compile MQX on a generic gcc_arm compiler. Original documentation can be found in: \doc\tools\gnu\MQX_GNU_Getting_Started.pdf I will try to explain a bit more of the setup process and the file changes that must be made to correctly compile, along with debugging your executable in processor expert. This guide is written for Windows and a version of the guide including a few screenshots of important screens is attached. Setup You will need: Mingw installed, along with mingsys-SED. This can be found at http://sourceforge.net/projects/mingw/ Make sure ‘c:\MinGW\bin’ has been added to system ‘PATH’ variable SED is part of a cmd improvement suite called mingsys. You can install the whole suite, but we only need SED KDS installed A suitable text editor that allows find and replace of text in all files of a selected directory. I recommend Notepad++ and it is what I will use in the tutorial. MQX file changes The original makefiles and batch scripts were created for gcc_arm v4.7.4, but KDS 1.0.1 is using 4.8.0. This means some directory paths have changed and these changes must be updated within MQX’s files. First, let us define the toolchain for the builder to use, in \build\common\make\global.mak, modify the following definition: ifeq ($(TOOL),gcc_arm)      TOOLCHAIN_ROOTDIR = \toolchain Endif Next we need to update the directory listings for gcc_arm components within its root directory. This comes down to replacing all instances of “/4.7.4/” with “/4.8.0/” in all ‘gcc_arm.mak’ files (you could choose to only edit the .mak files of boards you intend to use,  but it’s just as easy to replace all instances). In notepad++, this is simple process of running a “Find in Files”. The files themselves will be located in directories associated with building mqx for each platform: \mqx\build\make\ \tools\gcc_arm.mak Along with some entries within application builds: \mqx\examples\ \build\make\ _ \tools\gcc_arm.mak Lastly, specifically for demo application builds, there is one more directory change and one exclusion to make: remove ‘armv7e-m/’ from directory paths and comment out ‘libnosys.a’ (I must clarify I don’t understand the importance of libnosys and couldn’t find a suitable replacement with KDS’ gcc_arm toolchain. I have build hello2 successfully without it, but maybe other projects will require it) Again, this is a simple ‘Find in Files’, replacing “armv7e-m/” with no characters, then replacing the line: RT_LIBRARIES += $(TOOLCHAIN_ROOTDIR)/arm-none-eabi/lib/armv7e-m/softfp/libnosys.a With #RT_LIBRARIES += $(TOOLCHAIN_ROOTDIR)/arm-none-eabi/lib/armv7e-m/softfp/libnosys.a to comment it out. Building Libraries The build process is now incredible easy, as we can use the batch scripts provided in MQX to build our libraries. Either use “ \build\ \make\ build_gcc_arm.bat” to create the full set of libraries for the chosen board (bsp, psp, usb, shell, mfs,rtcs), or use any “build_gcc_arm.bat” found in the component and board area of your choice. These will automatically build the libraries and move the created libraries and code to ““ \lib\ .gcc_arm\” Note: when building full libraries the system will sometimes throw up errors when calling ‘mkdir’, saying that the folder structure already exists.  I have found if you re-run the script again it will not complain the second time and behaves fine. Building Examples So far only tested ‘hello2’on twrk60n512, but principles should apply to all boards and projects Again, we use the batch scripts provided in MQX, found in locations such as: \mqx\examples\ \build\make\ \build_gcc_arm.bat Running these batch scripts will create another folder within the directory, called “gcc_arm”, in which you can find “initflash_debug” and “initflash_release”.  Inside each of these folders is your compiled application. Debugging your examples Now let’s actually do something in KDS: debugging the examples and showing that they work. For this you need to have a workspace (otherwise KDS won’t run), but you can close any open projects if you wish.  Then Click on the debug menu and select “Debug Configurations...” Double click on your chosen debug interface and under the option for “C/C++ Application”, choose browse and select the ‘.elf’ file from the ‘initFlashdebug’ folder of your application. I hope this helps some people who need to get MQX running through KDS before the official support becomes available. For information on when MQX will be supported on KDS, see https://community.freescale.com/docs/DOC-95477 Re: Compiling MQX Libraries and Demos for the KDS Toolchain. Can I also compile MQX 4.0.2 libraries and demoes with KDS toolchain and the procedure above? I need to convert one CW 10.4 + MQX 4.0.2 project in KDS...

G5 Engineering: IP Camera Solution based on the i.MX 6 Applications Processor G5 Engineering demonstrates an IP camera solution based on i.MX6 apps processor at the FTF Americas 2014.   Features Multiple IP cameras that are aggregated by one i.MX6 and then sent over an IP backhaul to a second i.MX 6 for integration into a single image The images are brought out to the screen. No need to use Windows reducing virus instances With a click of a button can change the display to 1x1 or 1x2 to 4x4 views Featured NXP Products ARM® Cortex®-A9 Cores: i.MX 6 Series Multicore Processors Links G5- NXP Partner   Industrial

Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS)   Hello Freedom community users Bheema has posted on the Element14 community a very clear tutorial (accessible following the link below) to create from scratch a basic project example for the FRDM-K64 with Kinetis Design Studio (KDS). Freescale Freedom development platform: [FRDM-K... | element14 I strongly recommend you to start following those steps to properly setup the tool and the OpenSDAv2 interface embedded in the new Freedom and TWR boards. Happy Programming Greg General Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Ok Got it. Didn't realise they were different. Many thanks. Really appreciate your blogs and the examples you are posting. Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Neil, it looks you have created an SDK project in the wizard with PEx. the thing is this: with using the SDK, it is not possible to use any of the LDD projects. You only can use components designed for the SDK. There is no easy way to convert an SDK project into a 'non-SDK' project, as there are a lot of internal dependencies. If you want to use LDD or any 'non-SDK' projects with the Kinetis SDK, then make sure that SDK is *disabled*: Erich Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hello Eric Thanks - appreciate the support and happy to say what I'm finding. I've come up with another issue - I don't know if I'm missing something really basic. I went back into start another project - my aim is to test the USB HOST MSC writing to a USB Stick. Following the tutorial, exactly as before, as soon as I add the first pin to the project Bit1:BitIO_LDD it is marked with a red x - and the tab Problems has "Errors: ERROR: This component is not supported in Kinetis SDK project mode. " I seem to have upset the Processor Expert somehow and don't seem to be able to get it back. I've tried a number of different approach to just generating one bit correctly, closing the project,rebooting my machine to make sure all processors are dead, but it isn't working. I've closed all unrelated projects. I would add a snapshot jpg but, its disabled in this editor. So I must be doing something really basic wrong but I can't figure it out. Should I switch workspaces? thanks for any help Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Neil, thanks for posting the solution! I would not have thought that the virus scanner could have caused this. But indeed, I had seen myself other cases where his happened. thanks again, Erich Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Erich Thanks again for input - I got it working, For anybody else what I did was I have the USB on my Win8.1 connected to the USB microAB on the FRDM-K64F In the Control Panel - Device Manager - USB Controller - it shows "J-Link OB CDC" On the FRDM-K64F that was presetup with mbed boot, I held the reset down and pushed in the USBmicroA connector, Then dragged and dropped the "JLink_OpenSDA_V2.bin"  (JLink_OpenSDA_V2_1.bin is incompatible) then I setup the debugger for Segger and pressed the Debug button. It ran until it hit main() and then stopped then pressF8 to resume. The 2nd time I ran it,  my AVG AntiVirus 2014  kicked and removed the Segger J-Link detecting that Segger "unknown" was accessing the internet I guess "Unknown is a software that installs an additional program to display and/or download to your device unwanted advertisements, toolbars and may be considered privacy-invasive. These kinds of threats, called Adware, track your computer's web usage to feed you undesired ad pop-ups and some might even hijack your browser start or search pages,redirecting you to a different site or search engine than the one you had originally configured.Unknown is currently ranked 4303 in the world of online malware" It referenced  FreescaleKDS_1.1.0\Segger\JLinkGDBServerCL.exe http://www.avgthreatlabs.com/virus-and-malware-information/info/unknown/?name=Unknown&utm_source=TDPU&utm_medium=IDP&CTR… So it looks like JLinkGDBServerCL is advertising its being used. After restoring  JLinkGDBServerCL, and next time it happened marking it as safe, it continued, and seems to be working Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Neil, It seems to me that you try to talk with OpenOCD to a Segger firmware/probe. This will not work. Have a look at GDB Debugging with Kinetis Design Studio. You write >>for FRDM-K64F BOOTLOADER  it takes JLink_OpenSDA_V2.bin The it should enumerate as a Segger J-Link, and then you need to talk to it with the Segger interface. Erich Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Erich Thanks for info. I can't get the Debugger/USB to work with the FRDM-K64F.even though I can get OpenOCD.exe to talk to the FRDM-K64F/USB with the "mbed composite driver" installed. I wonder if there is tutorial somewhere as the configuration seems to be complex. I am finding /scripts/target/k64.cfg suggesting that it is supposed to work. There doesn't appear to be an explanation of how to configure GDB OpenOCD Debugging/USB to work with the FRDM-K64F Much appreciate any insights Summary for FRDM-K64F BOOTLOADER  it takes JLink_OpenSDA_V2.bin   or possiblyCMIS mbded (from http://mbed.org/handbook/Firmware-FRDM-K64F) Reading from Win8.1 device manager I see OpenSDA_V2.bin creates  USB controller entry "J-Link OB CDC" that OpenOCD doesn't see to find 20140530_k20dx128_k64f_if_mbed.bin  (rev0203)  create USB Controller entry "mbed Composite Device" that OpenOCD can find OpenOcd needs to set some configuration options From KDS - select icon drop down Debug Configuration, then select GDB OpenOCD Deubgging and previously created "K64_RGB_Switch_Int_Debug - tab.Debugger, Input "Configuration Options" of which I'm trying -f ${openocd_path}/scripts/target/k64.cfg (from \Freescale\KDS_1.1.0\openocd\scripts\target   ) When I launch the debugger (for both OpenSDA-V2 and mbed) I get -------------------- Error in final launch sequence Failed to execute MI command: -target-select remote localhost:3333 Error message from debugger back end: localhost:3333: The system tried to join a drive to a directory on a joined drive. localhost:3333: The system tried to join a drive to a directory on a joined drive. ------------------------- with OpenOcd_v2.bin in the FRDM-K64 if I run C:\n\bin\Freescale\KDS_1.1.0\openocd\bin\openocd -c Open On-Chip Debugger 0.8.0-dev-00003-g0c51359 (2014-07-25-13:18) C:\n\bin\Freescale\KDS_1.1.0\openocd\bin\openocd: option requires an argument --c Runtime Error: embedded:startup.tcl:47: Can't find openocd.cfg in procedure 'script' at file "embedded:startup.tcl", line 47 Info : No configuration files specified defaulting to kinetis.cfg Info : only one transport option; autoselect 'cmsis-dap' Error: unable to open CMSIS-DAP device Error: unable to init CMSIS-DAP driver Error: Error selecting 'cmsis-dap' as transport Runtime Error: C:/n/bin/Freescale/KDS_1.1.0/openocd/bin/..//scripts/kinetis.cfg: 3: in procedure 'script' at file "embedded:startup.tcl", line 58 in procedure 'interface' called at file "C:/n/bin/Freescale/KDS_1.1.0/openocd/bi n/..//scripts/kinetis.cfg", line 3 C:\Users\neilh77> ------------------------------------------------------------------------- with mbed  Composite Device C:\n\bin\Freescale\KDS_1.1.0\openocd\bin\openocd -c Open On-Chip Debugger 0.8.0-dev-00003-g0c51359 (2014-07-25-13:18) C:\n\bin\Freescale\KDS_1.1.0\openocd\bin\openocd: option requires an argument --c Runtime Error: embedded:startup.tcl:47: Can't find openocd.cfg in procedure 'script' at file "embedded:startup.tcl", line 47 Info : No configuration files specified defaulting to kinetis.cfg Info : only one transport option; autoselect 'cmsis-dap' Info : CMSIS-DAP: SWD  Supported Info : CMSIS-DAP: Interface Initialised (SWD) Info : add flash_bank kinetis kinetis.flash cortex_m reset_config sysresetreq adapter speed: 1000 kHz Info : CMSIS-DAP: FW Version = 1.0 Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1 Info : DAP_SWJ Sequence (reset: 50+ '1' followed by 0) in procedure 'init' C:\Users\neilh77> --------------------------------------- Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Hi Neil, The Segger OpenSDA v2.1 will not work on your FRDM-K64F, unless you change the bootloader. Some details about OpenSDA v2.0 and V2.1 can be found on the bottom of FRDM-K22F: Debugging with Segger J-Link OpenSDAv2.1 Firmware The OpenSDAv2.1 is only on the FRDM-K22F board (see above article). On the FRDM-K64F you can load the Segger OpenSDAv2.0 application. See Segger J-Link Firmware for OpenSDAv2 | MCU on Eclipse Re: Toggling the FRDM-K64F RGB LED using interrupts in Kinetis Design Studio (KDS) Absolutely Excellent tutorial on how to drive the KDS. Thankyou for posting it. However I've run into problems with the Segger J-LInk SEGGER - The Embedded Experts - OpenSDA / OpenSDA V2 there are two versions now 2_0.sda and 2_1.bin and they aren't explained. Neither works on my FRDM K64F board. I've been spinning my wheels trying different alternatives for the last 4hours. So I wonder if anybody can give some hints. Timeline: On a newly received Win8.1 I've got the KDS1.1.0 release downloaded, and built an empty module by specify the board FRDM K64F Then discovered the excellent Bheema tutorial above - but no place to comment there - so trying here. Created the project from the processor, then built it- but when came to debug it - it said "no emulators connected via USB" I had the mbed serial and composite device loaded. Followed Bheemas blog on OpenSDA installed _JLink_V490a.exe which has the "USB Driver for J-Link" and "USB Driver for J-Link with Virtual COM Port" loading the Segger OpenSDA V2 - and V2.1and dropped them into the BOOTLOADER -  nothing works after power cycling the FRDK64F board. The board does reliable come to BOOTLOADER (E:) fortunately. I've tried rebooting my win8.1 system to make sure drivers loaded, but nothing.

Why add Deglither in Pre-Exc 2 of AR6000? In pre excitation mode 2, you can have any duty cycle between pre exc value and 100% depending on battery and Vset voltage. On some alternators, with high duty cycles, the switching of excitation causes so much noise through the phase that this noise can be interpreted as valid phase signal. Thus, the device can go to regulation. To avoid that, we added the ability to deglitch the phase input only in pre excitation mode 2 to be sure that the signal we have are real phase signals. Depending on the duration of the noise our customer can see during pre excitation mode2, they can set the value of deglitcher. If they don't use pre excitation mode2, this value is "don't care".   Alternator Regulator

36 V eXtreme Switch Tower System Module - Demo Explore MC06XSD200, MC10XSD200, MC16XSD200 and MC50XS4200 eXtreme switch products that are showcased using the Tower System for industrial lighting and motor applications. NXP's family of intelligent, dual high side eXtreme switches for 36 V systems offers devices with current capability ranging from one to 12 A DC that are fully compatible in footprint and software within the PQFN sub family. Each output can be programmed to be used for any kind of loads, including lamps, LEDs, motors or solenoids. This allows customers to design a flexible module which can become specific and optimized for a given application through software. NXP's 36 V eXtreme switch solution provides robust design, intelligence and safety needed for industrial applications up to 36 V supply voltage. With increased integration, the switch drives lighter-weight, smaller systems and a lower component count.       Features Up to 12 A steady-state current per channel Separate bulb and DC motor latched over-current handling Sleep mode with minimal supply current (< 10 µA @ 24 V) Individually programmable internal/external PWM clock signals Overcurrent, short-circuit, and overtemperature protection with programmable auto-retry functions Accurate temperature and current sensing Open-load detection (channel in OFF and ON state), also for LED applications (7.0 mA typ.) Normal operating range: 8.0 - 36 V, extended range: 6.0 - 58 V 3.3 V and 5.0 V compatible 16-bit SPI port for device control, configuration, and diagnostics at rates up to 8.0 MHz Compatible PCB foot print and SPI software driver among the family These products are included in NXP's Product Longevity Program with assured supply for a minimum of 15 years after launch Featured NXP Products MC06XSD200: MC06XSD200, Dual 6.0 mOhm High Side Switch - Data Sheet MC10XSD200: MC10XSD200, Dual 10 mOhm High Side Switch - Data Sheet MC16XSD200: MC16XSD200, Dual 16 mOhm High Side Switch - Data Sheet MC50XS4200   Industrial

PN7462 Interface configuration Overview The PN7462 family consists of 32-bit Arm® Cortex®-M0-based NFC microcontrollers offering high performance and low power consumption. Because of the integrated NFC, many of the applications in which this product is used require interaction between some controllers, either to send data or instructions. In this case the board serves as a device for reading or writing NFC devices. Required Material OM27462CDKP: NFC Controller development kit  MCUXpresso Software and Tools  Step-by-Step Download MCUXpresso Download and unzip attachment Open the Project in MCUXpresso Build it Connect LPC Link to PN7462 card Connect the two cards to the pc Debug the Project Use GPIO 4 and 5 for select interface Use GPIO 6, 7 and 8 for select operation mode

Reading Kinetis K64 Internal Flash Causes HardFault Symptoms As we know: Flash must be programmed after an erase operation. Violation of this rule will cause programming fail and even hardfault(when AHB reading) on Kinetis K64 parts. Customer accidently uses SDK’s API programming same sector twice(over-programming) without an erase operation. Then when perform AHB reading of this sector(include using JFLash to read this sector), an Hardfault occurs. Diagnosis K64 flash has internal ECC on each sector. When over-programming happens, ECC will be crushed and trigger Hardfault when AHB reading of this sector. Solution Using SDK API FLASH_VerifyErase to check if this sector is erased. Call FLASH_VerifyErase every time before you want to program the flash. This problem will impact all Kinetis device which has FTFE flash module. Thanks for Alex Yang provide the material.

RDDSCPMSMVCSMO: Sensorless PMSM Vector Control for Compressors Reference Design Using MC56F8013 Overview Features Block Diagrams Design Resources Overview This NXP® reference design of a 3-phase sensorless PMSM vector control drive with a sliding mode observer (SMO) is targeted mainly for compressor control and other consumer and industrial applications. This cost-effective solution uses the NXP MC56F8013 device dedicated for motor control. Software written in C-code using some library algorithms Available for the MC56F8013 and MC56F8346 digital signal controllers Hardware-based on the NXP universal motor control h/w modules Features The system is designed to drive a three-phase PM synchronous motor. Application features are: 3-phase sensorless PMSM speed vector control (FOC) Sliding mode observer with adaptive velocity estimation Based on NXP ®  MC56F8013 (resp. 56F8346) controller Running on a 3-phase high voltage (230/115V) power stage FreeMASTER software control interface and monitor Block Diagrams Design Resources Legacy Designs

RDSABRE_FOR_EREADERS: SABRE for eReaders Overview Features CPU Complex Multimedia Display External Memory Interface Advanced Power Management Connectivity Controllers Design Resources Overview The NXP ®  Smart Application Blueprint for Rapid Engineering (SABRE) series of market-focused reference designs delivers the SABRE platform for eReaders based on the i.MX508 processor. The i.MX508 is the first SoC designed specifically for eReaders with a high-performance Arm® Cortex®-A8 CPU and integrated display controller certified by E Ink® for Electronic Paper Display (EPD) panels The SABRE platform provides a reference design for EPD display, touch control, audio playback as well as the ability to add WLAN, 3G modem or Bluetooth® The platform was designed to facilitate software development with faster time to market through support of both Linux® and Android™ operating systems Archived content is no longer updated and is made available for historical reference only.   Features CPU Complex Up to 800 MHz Arm Cortex-A8 32 KB instruction and data caches Unified 256 KB L2 cache NEON SIMD media accelerator Vector floating point coprocessor Multimedia OpenVG™ 1.1 hardware accelerator 32-bit primary display support up to SXGA+ resolution 16-bit secondary display support EPD Controller supporting beyond 2048 × 1536 at 106 Hz refresh (or 4096 × 4096 at 20 Hz) Pixel Processing Pipeline (PxP) supporting CSC, Combine, Rotate, Gamma Mapping Display 6”Electronic Paper Display Panel daughter card powered by E-Ink External Memory Interface Up to 2 GB LP-DDR2, DDR2 and LP-DDR1(mDDR), 16/32-bit SLC/MLC NAND flash, 8/16-bit with 32-bit ECC Advanced Power Management Multiple independent power domains State Retention Power Gating (SRPG) Dynamic voltage and frequency scaling (DVFS) Connectivity High-Speed USB 2.0 OTG with PHY High-Speed USB 2.0 Host with PHY Controllers Wide array of serial interfaces, including SDIO, SPI, I2C and UART I2S audio interface 10/100 Ethernet controller Design Resources Legacy Designs

[Solution] IAR version 8.32 can not debug revision '1B' of LPC55S69 silicon When you are the first time to debug LPC55S69, please read below document and double check your IDE, SDK and EVK version is correct. Usually, we prefer use the latest IDE, SDK and EVK boards. Important updates when using LPCXpresso55S69 Revision A2 boards and 1B silicon  [Problem Description] When you use IAR 8.32 to debug LPC55S69 '1B' silicon, the IDE will remind you "The debugging session could not be started", like below picture show: The reason of this failure is that IAR 8.32's LPC55S69 chip configuration files only support revision '0A' silicon, not '1B'. We strongly recommend customer download and use IAR 8.40.2 or latest version. The IAR IDE start support LPC55S68 '1B' silicon from 8.40.2. [Solution] If you have some reasons that must use IAR 8.32, you can download attached zip file. This zip file like a patch, include the IAR LPC55S69 '1B' support files. Un-zip this file and merge the same files under IAR installed path :IAR\arm\config\flashloader\NXP Then the IAR can support '1B' silicons. [How to identify LPC55(S)6x chip silicon versions] On the top-side marking code, there is '1B'  charactors at the end of mark strings. See below two pictures, the left one is '1B' version chips.                      LPC55(S)6x ver '1B'                                                               LPC55(S)6x ver '0A'                    LPC55xx

eMMC RPMB Enhance和GP [中文翻译版] 见附件   原文链接： https://community.nxp.com/docs/DOC-343116  i.MX6_All i.MX6DL i.MX6Dual i.MX6DualPlus6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX i.MX6UL

Powertrain & Electrification: Wireless BMS Introduction of innovative BMS system concepts based on wireless communication. Overview of system configuration and communication strategy. Validation results from lab work with OEM partner. Introduction of innovative BMS system concepts based on wireless communication. Overview of system configuration and communication strategy. Validation results from lab work with OEM partner. Power Management

Yocto Project™ Advanced A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. i.MX Applications Processors Re: Yocto Project™ Advanced These slides use the 3.10 Kernel and meta-fsl-arm?  Isn't this stale?  The last commit to meta-fsl-arm was in 2016:  meta-fsl-arm - Layer containing Freescale ARM hardware support metadata  I was very much looking forward to reading about the current tips & tricks for building with i.MX & Yocto, but I don't think this is it. 

インフォテインメント、コネクティビティ、セキュリティ:i.MX 8アプリケーションプロセッサ向けAUTOSAR MCAL <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この講義では、NXPの i.MX 8 AUTOSAR MCALおよびSafety MCAL製品の詳細について説明します。これらは、ECU設計アプローチがコーディングからコンフィギュレーションにシフトしているため、製品開発のコストと時間に多大なメリットをもたらします。これらは、i.MX MPUを利用する多くの車載ECU製品にとって、AUTOSARの階層化アーキテクチャに不可欠なコンポーネントとなります。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この講義では、NXPの i.MX 8 AUTOSAR MCALおよびSafety MCAL製品の詳細について説明します。これらは、ECU設計アプローチがコーディングからコンフィギュレーションにシフトしているため、製品開発のコストと時間に多大なメリットをもたらします。これらは、i.MX MPUを利用する多くの車載ECU製品にとって、AUTOSARの階層化アーキテクチャに不可欠なコンポーネントとなります。 i.MXアプリケーション・プロセッサ

イネーブリングテクノロジー:ハンズオンワークショップ:FreeMASTERクイックスタート – アプリケーション開発とデバッグが簡単に <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、NXPのFreeMASTERデバッグツールを使用して、システム開発とデバッグを支援する方法を学習します。さまざまなアプリケーションで多くの用途がありますが、MagniV MC9S12ZVMRMマイコンをベースにしたモータ制御の例を使用して、開発プロセスを簡素化するためのFreeMASTERの機能と使用法を示します。参加者は、システム変数をその場で調整したり、システムパラメータをリアルタイムで監視したりできるように、使用および設定することがいかに便利で簡単かを実感できます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、NXPのFreeMASTERデバッグツールを使用して、システム開発とデバッグを支援する方法を学習します。さまざまなアプリケーションで多くの用途がありますが、MagniV MC9S12ZVMRMマイコンをベースにしたモータ制御の例を使用して、開発プロセスを簡素化するためのFreeMASTERの機能と使用法を示します。参加者は、システム変数をその場で調整したり、システムパラメータをリアルタイムで監視したりできるように、使用および設定することがいかに便利で簡単かを実感できます。

Small Cell Doherty Evaluation Board: Richardson RFPD and NXP Demo This development board for RF power products is now available from Richardson, one of NXPs distributors Demo / product features This next generation board provides RF design engineers with best efficiency, a range of frequencies and voltage. Richardson has a combined depth of real-world RF technical experience and a solid partnership with NXP that enables us to serve the unique needs of the RF design engineer. Richardson and NXP serve customers across a similar set of vertical markets, including aerospace and defense, military, wireless infrastructure, mobile, broadcast and ISM. Links RF | NXP Richardson RFPD - NXP Semiconductors Mobile

eMSG インバウンドコンテキスト管理 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

DwF杭州 - 2015-08-05 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車およびコネクテッドカー 設計、ソフトウェア、サービス IAR: Cでの安全確保 スマートインダストリー インサイトとイノベーション スマートネットワーク

Interrupt latency in i.MX6SLX M4 with MQX Hi all, Cortex-M4 for i.MX6SoloX that is new to i.MX6SX customers. They concerns GPIO ISRs response time are not real time and hugh latency while Android/Linux is running on Cortex-A9 in i.MX6SoloX. I shared my test steps, report and image for your reference. Best regards, Carl

Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Project Summary Skills Developed: Materials: Step 0: Prerequisite Videos Step 1: Get a FRDM-JAM Step 2: Put it Together Step 3: Download Step 4: Hack and Slash! Sound Samples Utilities, etc: Project Summary MonkeyJam will use the FRDM-K20D50 board (which has a Cortex M4 core with DSP instructions) along with the FRDM-JAM shield so you can  make your very own guitar /bass  stomp box.  The end result will be a functional DSP system that will allow you to do high quality amplifier simulation and effects. The FRDM-JAM does not limit you to DSP on musical instruments!  There are 3.5mm stereo jacks to DSP filtering any type of audio signal.    You could even use the USB interface to create a USB-MIDI Synthesizer!  Lastly,  no need to bring the house down.....  a headphone amplifier circuit is provided so you can jam out without bothering the neighbors. MBED Support coming *very soon* Skills Developed: Real Time Processing DSP Algorithms Fixed Point Mathematics 24-bit I2S Data Converter Interfacing Soldering SOIC8 and 1206 Surface mount devices Cortex CMSIS DSP Library Materials: FRDM-K20D50 FRDM-JAM Development Tools Install Codewarrior 10.5 for Microcontrollers (Eclipse) Special Edition to your  machine Example Code Get the latest copy from Github Step 0: Prerequisite Videos The videos are organized into a nice YouTube playlist: H.I.T 1: Monkey Jam - YouTube https://www.youtube.com/playlist?list=PLWM8NW5LEukgM-D5eRMtKZ8R2WfXnqKGp MonkeyJam Watch Me 1st FRDM-JAM Hardware Overview MonkeyJam Software Overview Introduction to Fixed Point Math for Embedded Systems - Part 1 of 3 Introduction to Fixed Point Math for Embedded Systems - Part 2 of 3 Introduction to Fixed Point Math for Embedded Systems - Part 3 of 3 Real Time Signal Processing Part 1 of 3 Real Time Signal Processing Part 2 of 3 Real Time Signal Processing Part 3 of 3 q31_t (Q0.31) Number Format for the CMSIS DSP Libraries and the MonkeyJam Software Guitar physics in a nutshell Ideas for hacking the MonkeyJam Step 1: Get a FRDM-JAM MonkeyJam Build Package on the FRDM-JAM site.    Please let us know if you are interested in a pre-assembled version.  If there is enough demand we will get some preassembled for purchase, I will get a Kickstarter going!   Don't be afraid to build it yourself,  Soldering is fun!  There is plenty of good stuff on the web on how to do SMT soldering.  All of the parts on the board are fairly simply once you get the hang of it and everything can be hand soldered  The key is having some decent tools. Step 2: Put it Together Attach the FRDM-JAM to the FRDM-K20D50.  The FRDM-K20D50 comes with female headers that you can solder on so the boards can be easily separated.  Note that as of Rev Gamma (current version),   it is possible to connect to a K64F.    The software isn't quite there but it hardware connections are available.   If you are unsure,  stick with the FRDM-K20D50 Step 3: Download Download the Example Software from Github.  The video "Loading and Configuring the MonkeyJam Example Software" will step you though downloading the program and doing some basic configuration. Step 4: Hack and Slash! Plug In and jam! Sound Samples Each sound sample was my Carvin Ultra-V guitar plugged direct into the MonkeyJam Board.  The output was fed to a Zoom Handy Recorder H4n (Thanks to Brandin Claar of Remodulate LLC for the recorder).  The H4N recorded the signal at 44.1KHz Sample rate @16-bit.  The sound files were converted to mono format via Goldwave.  No processing (other than a  volume boost on the files) was performed.   I listen to the recording in real-time via a line out on the H4N.  File (See Attachments) Patch Notes STE-003-Neck-a12b12g12-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 12 O'Cock Beta Pot - 12 O'Cock Gamma Pot - 12 O'Cock Pattern Similar to Metallica Sanitarium STE-005-Neck-a7b5g5-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 7 O'Cock Beta Pot - 5 O'Cock Gamma Pot - 5 O'Cock Pattern Similar to Metallica Sanitarium STE-006-Neck-a12b7g5-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 12 O'Cock Beta Pot - 7 O'Cock Gamma Pot - 5 O'Cock Pattern Similar to Metallica Sanitarium STE-007-Neck-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Neck Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-008-Neck+Bridge-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Neck + Bridge Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-009-Bridge-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Bridge + Bridge Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-010-Neck-VariousSettings-Jammy.wav PATCH_TUBEY_CLEAN Neck + Bridge Pickup The pots were moved around throughout the file B-Minor Type Jam STE-011- Bridge - Various Settings - On-Off Demo-RandomDroppedD.wav PATCH_OVERDRIVE Bridge Pickup Alpha Pot - 5 O'Cock Beta Pot - 12 O'Cock Gamma Pot - 12 O'Cock Random Dropped D twiddling STE-012- Neck - Various Settings - On-Off Demo-Jammy.wav PATCH_OVERDRIVE Neck Pickup Alpha Pot - 5 O'Cock Beta Pot - 7 O'Cock Gamma Pot - 7 O'Cock Random B-Minor twiddles (bluesy) PATCH_OVERDRIVE             +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                               |                  |      |                          |      |                     |                    Signal In  |    IIR BiQuad    |      |      Hard Overdrive      |      |      IIR BiQuad     |  Signal Out       +–––––––––+>|                  +––––+>|                          +––––+>|                     +–––––––––––––+>                |   [Peaking EQ]   |      | [atan24pi Look Up Table] |      |  [Low Pass Filter]  |                               |                  |      |                          |      |                     |                               +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                                                                                                                                                     0.1 < Q < 1.5    [Pot Alpha]                                     Q = 0                                                                                                                                                              50 < Fs < 750    [Pot Gamma]                                   Fs = 2000                                                                                                                                                          -20 < dbGain < 20  [Pot Beta]                                                                                                                                                                                        PATCH_TUBEY_CLEAN              +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                               |                  |      |                          |      |                     |                    Signal In  |    IIR BiQuad    |      |      Soft Overdrive      |      |      IIR BiQuad     |  Signal Out       +–––––––––+>|                  +––––+>|                          +––––+>|                     +–––––––––––––+>                |     [LowShelf]   |      | [atan4pi Look Up Table]  |      |  [Low Pass Filter]  |                               |                  |      |                          |      |                     |                               +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                                                                                                                                                     0.05 < Q < 2.58   [Pot Alpha]                                     Q = 2.0                                                                                                                                                             1000 < Fs < 4000    [Pot Beta]                                   Fs = 2500                                                                                                                                                      -15 < dbGain < 15  [Pot Gamma]                                                                                                                                                                                    Utilities, etc: Biquad Filter View - A IIR Biquad Filter Design & Visualization Tool Student Project Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli I have implemented the CMSIS code and also made the document for others , kindly look if anything is incorrect in the process and please update it. https://community.freescale.com/message/414670#414670 Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Hughes Can you provide me the link of the video in which you have demonstrated how to implement  CMSIS library with codwarrior basically I am concerned with FFT library which you have implemented? It Will be a great help. Thanks Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Thanks for your reply. when I am opening your project for the 1st time I am getting some warning message. Is this message of any concern?. Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Amit: If you click on the project properties for the library and look at processor settings, there are 2 symbols (ARM_CM4 and ARM_ROUNDING).   This is all I had to do to get it compile. I think I covered it in one of the videos.  If not, I will certainly have to get some sort of small video for it!. -Eli Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Hughes I Imported the MonkeyListen Project and it got compiled without any error. right now for testing I am targeting FRDM-K20D50M (MK20DX128). After this I will be targeting mk60fn1m0vlq12. What are the settings required to be done for using the library in any project ? If you can provide some snapshot of  the settings required to make it work It will be helpful for all the community members. As I went across some queries which was unanswered regarding the same. In ARM's website also I didn't find any help regarding this. When I saw your tutorial everything was well explained. So If this portion is also covered in it than it will a great help for people like me. and I am sure many people want to use it but can't use due to this implementation part. Thanks in advance Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Amit: Do you try importing the MonkeyListen project and see the settings I used?   What chip are you targeting? Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi eli_hughes Thanks For the awesome tutorial. It pretty much shows the real life implementation of DSP. I wanted to ask you about implementation of CMSIS library in codewarrior. In one of my projects I wanted to implement DSP library to implement FFT. But I am stuck in implementing CMSIS library. I saw your Video for this as well as the 2nd project i.e Project #2: Monkey Listen! Audio Spectrum Analyzer Display That was also awesome like this. But again I cannot move further as I am facing problem in implementing the library.I went through some post regarding implementing the CMSIS library but that was not compiling and was giving errors. and sometimes was exceeding the m-text limit. I went through the following links. Tutorial: Using the ARM CMSIS Library | MCU on Eclipse Adding the CMSIS-DSP library 移植CMSIS-DSP库到CodeWarrior的步骤以及Kinetis FPU单元应用的对比 Please look into the matter. I hope this post will be beneficial for many community users. Thanks in advance Kind Regards Amit Kumar