[RT1170]How to make a slave core project as a XIP target Normally we make a dual core project as below: Master Core Project running as a XIP target Slave Core Project running as a RAM target Master Core loads the image of the slave core into SRAM out of POR and kicks off the slave core, so that both the master and slave cores run application from different memory regions to gain the max performance.  There are some cases when users need to get both the master and slave cores run applications as XIP targets, so the application image size, especially for the slave core would not be limited by the SRAM size, and it is also technically possible. Here are some tips for this kind of use case. 1. Changes on Master Core Project a) Update the memory settings by splitting the flash into two parts, one for master core, the other for slave core. Here the size of each of them is set as 0x2000000, but you may adjust them according to your requirements. b) Put the slave core application code into the second flash region as shown above. c) Update the slave core boot address in the master core project. 2. Changes on Slave Core Project a) Add a flash region for slave core application code, and make sure the flash loader is selected properly. You may notice this flash region starts from 0xA000000 instead of 0x32000000 for the master core project. That is because this is the alias address for the slave core in this case, please refer to the following for details. With offset of 0x2000000 we set for the master core project, we have 0xA000000 here for the slave core project. b) Unselect the option of "Link application to RAM" 3. Build & Debug This is a guide line to run both the master core and slave core projects as XIP targets from one flash. Hands-On Training

ラボTutorial_TPMオーバーフロー <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完全な資料は以下で見つけることができます https://community.freescale.com/docs/DOC-95205 (マイビデオで視聴)

PCI-Express introduction PCI-Express introduction PCIe Device Type And Topology PCIe system architecture          2.1 Transaction Layer          2.2 Data link layer          2.3 Physical Layer Interrupts Mechanism PCIe enumeration and resource assignment Re: PCI-Express introduction Hi, can you tell me the file/code in linux kernel for the PCIe RP controller driver and also for PCIe EP controller driver? also how does a RC Controller driver differs from the EP controller driver? what are the role/responsibility/functions of a RC and EP controllers?

How to add 3G modem in Sabresx board Overview The purpose of this document is to describe how to enable 3G modem in i.MX sabresx board for Android software. Hardware Changes Unlike other boards of I.mx series, in sabresx board  3G modem doesn't share to use PCIE slot any longer. It is not connected with PCIE slot by default. So if you still want to use 3G modem like in sabresd board. You need to do a tiny hardware rework. Like the below, R177 and R178 is DNP. Just add a zero resistor here. Software patches After you have do hardware rework above, then you should git am the attached patch to add software support which will add the dts config of 3G power. In our official release version, we don't include this patch. Android i.MX6_All Re: How to add 3G modem in Sabresx board Hi waterzhou I am working on i.MX 6 SoloX SABRE SD board to support a customer for 3G USB dongle for data connection. The changes that you mentioned above are related to the PCIe interface. Will the above changes also support/ applicable to  3G USB dongle? How do we interface the 3G USB dongle with the PCIe Interface? Thanks and Regards, -Devaraj

ZigBee/面向智能家庭的Wi-Fi连接网关 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 演示所有者AngelC 该演示展示了使用智能手机/平板电脑控制家庭网络内各种无线设备的能力。这是通过所谓的网关系统实现的，该系统由Tower System TWR K60 Kinetis 开发模块组成，该模块通过以太网/Wi-Fi 与无线路由器连接，再加上一个Kinetis KW2x MCU 设备，使用单个无线电（双 PAN）控制基于 ZigBee 的家庭自动化 1.2 和 TCP/IP 网络。 总之，平板电脑上的Android应用通过Wi-Fi连接网关，网关将每一个命令都进行转换，支持ZigBee HA 1.2和TCP/IP网络，从而使任何带Wi-Fi功能的设备都能控制多个设备，即使使用不同的通信协议。 特征 ZigBee 和 TCP/IP 连接 Android 应用程序 特色恩智浦产品 产品 链接 Kinetis ® K60-100 MHz，基于 Arm ® Cortex ® -M4 内核的混合信号集成微控制器 Arm ® Cortex ® -M4|Kinetis K60 100 MHz 32 位微控制器|NXP | NXP Kinetis K60 100 MHz MCU塔式系统模块 TWR-K60D100M|塔式系统板|Kinetis MCU|恩智浦 智能家居

Timesys: Optimized Performance Devices for Various Applications Demo Owner Brian Gildon   Timesys Vice President of Business Development, Brian Gildon demonstrates various NXP based applications for optimized performance devices. Demonstrations include  NXP's Vybrid TWR-VF65GS10 board on Linux, a fast boot demonstration using i.MX 6 platform on Linux and finally a Sabre SDP a multi-touch interface design for designers who want simple branding.   Features Timesys - Linux tools services and training First demo: Vybrid tower board demo RTOS and Linux running simultaneously Second demo: Boot up Android quickly from a cold boot Third demo: Accelerated video demo vs non-accelerated video comparison Fourth demo: QT widget support on a multi-touch interface Product Link SABRE Board for Smart Devices Based on the i.MX 6Quad Applications Processors i.MX 6Quad SABRE Development Board | NXP  VFxxx Controller Solutions VFxxx Controller Solutions based on Arm® Cortex® A5 and M4 Cores | NXP  Links Tymesys   Automotive Industrial

softISP、eIQに関する情報 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> softISPについて 品番 : https://github.com/NXPmicro/gtec-demo-framework/tree/master/DemoApps/OpenCL/SoftISP/source ドキュメント : https://www.nxp.com/docs/en/application-note/AN12060.pdf デモは 、Linux L4.19.35の パス / opt / imx-gpu-sdk / OpenCL / SoftISP にあります   eIQについて コミュニティ: https://community.nxp.com/community/eiq eIQサンプルAPPs: https://community.nxp.com/docs/DOC-343785 eIQライブラリソースコード: https://source.codeaurora.org/external/imx/meta-fsl-bsp-release/tree/imx/meta-ml/recipes-libraries?h=warrior-4.19.35-1.1.0

通过i.MX6Q SABRE-SD上的SD卡刷新eMMC的指南 [中文翻译版] 见附件   原文链接： Guide to flash an eMMC from SD Card on i.MX6Q SABRE-SD  i.MX6_All i.MX6DL i.MX6Dual i.MX6DualPlus6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX

ADAS 和驾驶员替换：BlueBox 深度解析 - 恩智浦 AD 处理平台 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXP BlueBox：深入了解硬件和软件。技术会议解释如何使用 Kalray 硬件和 Apollo 软件。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXP BlueBox：深入了解硬件和软件。技术会议解释如何使用 Kalray 硬件和 Apollo 软件。 软件和工具

NXPの包括的なセンサ概要:自動車およびIoT(産業/医療)アプリケーション向けのモーション、圧力、磁気センサ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、自動車市場とIoT市場の両方を対象としたNXPの完全なセンサポートフォリオについて説明します。このセッションでは、自動車とIoTの両方の領域におけるセンサーのさまざまなターゲットアプリケーションの概要についても説明します。このセッションでは、エアバッグ、タイヤ空気圧モニターから低電力アクティビティ監視、資産追跡まで、さまざまなアプリケーションについて説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、自動車市場とIoT市場の両方を対象としたNXPの完全なセンサポートフォリオについて説明します。このセッションでは、自動車とIoTの両方の領域におけるセンサーのさまざまなターゲットアプリケーションの概要についても説明します。このセッションでは、エアバッグ、タイヤ空気圧モニターから低電力アクティビティ監視、資産追跡まで、さまざまなアプリケーションについて説明します。 センサ

Test Elapsed time based on CTimer module Test Elapsed time based on CTimer module   Sometimes, It is required to test the time which an api function takes when the function is executed, for example, some users want to test the flash erasing time and flash programming time. User can use GPIO to set/clear and use scope to test the GPIO timing to measure the time an api function takes, the method is very simple and straightforward but inaccurate. The document describes to configure CTimer as a 32bits  free-running counter, user can read the counter value before and after an api function and compute the counter value difference to get the time the api function takes. The CTimer of LPC54xxx family counts the APB bus clock, the APB bus clock Is driven by 12 MHz FRO, user can use the following code to measure the elapsed time. For example, we test the elaped time of  delayTimer(10000); function, we get the variable tPoint1, tPoint2. The actual time is (tPoint2- tPoint1)*(1/12000000). In the example, the tPoint2=110127, the tPoint1=53, the elapsed time is (110127-53)*(1/12000000)=9.172us. //the souce code focuses on LPC54xxx family uint32_t tPoint1,tPoint2,tPoint3,tDiff; void test(void) {     tPoint1=CTIMER_GetTimerCountValue(CTIMER2);     //simulate elapsed time     delayTimer(10000);     tPoint2=CTIMER_GetTimerCountValue(CTIMER2);     tDiff=tPoint2-tPoint1;       //simulate elapsed time     delayTimer(20000);     tPoint3=CTIMER_GetTimerCountValue(CTIMER2);     tDiff=tPoint3-tPoint2;      PRINTF("Time instand:tPoint1=%d, tPoint2=%d, tPoint3=%d \r\n",tPoint1,tPoint2,tPoint3); } Snippet of simple source code based on MCUXpresso tools and LPC54618 board developed by XiangJun Rong #include "fsl_ctimer.h" void test(void); void CTimerInit(void); void delayTimer(uint32_t elapsedTimer); uint32_t tPoint1,tPoint2,tPoint3,tDiff; void CTimerInit(void) {     ctimer_config_t config;     ctimer_match_config_t matchConfig;     /*CTimer use APB bus clock as Timer tick, set the APB bus clock as 12MHz internal FRO */      CLOCK_AttachClk(kFRO12M_to_ASYNC_APB);     CTIMER_GetDefaultConfig(&config);       CTIMER_Init(CTIMER2, &config);       matchConfig.enableCounterReset = true;     matchConfig.enableCounterStop = false;     matchConfig.matchValue = 0xFFFFFFFF;     matchConfig.outControl = kCTIMER_Output_NoAction;     matchConfig.outPinInitState = true;     matchConfig.enableInterrupt = false;     CTIMER_SetupMatch(CTIMER2, kCTIMER_Match_3, &matchConfig);     CTIMER_StartTimer(CTIMER2); }   void test(void) {     tPoint1=CTIMER_GetTimerCountValue(CTIMER2);     //simulate elapsed time     delayTimer(10000);     tPoint2=CTIMER_GetTimerCountValue(CTIMER2);     tDiff=tPoint2-tPoint1;       //simulate elapsed time     delayTimer(20000);     tPoint3=CTIMER_GetTimerCountValue(CTIMER2);     tDiff=tPoint3-tPoint2;      PRINTF("Time instand:tPoint1=%d, tPoint2=%d, tPoint3=%d \r\n",tPoint1,tPoint2,tPoint3); }   void delayTimer(uint32_t elapsedTimer) {     uint32_t i;     for(i=0; i     {         __asm("nop");     } }   int main(void) {    …………………………………………………………………………………………………..     PRINTF("Elapse time test start: \r\n");     CTimerInit();     test();     for(;;) {} ………………………………………… }  

加州大学戴维斯分校团队 Chucksgon 技术报告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

スロバキア工科大学のシールチームテクニカルレポート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ブラチスラバのスロバキア工科大学(スロバキア)のチームFor Sealからのテクニカルレポート - EMEA Finals 2015 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ブラチスラバのスロバキア工科大学(スロバキア)のチームFor Sealからのテクニカルレポート - EMEA Finals 2015

APF-SNT-T1358 - 南京、深圳 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍全新的 QorIQ LS1 系列，这是 QorIQ LS 系列中第一个基于双 ARM ® Cortex ® -A7 内核的设备系列。您将收到 LS1 处理器的概述——优势、差异化以及网络和工业应用的功能。主讲人：尤鹏 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍全新的 QorIQ LS1 系列，这是 QorIQ LS 系列中第一个基于双 ARM ® Cortex ® -A7 内核的设备系列。您将收到 LS1 处理器的概述——优势、差异化以及网络和工业应用的功能。主讲人：尤鹏

Opal i.MX53 上的 WEC2013 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这段 1 分钟的视频重点介绍了在 Device Solutions Opal i.MX53 开发套件上运行的 Windows Embedded Compact 2013。与 Windows Embedded Compact 7 相比，此新版本在性能和生产力方面有许多增强。移植由 Guruce.com 完成。 此视频已被删除。 （在 “我的视频” 中查看）

Freescale Debuts Kinetis L Series, World's Most Energy-Efficient Microcontrollers New 32-bit MCUs designed to transform consumer and industrial applications currently using legacy 8- and 16-bit architectures SAN ANTONIO, Jun 19, 2012 (BUSINESS WIRE) -- Freescale Semiconductor FSL +0.80% is now offering alpha samples of its Kinetis L series, the industry's first microcontrollers (MCUs) built on the  ARM(R) Cortex(TM)-M0+ processor. Kinetis L series devices are on display this week at the Freescale        Technology Forum (FTF) Americas and were demonstrated during the event's opening keynote address. As machine-to-machine communication expands and network connectivity  becomes ubiquitous, many of today's standalone, entry-level applications will require more intelligence and functionality. With the Kinetis  L series , Freescale provides the ideal opportunity for users of legacy 8- and 16-bit architectures to migrate to 32-bit platforms and bring additional intelligence to everyday devices without increasing power  consumption and cost or sacrificing space. Applications, such as small  appliances, gaming accessories, portable medical systems, audio systems, smart meters, lighting and power control, can now leverage 32-bit capabilities and the scalability needed to expand future product lines -- all at 8- and 16-bit price and power consumption levels. "In our view, 8- and 16-bit development has reached the end of the road. Those architectures simply can't keep up as the Internet of Things gains traction," said Geoff Lees, vice president and general manager of Freescale's Industrial & Multi-Market MCU business. "Kinetis L series MCUs are ideal for the new wave of connected applications, combining the required energy efficiency, low price, development ease and small  footprint with the enhanced performance, peripherals, enablement and scalability of the Kinetis 32-bit portfolio." Extreme energy efficiency The ARM Cortex-M0+ processor consumes approximately one-third of the energy of any 8- or 16-bit processor available today, while delivering  between two to 40 times more performance. The Kinetis L series supplements the energy efficiency of the core with the latest in  low-power MCU platform design, operating modes and energy-saving peripherals. The result is an MCU that consumes just 50 uA/MHz* in very-low-power run (VLPR) mode and can rapidly wake from a reduced power state, process data and return to sleep, extending application battery life. These advantages are demonstrated in the FTF demo, which compares the energy-efficiency characteristics of the Kinetis L series against solutions from Freescale competitors in a CoreMark benchmark analysis.        The Kinetis L series is also part of the Freescale Energy-Efficient Solutions program. Kinetis L series energy-saving peripherals do more with less power by maintaining functionality even when the MCU is in deep sleep modes. In traditional MCUs, the main clock and processor core must be activated to perform even trivial tasks such as sending or receiving data, capturing or generating waveforms or sampling analog signals. Kinetis L series peripherals are able to perform these functions without involving the core or main system, drastically reducing power consumption and improving battery life. Built using Freescale's innovative, award-winning flash memory technology, the Kinetis L series offers the industry's lowest-power flash memory implementation. This improves upon the conventional silicon-based charge storage approach by creating nano-scale silicon islands to store charge instead of using continuous film, improving the flash memory's immunity to typical sources of data loss. "The Internet of Things needs very low-cost, low-power processors that        can deliver good performance," said Tom R. Halfhill, a senior analyst        with The Linley Group and senior editor of Microprocessor Report. "As  the first 32-bit microcontrollers to use ARM's Cortex-M0+ processor core, Freescale's Kinetis L-series MCUs will bring the energy efficiency and prices typically associated with 8- and 16-bit MCUs to a broad range of consumer and industrial applications." Development simplicity The Kinetis L series addresses the ease-of-use requirement critical for entry-level developers through innovations including: -- The Freescale Freedom development platform, a small, low-power, cost-efficient evaluation and development system for quick application prototyping and demonstration. It combines an industry-standard form factor with a rich set of third-party expansion board options. An integrated USB debug interface offers an easy-to-use mass-storage device mode flash programmer, a virtual serial port and classic programming and run-control capabilities. -- Processor Expert software, a GUI-based, device-aware software generation tool that eliminates the need to write peripheral start-up code or device drivers. Helps developers easily migrate from 8- and 16-bit to 32-bit solutions by simplifying the software architecture and  dramatically reducing application development time. --  The Kinetis MCU Solution Advisor, a web-based application with an interactive MCU product selector that helps identify the best-suited MCU by applying dynamic filters based on operating characteristics, packaging options, memory configuration and peripheral hardware library. Integration and scalability Each Kinetis L series family includes scalable flash memory options, pin-counts and analog, communication, timing and control peripherals, providing easy migration paths for end product line expansion. Features common to the Kinetis L series families include: --         48 MHz ARM Cortex-M0+ core --         High-speed 12/16-bit analog-to-digital converters --         12-bit digital-to-analog converters --         High-speed analog comparators --         Low-power touch sensing with wake-up on touch from reduced power states --         Powerful timers for a broad range of applications including motor control The first three Kinetis L series families: --         Kinetis L0 family -- the entry point into the Kinetis L series. Includes eight to 32 KB of flash memory and ultra-small 4mm x 4mm QFN packages. Pin-compatible with the Freescale 8-bit S08P family. Software- and tool-compatible with all other Kinetis L series families. --         Kinetis L1 family -- with 32 to 256 KB of flash memory and  additional communications and analog peripheral options. Compatible with the Kinetis K10 family. --         Kinetis L2 family -- adds USB 2.0 full-speed host/device/OTG. Compatible with the Kinetis K20 family. The Kinetis L series is pin- and software-compatible with the Kinetis  K series (built on the ARM Cortex-M4 processor), providing a migration path to DSP performance and advanced feature integration. Availability and pricing Kinetis L series alpha samples are available now, with broad market sample and tool availability planned for Q3. Pricing starts at a suggested resale price of 49 cents (USD) in 10,000-unit quantities. The Freescale Freedom development platform is planned for Q3 availability at  a suggested resale price of $12.95 (USD). For more information about Kinetis L series MCUs, visit   www.freescale.com/Kinetis/Lseries    . *Typical current at 25C, 3V supply, for Very Low Power Run at 4MHz core  frequency, 1MHz bus frequency running code from flash with all peripherals off. About the Freescale Technology Forum Created to drive innovation and collaboration, the Freescale Technology Forum (FTF) has become one of the developer events of the year for the embedded systems industry. The Forum has drawn more than 48,000 attendees at FTF events worldwide since its inception in 2005. Our annual flagship event, FTF Americas, takes place June 18-21, 2012, in San Antonio, Texas. About Freescale Semiconductor Freescale Semiconductor  FSL +0.80% is a global leader in embedded processing solutions, providing industry leading products that are advancing the automotive, consumer, industrial and networking markets. From microprocessors and microcontrollers to sensors, analog integrated  circuits and connectivity -- our technologies are the foundation for the innovations that make our world greener, safer, healthier and more connected. Some of our key applications and end-markets include automotive safety, hybrid and all-electric vehicles, next generation wireless infrastructure, smart energy management, portable medical  devices, consumer appliances and smart mobile devices. The company is  based in Austin, Texas, and has design, research and development,        manufacturing and sales operations around the world.   www.freescale.com Freescale, the Freescale logo, Energy Efficient Solutions logo, Kinetis  and Processor Expert are trademarks of Freescale Semiconductor, Inc.,  Reg. U.S. Pat. & Tm. Off. ARM is the registered trademark of ARM  Limited. Cortex is the trademark of ARM Limited. All other product or  service names are the property of their respective owners. (C) 2012   Freescale Semiconductor, Inc. Photos/Multimedia Gallery Available:   http://www.businesswire.com/cgi-bin/mmg.cgi?eid=50313420〈=en SOURCE: Freescale Semiconductor Kinetis L Series MCUs

Q&A: What is max size of uImage? Question: In a single uImage to contain the compressed kernel and rootfs, if the uImage is greater than 16MB, the system will not boot and reports errors. Is there a size limitation on uImage?  If so, is there a work around? Answer: uImage should only contains kernel compressed. rootfs should be read through a linux partition after the kernel boots up. Regarding the uImage's size, there is no limitation. In the other hand, a single uImage with kernel and filesystem is needed; in other words, kernel (alias uImage) needs a filesystem to work, and these are two independent systems in that sense. If u-boot, kernel and filesystem are in a single device (SD Card), the filesystem must be mounted in the first partition (SD, eMMC, etc) starting somewhere > 16M/512 sectors. But in cases where: * A fast boot is needed with  very small rootfs * As a intermediate (temporal) rootfs  before switching  to the real rootfs. The usage (actually used when flashing with the MFG tool) of this intermediate system is to load heavy modules, keeping the uImage small. This mechanism is called initramfs and the uImage will contain the kernel and the this mini rootfs compressed as cpio archive. But there appears to be a 16MB limitation. See here:  http://www.isysop.com/unpacking-and-repacking-u-boot-uimage-files/ It seems to be related to alignment suggesting that 24-bit addressing is used instead of 32-bit.  I did notice Thumb mode is used, which seems odd to me. i.MX6_All

MaxonF2140_1.001_02.07.2012.PEupd Maxon Description Driver implementing a driver for a DC Motor. Component Maxon.PEupd Dependencies none License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2012, all rights reserved. This an open source software using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice. Maxon Description Driver implementing a driver for a DC Motor. Component Maxon.PEupd Dependencies none License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2012, all rights reserved. This an open source software using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice. Component Exchange

SD_Card_1.152_30.07.2012.PEupd SD_Card Description SD Card low level driver Component SD_Card.PEupd Dependencies FreeRTOS, Wait, Timeout License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2012, all rights reserved. This an open source software implementing an SD card low level driver useful for the the ChaN FatFS, using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice. SD_Card Description SD Card low level driver Component SD_Card.PEupd Dependencies FreeRTOS, Wait, Timeout License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2012, all rights reserved. This an open source software implementing an SD card low level driver useful for the the ChaN FatFS, using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice. Component Exchange Re: SD_Card_1.152_30.07.2012.PEupd I'm doing that kind of things with ColdFire V1, V2 and Kinetis. I do not have a project to share for S12. As for an example how to use a file system with the CN128, maybe have a look at http://www.steinerberg.com/EmbeddedComponents/Examples/Example_CN128_FatFS/home.htm Re: SD_Card_1.152_30.07.2012.PEupd Hello, Actually it's my first time using SD card on embedded system. I'm planning to use the SD card as part of a data logger with an MC9S12. I want to save the data from an ADC on a csv file to be readed on Windows, so I need a file system. But I dont have a good idea of how works the file system. Let me know If you have some information, sources that can be helpful... That would be cool... Cheers On Fri, Sep 14, 2012 at 1:03 PM, Erich Styger Re: SD_Card_1.152_30.07.2012.PEupd Hello, Hmm, that would be a problem if you are using the component standalone. 'diskio.h' is the interface to FatFS. I need to check the component sources, and I admit I have used it only in the context of a file system (with the FatFS component, see http://mcuoneclipse.wordpress.com/2012/07/30/fatfs-with-kinetis. Are you planning to use the SD_Card component without a file system? Thanks, Erich Re: SD_Card_1.152_30.07.2012.PEupd I was trying to add this beam, but i get this error message when I click on Make... (diskio.h file not found) I would like to know why May be I'm doing somthing wrong... Thanks

Freescale MQX™ 4.0.2 Release The new Freescale MQX™ 4.0.2  release is now available on the www.freescale.com/MQX ·         Files available                    # Name Description 1 FSL_MQX_RELEASE_NOTES_4_0_2 Freescale   MQX™ RTOS 4.0.2 Release Notes 2 FSL_MQX__FFS_RELEASE_NOTES_4_0_2 Freescale   MQX™ FFS package 4.0.2 Release Notes 3 FSL_MQX_ATHEROS_RELEASE_NOTES_4_0_2   Freescale   MQX™ Atheros Wifi package 4.0.2 Release Notes 4 Freescale   MQX RTOS 4.0.2 Atheros Wifi package Atheros   Wifi solution for MQX™ 4.0.2 5 Freescale   MQX RTOS 4.0.2 FFS package NAND   Flash File System solution for MQX™ 4.0.2 6 Freescale   MQX RTOS 4.0.2 MQX™   Source code. Includes an RTOS, File   System, TCP/IP and USB host/device software stacks. Does not require MQX™ 4.0   installation. ·         What is New? o   AutoEVB Vybrid A5 and M4 Board support packages §  Support for CortexA5 and CortexM cores of dual core Vybrid processor §  Supporting standard set of IO drivers o   Vybrid BSP extensions §  RTC and NAND flash driver ported to Vybrid platform §  MMU support extended by handling of 4KB memory block §  Introduced new QuadSPI driver §  CortexM4 boot option enabled. §  Direct code execution from QuadSPI flash – XIP provided. Feature demonstrated in Vybrid QuadSPI bootloader. Introduced the first version of eDMA driver – the driver is experimental and will be further extended in the next MQX version. Documentation is not provided. o   Kinetis SPI driver was updated to use the eDMA driver. o   Hardware timer driver support extended to Systick and GPT HW modules. Kinetis and Vybrid BSPs updated to leverage the Hardware timer to provide MQX tick time. o   RTCS Hardware checksum acceleration enabled in ENET driver (for TCP and UDP); the benefits are the increased throughput and a reduced processor loading. This option is enabled by default for the K60N512 platform. o   HTTP server redesigned to provide a faster and more robust solution. The server API is simplified and changed to correspond to the RTCS standard. o   New SMTP client functionality provided as a part of the RTCS network suite. The client offers a simple API for e-mail handling. The new RTCS Shell command “email” demonstrates its functionality. o   The security_email, security_webserver, and security_telnet demo applications are removed from this release. Networking functionality is demonstrated in RTCS shell and httpsrv example applications. o   Multicore Communication (MCC) library updated to version 1.1. Fixed the incorrect usage of cache macros in the mcc_send() function. ·         Known issues o   For known issues and limitations please consult the release notes.