ワイヤレス通信 - Bluetooth®ソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

NET-N1877 インテリジェント・クラウド・エッジおよび顧客宅内向けQorIQ NFVソリューションの紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エンタープライズOEMやサービスプロバイダーのクラウドおよびプレミスアーキテクチャを推進する、エキサイティングな新しいネットワーク機能仮想化のユースケースについて学びます。新しいNXPのオープンスタンダードと最適化されたNFVシステムソリューションを理解し、ワットあたりのパフォーマンスを最大限に高めます。また、このNFVソフトウェアスイートをNXPプロセッサと組み合わせることで、顧客のCAPEX/OPEXを保護し、市場投入までの時間を短縮し、新たな顧客の収益源を実現する方法も実現できます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エンタープライズOEMやサービスプロバイダーのクラウドおよびプレミスアーキテクチャを推進する、エキサイティングな新しいネットワーク機能仮想化のユースケースについて学びます。新しいNXPのオープンスタンダードと最適化されたNFVシステムソリューションを理解し、ワットあたりのパフォーマンスを最大限に高めます。また、このNFVソフトウェアスイートをNXPプロセッサと組み合わせることで、顧客のCAPEX/OPEXを保護し、市場投入までの時間を短縮し、新たな顧客の収益源を実現する方法も実現できます。 スマートネットワーク

LAT-INS-T2438 - ARM® Cortex-M® マイクロコントローラをベースとする最も包括的なソリューション: KinetisとLPCのご紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、さまざまなアプリケーションに焦点を当て、KinetisファミリとLPCファミリの両方に焦点を当てます。各ファミリーの新しいメンバーを紹介し、今後これらのファミリーに何を期待できるかについての洞察を提供します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、さまざまなアプリケーションに焦点を当て、KinetisファミリとLPCファミリの両方に焦点を当てます。各ファミリーの新しいメンバーを紹介し、今後これらのファミリーに何を期待できるかについての洞察を提供します。

NXP FTF Connects - 圣保罗 - 2016年11月8日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 设计、软件与服务 LAT-DES-T2443 - i.MX 应用处理器产品系列更新：i.MX 6UltraLite、i.MX 6ULL、i.MX 6QuadPlus、i.MX 7 和 i.MX 8 LAT-DES-T2441 - 揭秘 MPU 设计：如何利用现有文档和工具简化基于复杂 i.MX 应用处理器的电路板的开发流程 LAT-DES-T2445 - PCB 布局技巧与窍门 – 稳健性之旅 智能家居和智能建筑 LAT-HMB-T2459 - 未来电子：设计时考虑安全性 LAT-HMB-T2460 - 图灵计算机：实践研讨会：为您的多媒体产品添加热点功能（3G/4G-Wi-Fi 路由器） 洞察与创新 LAT-INS-T2442 - 面向多市场的模拟解决方案 - 汽车和工业 LAT-INS-T2438 - 了解基于 ARM ® Cortex ® -M MCU 的最全面解决方案：Kinetis 和 LPC LAT-INS-T2437 - 核心解决方案 - 采用恩智浦接口和电源解决方案进行设计

IOH: Getting started with IOH in custom projects Introduction Adding IOH functionality to a custom project is not difficult, but does involve a few important steps. These steps are explained in more detail on this page. Since the implementation of most of the steps are IDE dependant, details for each supported IDE (LPCXpresso, Keil MDK, IAR EWARM) are given on seperate pages.   Steps in general In general, the following steps should be followed when using an IOH library in a custom project: 1. Add the IOH library (*.lib, *.a) to the project. 2. Add the path where the library's header file resides to the project’s include path. 3. #include the IOH header file in the source code of the application. 4. Configure the linker to place the IOH related sections in the IOH SRAM using our provided linker scripts (for LPCXpresso this step is performed automatically when an IOH enabled device is selected). 5. Enable the IOH SRAM (SRAM1) before C-library initialization (startup/system_init code). 6. Interact with IOH via the library's API.   Detailed instructions per IDE For more detailed, per IDE instructions, visit the pages below: LPCXpresso Keil MDK IAR EWARM

示例 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 模块发送信号，触发长 * 功能重置。 ******************************************************************************** * 测试硬件：MPC57xx * 掩模组：1N65H * 目标：internal_FLASH * Fsys: 200 MHz PLL，带 40 MHz 晶振参考 ******************************************************************************** 修订历史： 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 模块发送信号，触发长 * 功能重置。 ******************************************************************************** * 测试硬件：MPC57xx * 掩模组：1N65H * 目标：internal_FLASH * Fsys: 200 MHz PLL，带 40 MHz 晶振参考 ******************************************************************************** 修订历史： 1.0 2014年10月22日 b21190（Vlna Peter）初始版本 1.1 2015 年 3 月 24 日 b21190（Vlna Peter）添加 SWT 长重置 ********************************************************************************************/ 概述

IOH: Getting started with the example projects Introduction The IOH application examples provide a great and easy way to get started with I/O Handler. All provided IOH examples come with project files for LPCXpresso, Keil MDK and IAR EWARM. This page will give an overview on how to start exploring these examples. 1. Download the full IOH kit The first step is to download the full IOH kit. This kit contains: The IOH libraries. For every library one application note describing the library and the example application(s). One or more application example projects Download the full IOH kit attached Unzip the archive to e.g. C:/nxp/ 2. Open the project in the IDE The second step is opening the projects into the IDE. LPCXpresso: 1. Choose 'File'->'Import'. Then select 'General'->'Existing Projects into Workspace' 2. Select 'Select archive file' and click 'Browse'. Select the file 'lpcxpresso_nxp_lpcxpresso_11u37h.zip' which is in the unzipped folder       (e.g. C:/nxp/nxp_lpcxpresso_lpc11u37h_ioh/lpcxpresso_nxp_lpcxpresso_11u37h.zip) 3. Import all project into the workspace by clicking 'Finish'. Note: You may also choose to only import a selected number of projects. In that case, always                     make sure you import at least three project:      'lpc_chip_11uxx_lib', 'nxp_lpcxpresso_11u37h_board_lib' and the example project of interest. Keil MDK: In Keil, open the multi-project workspace located at: nxp_lpcxpresso_lpc11u37h_ioh\applications\lpc11xx\keil_uvision_projects\nxp_lpcxpresso_11u37h\nxp_lpcxpresso_11u37h_ioh_examples.uvmpw IAR EWARM: In IAR, open the multi-project workspace located at: nxp_lpcxpresso_lpc11u37h_ioh\applications\lpc11xx\iar_ewarm_projects\nxp_lpcxpresso_11u37h\nxp_lpcxpresso_11u37h_ioh_examples.eww 3. Building the project After successfullt importing the project into the IDE, the project can be build. LPCXpresso: Select the example project of interest and click the 'Build' icon. The chip and board project will be automatically be compiled. Keil MDK: 1. Right-click on the example of interest in the project explorer and select 'Choose as Active Project'. 2. Click 'Project'->'Batch Build...'. Select atleast the 'lib_lpc_chip_11uxx', 'lib_lpc_board_nxp_lpcxpresso_11u37h' and the project of interest. 3. Click 'Build'. IAR EWARM: 1. In the project explorer, select the project of interest from the drop-down list to make that project the active project. 2. Click 'Project'->'Batch build...' and then click 'Edit'. Select atleast the 'lib_lpc_chip_11uxx', 'lib_lpc_board_nxp_lpcxpresso_11u37h' and the project of interest as 'Configurations to build'. When done, press 'OK'. 3. Click 'Make'. Important: IAR EWARM may require an update and a patch. If this condition is not met, compilation (linking) will result in an 'internal error' message from the IAR linker. Please make sure you're running 6.70.1.5794 or higher and that you have installed the 'EWARM linker patch 6.70.2-5901'. Please check your IAR mypages for any available updates. 4. Flashing the binary into the board LPCXpresso: 1. Connect a USB cable to J6 of the LPC11U37H board. J6 is the Link-2 USB connector, which allows LPCXPresso to access the LPC11U37H target for programming and debugging. 2. Click the 'Debug' icon to launch a debug session. 3. click the 'Resume' icon to start code execution. Keil MDK: 1. Either: Configure the Link2 as CMSIS DAP/J-Link (click here for more details) and connect a USB cable to J6 of the LPC11U37H board. J6 is the Link-2 USB connector. Connect a supported external debugger to P1 2. Click the 'Load' icon in Keil to download the compiled binary into the board. 3. After download has finished, hit the reset button to run the example. IAR EWARM: 1. Either: Configure the Link2 as CMSIS DAP/J-Link (click here for more details) and connect a USB cable to J6 of the LPC11U37H board. J6 is the Link-2 USB connector. Connect a supported external debugger to P1 2. Click the 'Download and Debug' icon in IAR to download the compiled binary into the board and to start a debug session. 3. After download has finished, click the 'Go' icon to start code execution.

Session 9: Light Weight ADC Driver This video presentation is the ninth installment of the Essentials of MQX RTOS Application Development training course. In this session, you will be introduced to the LWADC Driver, and will learn to configure and read ADC input. This training was created by Embedded Access Inc., a Freescale sponsored training provider and proven partner. Session 9 Course Line Lab Outline Analog signals and uses cases for ADCs How ADCs work Driver walk through Attributes of ADCs Configuring ADCs Reading the ADC Scaling the ADC output Initializing an ADC device Initializing an ADC input Reading an ADC input Scaling an ADC reading Reading an average of the ADC input First, watch the video for Session 9: LWADC Driver​. Then, follow through with the interactive lab assignment below. SESSION 9: LAB ASSIGNMENT INTRODUCTION In our previous lab we used a light weight timer to set an event bit every 100 msec and whenever this event bit was set the Input Task would send a message to the Health Task with the reading from the potentiometer. The problem however was that we hadn't yet covered the ADC and so the potentiometer value sent was 0.Now that you know how to initialize an ADC device and it's input it's now time to update this part of our application to include the actual potentiometer value in the message that is sent by the Input Task. OBJECTIVE The objective of this lab is to learn about the lwadc driver by adding code to read the potentiometer and send the value to the health task.This objective will be accomplished by: Initializing the ADC driver Initializing the ADC input Periodical reading of the ADC Changing the scaling so a voltave between 0 and 12000 millivolts is displayed Using _lwadc_read_average New functions/ structures you will use:      LWADC_STRUCT, LWADC_VALUE, __lwadc_init(), _lwadc_init_input(), _lwadc_read(),_lwadc_set_attribute(),_lwadc_read_average() ASSIGNMENT INITIALIZE THE INPUT We saw in the video that there is a separate structure of type LWADC_INIT_STRUCT for each of the ADC Devices. These are located in init_lwadc.c which is in the 'BSP_Files' folder of the BSP project. It would be a good idea to review this file to get familiar with this structure. Just below where you initialized the switches (with the init_switch() function) in InitTask.c use the lwadc_init() function to initialize ADC 1. ADC 1 will be used because the potentiometer is connected to ADC 1 on the tower K70 board. We'll see this in a moment. ADC 1 is the default ADC controller in this BSP and there is a define for this in the board specific BSP file (twrk70f120m.h) called BSP_DEFAULT_LWADC_MODULE. So you can use this define to point to the ADC1 init structure or more directly use 'lwadc1_init'. Note that the extern for BSP_DEFAULT_LWADC_MODULE is missing in some versions of MQX so you may need to add an 'extern const LWADC_INIT_STRUCT BSP_DEFAULT_LWADC_MODULE' at the top of InputTask.c. This will initialize the ADC device but the next step is to initialize the data structure for the input to this ADC Device. This is done with the lwadc_init_input() function. Don't forget to declare a structure of type LWADC_STRUCT. As with all inputs, you will find in twrk70f120m.h, a define for the ADC input from the potentiometer. It is called BSP_ADC_POTENTIOMETER and it is set it to (ADC1_SOURCE_AD20). This defines the ADC Device that it is connected to and the pin muxing. READING THE INPUT Now we're ready to read the input. You will recall that in the endless loop of our Init Task it will wait indefinitely for either a switch or ADC event bit to be set, and once one of these bits has been set the appropriate action is taken. We added the setting of the ADC event bit in the last lab with the use of a timer. Currently when this bit is set the Input Task will send a message to the Health Task but we don't have any real data to send so our job is to add that data now. Before sending the message the Input Task should use the _lwadc_read() function to get the setting of the potentiometer. You will need a variable of type LWADC_VALUE for the reading from the ADC to be written to. Update the data field in the message to the Health Task to be the read value from the ADC. Since the _lwadc_read() function returns TRUE if the read is successful and FALSE if the read was unsuccessful it would make sense to update your code to only send a message if the read from the ADC was successful. TEST THE ADC Compile and run your code. On the print out you should see the Health Task and Display Task message ADC messages being displayed continuously (officially once every 100 msec because that's the period of our timer that triggers the reading of the ADC). If you change the setting of the potentiometer on the K70 tower card the value printed out should change and the readings should range from 0 (or close to it) to 3300 (or close to it) to represent 3300 millivolts. CHANGING THE SCALING AND READING METHOD As you saw the input wasn't scaled at all, it simply showed you the voltage (in millivolts) that the ADC was reading. But you may want to scale the input to a range that is more meaningful. Instead of having the input range from 0 to 3300 we want to scale this so it ranges from 0 to 12000. This could represent a temperature that goes up to 1,200 degrees (in tenths of a degree) or a voltage range that goes up to 12 volts (measured in millivolts). Use the _lwadc_set_attribute() function to change the scaling. Try this on your own, if you need a hint use the whiteboard. Change the reading of the ADC to return an average value over 8 reads. This requires the _lwadc_read_average() function. TESTING THE SCALING Compile and run your code. Confirm on the output that the range of the potentiometer is now from 0 to 12000. Need more help? The full source code for this lab can be found in the 'Lab Source Code' folder here​.

AMF-INS-T2024 - Semiconductor 101/102: Functionality and Manufacturing of Integrated Circuits Many people involved in the electronics industry need a basic knowledge of semiconductor components in order to understand issues like manufacturing cycle time, semiconductor fab consolidation and failure analysis results. This session is geared towards a non-technical audience and gives a high-level overview of semiconductor devices and how they are made. The lecture begins with a brief overview of how semiconductor devices work. The bulk of the presentation describes the generic manufacturing flow for semiconductor devices with an emphasis on the complexity of the equipment/facilities used and the process time required. Many people involved in the electronics industry need a basic knowledge of semiconductor components in order to understand issues like manufacturing cycle time, semiconductor fab consolidation and failure analysis results. This session is geared towards a non-technical audience and gives a high-level overview of semiconductor devices and how they are made. The lecture begins with a brief overview of how semiconductor devices work. The bulk of the presentation describes the generic manufacturing flow for semiconductor devices with an emphasis on the complexity of the equipment/facilities used and the process time required.

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.

AUT-N1786 ADASブルーボックス開発の異種ツールランドスケープの探索 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPは、ADAS開発のための最先端のハードウェアおよびソフトウェアツールを提供しています。ソフトウェアアルゴリズムの開発者は、困難な場合がある異種ツール環境に遭遇します。このセッションでは、ADASアルゴリズム開発のためのNXPのイネーブルメント製品について説明し、これらのツールを使用してBlue Boxのセンサ入力データパスを実装する方法について説明します。このセッションでは、AUTOSARドライバ、S32V上のコア間通信とPCIe、LS2ルートコンプレックスドライバ、重要な安全データのLS2 Linuxデータ管理など、ヘテロジニアスツールのランドスケープを確認します。参加者は、ADAS開発でNXPのツールを活用する方法を明確に把握できます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPは、ADAS開発のための最先端のハードウェアおよびソフトウェアツールを提供しています。ソフトウェアアルゴリズムの開発者は、困難な場合がある異種ツール環境に遭遇します。このセッションでは、ADASアルゴリズム開発のためのNXPのイネーブルメント製品について説明し、これらのツールを使用してBlue Boxのセンサ入力データパスを実装する方法について説明します。このセッションでは、AUTOSARドライバ、S32V上のコア間通信とPCIe、LS2ルートコンプレックスドライバ、重要な安全データのLS2 Linuxデータ管理など、ヘテロジニアスツールのランドスケープを確認します。参加者は、ADAS開発でNXPのツールを活用する方法を明確に把握できます。 セキュアなコネクテッド&自動運転車

TN004_add Criterion for Valid User Code into HEX .docx

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 双核设备上的汽车仪表盘。 设计 | 软件与服务

Getting started with LPCOpen: Running the demo applications Hello community!   Attached is a document that explains the steps to use LPCXpresso with the LPCOpen projects for your preferred device and platform. The steps described in the document were done using the LPC54102 MCU like the one in the LPCXpresso Board for the LPC54100 family of MCUs, but the same principles are applicable to any LPC MCU. The steps described in this document are valid for the following versions of the software tools: o    LPCXpresso v8.1.4 o    LPCOpen v3.xx Contents 1. Overview and concepts    1.1    LPCOpen       1.1.1 Core driver library       1.1.2 Middleware       1.1.3 Examples       1.1.4 Using LPCOpen with an RTOS 2. Running the demo applications    2.1 Downloading a LPCOpen package    2.2 Importing the LPCOpen examples    2.3 Building and debugging blinky project Appendix A - References I hope you can benefit from this post, if you have questions please let me know.   Best Regards! Carlos Mendoza General

AUT-N1786 Exploring the Heterogeneous Tool Landscape of ADAS Blue Box Development NXP supplies cutting edge hardware and software tools for ADAS development. The software algorithm developer will encounter a heterogeneous tool environment that may prove to be challenging. In this session, we will walk through NXP's enablement offerings for ADAS algorithm development and explain how to use these tools to implement a sensor input data path for Blue Box. This session will review the heterogeneous tool landscape, including AUTOSAR drivers, Inter-Core Communication and PCIe on S32V, as well as LS2 Root Complex Driver and LS2 Linux data management of critical safety data. Attendees will leave with a clear picture of how to leverage NXP's tools in ADAS development. NXP supplies cutting edge hardware and software tools for ADAS development. The software algorithm developer will encounter a heterogeneous tool environment that may prove to be challenging. In this session, we will walk through NXP's enablement offerings for ADAS algorithm development and explain how to use these tools to implement a sensor input data path for Blue Box. This session will review the heterogeneous tool landscape, including AUTOSAR drivers, Inter-Core Communication and PCIe on S32V, as well as LS2 Root Complex Driver and LS2 Linux data management of critical safety data. Attendees will leave with a clear picture of how to leverage NXP's tools in ADAS development. Secure Connected & Automated Vehicles

AFT09MS031N、AFT05MS031N 在 Tetra 和 DMR/dPMR 中的应用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 回复：AFT09MS031N、AFT05MS031N 在 Tetra 和 DMR/dPMR 中的应用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 亲爱的，我使用了非线性ADS模型AFT05MS031N射频功率晶体管，首先我根据数据表绘制了380-450MHz的推荐电路，其微带线、元件值以及提到的PCB基板数据完全相同，但模拟输出功率远低于数据表声称的28瓦，而且完全是非线性的！（我在相同和不同的偏置条件下进行了测试） 因此，我自己设计，模拟显示 P-1dB 约为 16 瓦，然后我在 PCB 板上构建它，但 CW 测试显示 P1dB 要低得多（约 2 瓦）！ 我的问题是，您确定这个晶体管的 ADS 模型吗？您用它做过设计吗？以及数据表推荐的电路值吗？ 谢谢。

i.MX_6SoloX 多核编程入门.pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Linux 3.14.52_1.1.0 多核编程指南以及适用于 i.MX 6SoloX 的 FreeRTOS BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Linux 3.14.52_1.1.0 多核编程指南以及适用于 i.MX 6SoloX 的 FreeRTOS BSP i.MX6SoloX

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

FTF-ACC-F1112.pdf S32 Design Studio for ARM is a hands-on training with the new Eclipse-based tool chain with C development tools in the integrated development environment including editor, compiler, and debugger support of Freescale's latest automotive ARM-based MCUs. Participants will learn about the project creation, editing, compiling, Processor Expert configuration tool, and debugging of a small example project under the direction of one of Freescale's tools experts. The class will focus on the Freescale KEA MCUs with the highly-integrated, easy-to-use tool chain. The student will start with a project from scratch, work through new project creation, configuration of the compiler, compilation, flashing executable onto the target MCU and complete the class with debugging the project on the target MCU evaluation board. S32 Design Studio for ARM is a hands-on training with the new Eclipse-based tool chain with C development tools in the integrated development environment including editor, compiler, and debugger support of Freescale's latest automotive ARM-based MCUs. Participants will learn about the project creation, editing, compiling, Processor Expert configuration tool, and debugging of a small example project under the direction of one of Freescale's tools experts. The class will focus on the Freescale KEA MCUs with the highly-integrated, easy-to-use tool chain. The student will start with a project from scratch, work through new project creation, configuration of the compiler, compilation, flashing executable onto the target MCU and complete the class with debugging the project on the target MCU evaluation board.

Technical Report Roznovaci.pdf The Freescale Cup High School challenge technical report from team Roznovaci from Stredni Skola informatiky, Elektrotechniky a Remesel Roznov (Czech Republic) The Freescale Cup High School challenge technical report from team Roznovaci from Stredni Skola informatiky, Elektrotechniky a Remesel Roznov (Czech Republic)