University Programs Knowledge Base

Discussions

Official rules of the USA Regional Freescale Cup! New in 2014 - Roll-out of leagues: Depending on region there will now be three leagues. To advance to the Global race you must use stock league vehicles. Stock League - Race using approved components, less customization allowed Custom League - Race with less restrictions and custom hardware Innovation League - More than just racing. Complete an objective or task to score points and win. (Scheduled 2015 for USA) Notes You can view this document in PDF format using the Action Menu bar. The Worldwide challenge is only open to the stock (unmodified) challengers at this time. A team may run in both leagues, but the car must comply accordingly. If you have ANY questions about these rules, post them in the comments section below. If you have questions about regional rules, ask in your regional group. Section 1: Team Requirements Four person maximum team size. A team may have only one graduate student. Cars will be designed and constructed by students ONLY. Participants, advisers, and audience are expected to exhibit good sportsmanship. Any inappropriate behavior or cheating may result in disqualification. Section 2: Event Registration One person from the team must register the entire team for the worldwide challenge no later than January 31st. Section 3a: STOCK LEAGUE - Equipment Requirements Each team shall use the same basic kit of parts as described below. The following requirements are in place to keep the playing field level. You must use one of the approved controller and motor driver boards. If any standard component of the car model is damaged, then the same replacement component should be used. Mechanical The original and unaltered equipment must be used in the entry. Outer tire treads and rim Drive - DC motors Transmission Ratio of Drive Motor Servo Motor Allowed modifications and restrictions: You may not change the wheel base (distance between wheels) No part of the car shall exceed dimensions of 250mm/9.85in (W) x 400mm/15.75in (L)x 305mm/12in.(H) You may drill holes and mount auxiliary pieces on the chassis assuming it is contained within the above dimensions. You may change the orientation of the servo motor and related linkages. You may add a "skin" to the car but it must be removable during inspection. You may adjust or remove springs, linkages, and other non-essential pieces. You may adhere the tread to the rim. Electrical Battery (purchase separately) 7.2V, <=3000mAh, rechargeable NiCd or NiMH Only one (1) battery at a time may be used to power the vehicle and any attached hardware You must use one of the approved boards below to control your car. Control System FRDM- series of boards The FRDM-KL25Z is included but not mandatory to use. TRK- series Kinetis based TWR- series High Voltage Motor Control and Interface TFC-SHIELD The TFC-SHIELD is included but not mandatory to use. The Dual Motor Control Board from Landzo technologies. Allowed modifications and restrictions: One processor - No auxiliary processor or other programmable device is allowed. The car must use a optical sensor to navigate DC-DC boost circuit may not exceed battery voltage. Total capacity of all capacitors should not exceed 2000 uF. Sensor Limits You may use additional cameras. Maximum of sixteen (16) sensors Examples of sensor count: IR Transmitter/Receiver pair is 1 sensor A CCD sensor is 1 sensor The provided Line Scan Camera is 1 sensor A hall effect sensor on two rear wheels is 2 sensors An encoder mounted on one wheel is 1 sensor A display (is allowed) does not count as a sensor Section 3b: CUSTOM LEAGUE - Equipment Requirements The custom league allows for greater customization of the vehicle. There is still a set of standard components that must be used. If any of the standard component of the car model is damaged, then the same replacement component should be used. Mechanical The original and unaltered equipment must be used in the entry. Outer tire treads and rim Drive - DC motors Transmission Ratio of Drive Motor Servo Motor Allowed modifications and restrictions: You may not change the wheel base (distance between wheels) No part of the car shall exceed dimensions of 250mm/9.85in (W) x 400mm/15.75in (L)x 305mm/12in.(H) You may drill holes and mount auxiliary pieces on the chassis assuming it is contained within the above dimensions. You may change the orientation of the servo motor and related linkages. You may add a "skin" to the car but it must be removable during inspection. You may adjust or remove springs, linkages, and other non-essential pieces. You may adhere the tread to the rim. Electrical Battery (purchase separately) 7.2V, <=3000mAh, rechargeable NiCd or NiMH Only one (1) battery at a time may be used to power the vehicle and any attached hardware Allowed modifications and restrictions: One Freescale processor to control everything- No auxiliary processor or other programmable device is allowed. You may build your own controller board and/or high-voltage (motor) driver board. The car must use a optical sensor to navigate DC-DC boost circuit may not exceed 12V. Total capacity of all capacitors should not exceed 2000 uF. Sensor Limits You may use additional cameras. Maximum of sixteen (16) sensors Examples of sensor count: IR Transmitter/Receiver pair is 1 sensor A CCD sensor is 1 sensor The provided Line Scan Camera is 1 sensor A hall effect sensor on two rear wheels is 2 sensors An encoder mounted on one wheel is 1 sensor A display (is allowed) does not count as a sensor Section 4: Vehicle Inspection Before the race, the judges will perform a technical inspection of all entries. This includes vehicle specifications, dimensions, and equipment requirements listed in Section 3. All cars must be placed in the Inspection area on or before the designated time. Once in the Inspection Area, you may not touch car until you are called to race! In the event of any violations, the organizing committee may disqualify the corresponding team. Section 5: Timed Race Procedure Race order will be determined by a random drawing. When your team is called you may remove your car from inspection area. You will have two (2) minutes to prepare the car. Approved Adjustments - You may: Configure parameters via on-board interfaces. (Switches, Knobs, etc.) Alter the angle of your camera Change batteries Disallowed Adjustments -You may not: Reprogram your processor Configure parameters via wired or wireless communications. There shall be only one team member on the track at any given time. (excludes testing times) Before the 2 minute expires you must signal “Ready” to the referee before starting car. After the referee confirms “Ready”, the vehicle should leave the starting area within 30 seconds. Teams have THREE attempts to complete ONE lap. The FIRST (not the best) completed time will be recorded. Example: Attempt 1 – Vehicle goes to fast around a curve and goes off track. Time is not recorded. Attempt 2 – Vehicle makes it around track successfully. Time is recorded. Attempt 3 – Is forfeit because FIRST time (Attempt 2) has been recorded. After each attempt you have two minutes to make approved (see above) adjustments to vehicle. After the attempts, the team shall return the vehicle to inspection area. Event displays will post the times after each team races. Section 6: Race Day Schedule Practice Time - Prior to final race, a test track will be available. Final calibration may be made at this time. This will be organized with team slots and/or “free-time”. 2. Reconfigure practice track to final track. Vehicle Inspection (see section 4) Timed Race Awards Ceremony Section 7: Event Personnel Organizing committee – A committee of senior judges and Freescale event organizers. Will coordinate event day activities and mediate and resolve any disputes. Referees - Responsible for on-track activities. This includes race track management such as starting and stopping vehicles, as well as timing and scorekeeping. Comprise up of of faculty, student, and/or Freescale and industry employees. Judges - Interpret and enforce rule compliance. This will be comprised of Freescale employees and members of contributing industry sponsors. Event Personnel shall not aid any one specific team. Communication shall be open to all teams and shall not disclose any information that might compromise the fairness of the competition. Section 8: Fouls, Failure and Disqualifications The rules will be interpreted by Freescale and the organizing committee of the event. Foul, is a minor infraction, which results in time penalties. Failure, results in the current attempt time not being recorded. Subsequent attempts are allowed. Disqualification is a major infraction which results all times not being recorded. Referee will determine whether the racing car ran out of the race track and assign time penalties. Any of the following conditions will be considered a foul and will result in time penalty added: The race car fails to leave the starting area within 30 seconds after beginning of the race [+1 second]. The race car fails to stop 2 meters/6 feet or leaves the track after crossing the finish line [+1 second]. Any of the following conditions will be considered a failure and no time will be given: Three or more wheels leave the race surface. The racing team fails to get prepared for the attempt within the two (2) minutes allotment. The player touches the race car after the technical inspection without consent of the referee. The race car fails to finish within 120 seconds after leaving the starting area. Touching the car at any time between start and finish. "Start" - Once the vehicle crosses the starting line. "Finish" - Once the vehicle crosses the finish line. Any of the following conditions will be considered a disqualification: Any off track equipment or behavior that may influence or impede cars. Doing a Disallowed Modification anytime after Inspection. More than one team member in the playing field. Any cheating during the competition. Failure to pass the technical inspection. Equality and fairness will be ensured as much as possible on the condition of actual feasibility. Disputes will be resolved by a vote of Freescale, members of the organizing committee, and judges. Section 9: Timing/Scoring Time will be captured using an electronic gate and/or handheld timer. Time starts and ends when the first part of the racing car breaks the start/finish line. Fouls will result in the time addition to the car’s lap time. Disqualifications and Failures will result in no score. Section 10: Parameters of the Racing Track A test track made from the same material as the final track will be made available on the day prior to the final race for calibration and design modifications. The actual layout of the final racing track will be unknown to competitors until competition day. Width of the racing track shall not be less than 600mm/24in. Material and dimensional specifications can be found on the community. Surface of the racing track is matte white, with a continuous black line (25mm/1in wide) in the center of the track. The racing track can intersect with a crossing angle of 90°. The racing track can have inclines, declines, and tunnels. The rules and conditions are subject to change by Freescale if necessary. Freescale reserves the right in their sole discretion to cancel, suspend and/or modify The Freescale Cup race at any time. These official rules are drawn up in the English language. If these official rules are provided in any other language and there is a conflict in the text, the English language text shall prevail. Freescale and the Freescale logo are trademarks or registered trademarks of Freescale Semiconductor, Inc. in the U.S. and other countries. All other product or service names are the property of their respective owners. © Freescale Semiconductor, Inc. 2014

This tutorial covers the details of Driving a motor on the on the Kinetis K40 using the TWR-K40x256-KIT evaluation board. Overview In this exercise students will utilize the sample project to turn a motor on and off using the TWR-K40x256-KIT evaluation board. Students will: Put together the car chassis Create a Sample Project Build the code Download and run the code on a Kinetis TWR-K40x256 board. Learn how the code works To successfully complete this exercise students will need the following board and development environment. Kinetis TWR-K40x256 board Motor Driver Board Freescale Cup Chassis with the Motors connected 7.2v Nicad Battery CodeWarrior for Microcontrollers Recommend completing the the Blink LED Tutorial before undertaking this Tutorial Put together the Car Chassis: There are several steps in this process: Build the Freescale Cup Car Chassis Hardware Design Step Review the Driving A DC Motor Article If needed, obtain background information on motors, timer modules, PWM signals and counters by navigating to the driving a DC motor article. Design and Implement The Hardware 1. You will need to connect the Tower K40 to the Motor Board via the TWR-PROTO or some other mechanism. 2. You will need to connect the Motor Board to the DC motors and Battery This link shows a video of the motors spinning. They start from Off and slowly pick up speed http://www.youtube.com/watch?v=kY2bRiICzwc&feature=relmfu Motor Controller Board This board takes the low-voltage, low-power "control" signals from the MCU and through an H-Bridge takes ahigh-voltage, high-power power supply (the battery) to drive the motors. Motor Board page. 1. Be careful with the wires connected to the motor. Constant flexing of the solder connection can result in joint failure. If this happens, just re-solder it. 2. The wires which protrude from the motors of The Freescale Cup Chassis are in the format of Insulated Crimp On Bullet Connectors. These can be found at Radio Shack if they are missing from the kit. Build the Code If you have more than one project in your project view, make sure the proper project is the focus. The most reliable way to do this is to right click the project and choose Build Project as shown below. You can also go to the Project menu and choose the same command. Learning Step: Motor Code Description Functions Variables The edge-aligned mode is selected when (QUADEN = 0), (DECAPEN = 0), (COMBINE 0), (CPWMS = 0), and (MSnB = 1). The EPWM period is determined by (MOD − CNTIN + 0x0001) and the pulse width (duty cycle) is determined by (CnV − CNTIN). The CHnF bit is set and the channel (n) interrupt is generated (if CHnIE = 1) at the channel (n) match (FTM counter = CnV), that is, at the end of the pulse width. This type of PWM signal is called edge-aligned because the leading edges of all PWM signals are aligned with the beginning of the period, which is the same for all channels within an FTM. Initialize the Motor void InitMotorPWM() { //Enable the Clock to the FTM1 Module SIM_SCGC6 |= SIM_SCGC6_FTM1_MASK; // PORTC_PCR4 = PORT_PCR_MUX(1) | PORT_PCR_DSE_MASK; //Enable GPIO on on the pin - //route the output of that channel 0 to the pin... (pick a different multiplexer value for routing the timer) //ch 11.4.1 of the k40 reference manual is the pin control register //For port c pin 1.. bits 10-8 Pin Mux Control... PORTA_PCR8 = PORT_PCR_MUX(3) | PORT_PCR_DSE_MASK; PORTA_PCR9 = PORT_PCR_MUX(3) | PORT_PCR_DSE_MASK; // Choose EDGE-Aligned PWM: selected when QUADEN=0, DECAPEN=0, COMBINE=0, CPWMS=0, and MSnB=1 (page 964) // Properly set up Flex Timer Module //FTM0_MODE[WPDIS] = 1; //Disable Write Protection - enables changes to QUADEN, DECAPEN, etc. FTM1_MODE |= FTM_MODE_WPDIS_MASK; //FTMEN is bit 0, need to set to zero so DECAPEN can be set to 0 FTM1_MODE &= ~1; //Set Edge Aligned PWM FTM1_QDCTRL &=~FTM_QDCTRL_QUADEN_MASK; //QUADEN is Bit 1, Set Quadrature Decoder Mode (QUADEN) Enable to 0, (disabled) //FTM0_SC = 0x16; //Center Aligned PWM Select = 0, sets FTM Counter to operate in up counting mode, //it is field 5 of FTMx_SC (status control) - also setting the pre-scale bits here // Also need to setup the FTM0C0SC channel control register - Page 897 section 37.3.6 FTM1_CNT = 0x0; //FTM Counter Value - (initialize the CNT before writing to MOD) (16 bit available - bits 0-15 are count) FTM1_MOD = FTM1_MOD_VALUE; //Set the Modulo resister (16 bit available - bits 0-15), Mod is set to 24000 FTM1_CNTIN = 0; //Set the Counter Initial Value to 0 (pg 915) //change MSnB = 1 FTM1_C0SC |= FTM_CnSC_ELSB_MASK; FTM1_C0SC &= ~FTM_CnSC_ELSA_MASK; FTM1_C0SC |= FTM_CnSC_MSB_MASK; FTM1_C0V = FTM1_MOD_VALUE/2; //Set the Channel n Value to (16 bit available - bits 0-15) //Set the complimentary pinout FTM1_C1SC |= FTM_CnSC_ELSB_MASK; FTM1_C1SC &= ~FTM_CnSC_ELSA_MASK; FTM1_C1SC |= FTM_CnSC_MSB_MASK; FTM1_C1V = FTM1_MOD_VALUE/2; FTM1_SC = FTM_SC_PS(0) | FTM_SC_CLKS(1); // Interrupts FTM1_SC |= FTM_SC_TOIE_MASK; //enable the interrupt mask enable_irq(63); // (79-16) Set NVIC location, but you still have to change/check NVIC file sysinit.c under Project Settings Folder } Set the PWM of the Motor void SetMotorPWM(float DutyCycle) { //float compDuty = (float)100.0-DutyCycle; FTM1_C0V =(int)((DutyCycle*.01)* (float)FTM1_MOD_VALUE); FTM1_C1V =(int)((1.0-DutyCycle*.01)* (float)FTM1_MOD_VALUE); } Create Interrupt when motor functions are complete void MotorTick() { if (MotorTickVar < 0xff)//if motor tick less than 255 count up... MotorTickVar++; //Clear the overflow mask if set if(FTM1_SC & FTM_SC_TOF_MASK) FTM1_SC &= ~FTM_SC_TOF_MASK; //LED_E2_TOGGLE; // ends up being ___ Hz (correct) } Calling the Motor function The function SetMotorPWM(MotorPwm) turns the motor at the "MotorPwm" rate from 0-49 (backwards), 50 (stall) and 100 (forwards).

Summary This page contains the technical information for the FRDM-OLED shield. This includes the schematics, bill of materials (BOM), gerber files and raw design files. Main features: Newhaven NHD-2.7-12864UCY3 128x64 pixel graphic OLED Display Electret microphone interface with gain control RS-485 Interface for doing cool things like driving a DMX lighting system. General purpose I/O (I/O is shared with A/D pins so you could make your own scope!) Example software, video tutorials tutorials, cool demos, etc are location on the page for MonkeyListen project page located here. Notes: You can order PCBs through OSHPark or your favorite board house. There is a special .zip file with files ready to go for OSHPark (using their preferred naming convention). There is a complete design package which has the raw design files (Altium Designer Format) as well as gerbers, a bill of materials, assembly plots etc. Look in the "BUILD_PACKAGE" folder for the stuff needed to make the board. A PDF Schematic is also provided for easy reference. If you are interested in a low cost pre-fabbed board or a fully assembled version, please leave a comment. A kickstarter project may follow to get a bunch built!

MCU 101 - Beginners Concepts https://community.nxp.com/docs/DOC-1241 Blink LED Drive a DC Motor Turn a Servo Line Scan Camera Glossary of Terms Software Tools CodeWarrior Software Development Tools & IDE (recommend you download the Special Edition) CodeWarrior Beginners Tutorial (videos) TWR K40X256 Hardware setup Creating a new bareboard project Debugging a bareboard project Importing projects and merging code Discussion of the header files (part 1) Discussion of the header files (part 2) (Code) Beginners Hands-on Tutorials Introduction to Microcontroller Programming Blink LED Drive DC Motor Turn A Servo LIne Scan Camera Sample Codes LED BLINK 96MHZ Hardware DIY Tower System Mounting DIY Camera Mounting Batteries Advanced Tutorial Series Push-Buttons https://community.nxp.com/docs/DOC-1034 Miscellaneous Topics Reading a Reference Manual PCB design tips

This tutorial covers the details of Driving a motor on the Qorivva TRK-MPC5604B: MPC5604B StarterTRAK evaluation board. Overview 1. Put together the Car Chassis: Motor Controller Board Version A. 2. Import the Sample Project 3. Build the Code 4. Download/Debug/Run 5. Learning Step: DC Motor Code Description Functions Motor_Right () & Motor_Left() Motor_Right_Current () & Motor_Left_Current() Sample Code Download Link Alternative Examples: Other Qorivva Tutorials: Useful Technical Links Overview In this exercise students will utilize the sample project to turn a DC motor on an off using the Qorivva TRK-MPC5604B board. Students will: Put together the car chassis Open the Sample Project Make changes to main.c to call the motor functions Build the Motor function code Download and run the code on a Qorivva TRK-MPC5604B board. Learn how the code works To successfully complete this exercise students will need the following board and development environment. Qorivva TRK-MPC5604B board. Freescale Cup Chassis (connector for the motor/board) Motor Drive Version A board Kit Cables and interconnects 7.2v Nicad Battery CodeWarrior for Microcontrollers V2.8 Recommend completing the the Blink LED Tutorial Motor Example code 1. Put together the Car Chassis: There are several steps in this process: Build the Freescale Cup Car Chassis Add the Qorivva-Mpc560xb version components to the chassis The first step of this tutorial is to gain background information on background information on motors, timer modules, PWM signals and counters. To learn more about these general topics read the Drive A DC Motor overview article. You will need to connect your motor to the microcontroller via the Motor Drive board. This board is connected to the battery, and serves to power the motors. separate power source. This is an easy process using the provided Motor Controller Board. Motor Controller Board Version A. The Freescale Cup Motor Drive VA board uses the following connector type: white 3 pin connectors (for motor) (Molex 3-pin .100") white 2 pin connector (for battery) (Molex 2-pin .100") Schematics Wiring Connections for the TRK-MPC5604B 2. Import the Sample Project The next step is to import an existing project into your Workspace. in this case, the TRK-MPC5604B Sample project. Follow the instructions on the codewarrior project import page if you can't remember how to to import the project into CodeWarrior. 3. Build the Code If you have more than one project in your project view, make sure the proper project is the focus. The most reliable way to do this is to right click the project and choose Build Project as shown below. You can also go to the Project menu and choose the same command. If you encounter errors, look in the Problems view and resolve them. You can ignore any warnings. 4. Download/Debug/Run 5. Learning Step: DC Motor Code Description What will happen: This demo is setup for two motors (one left and one right). You will then independently turn on and off each motor Functions This file sets up the Pulse Width Modulation Timer Module for use by a DC Motor. It is set to utilize Edge-Aligned PWM, and this file properly configures the period, and pulse width for use by the other modules Motor_Right () & Motor_Left() void MOTOR_LEFT(void) { TransmitData("****Left Drive Motor Test****\n\r"); SIU.PCR[16].R = 0x0200; /* Program the drive enable pin of Left Motor as output*/ SIU.PGPDO[0].R = 0x00008000; /* Enable Left the motors */ Delaywait(); SIU.PGPDO[0].R = 0x00000000; /* Disable Left the motors */ } void MOTOR_RIGHT(void) { TransmitData("****Right Drive Motor Test****\n\r"); SIU.PCR[17].R = 0x0200; /* Program the drive enable pin of Right Motor as output*/ SIU.PGPDO[0].R = 0x00004000; /* Enable Right the motors */ Delaywait(); SIU.PGPDO[0].R = 0x00000000; /* Disable Right the motors */ } Motor_Right_Current () & Motor_Left_Current() void RIGHT_MOTOR_CURRENT(void) { TransmitData("****Right Motor Current****\n\r"); SIU.PGPDO[0].R = 0x00004000; /* Enable Right the motors */ Delaywait(); for (i=0;i <10;i++) { ADC.MCR.B.NSTART=1; /* Trigger normal conversions for ADC0 */ while (ADC.MSR.B.NSTART == 1) {}; curdata = ADC.CDR[2].B.CDATA; printserialsingned(curdata); } SIU.PGPDO[0].R = 0x00000000; /* Disable Right the motors */ } void LEFT_MOTOR_CURRENT(void) { TransmitData("****Left Motor Current****\n\r"); SIU.PGPDO[0].R = 0x00008000; /* Enable Right the motors */ Delaywait(); for (i=0;i <10;i++) { ADC.MCR.B.NSTART=1; /* Trigger normal conversions for ADC0 */ while (ADC.MSR.B.NSTART == 1) {}; curdata = ADC.CDR[1].B.CDATA; printserialsingned(curdata); } SIU.PGPDO[0].R = 0x00000000; /* Disable Right the motors */ } Sample Code Download Link Qorivva Sample Code Download Link Alternative Examples: Application Note 4251 and Software. Other Qorivva Tutorials: Qorivva: Blink a Led Tutorial Qorivva: Turning a Servo Tutorial Qorivva: Line Scan Camera Tutorial Useful Technical Links TRK-MPC5064B Freescale Webpage TRK-MPC5064B Freescale Reference Manual TRK-MPC5064B Freescale Schematic

Acronyms related to electronics and embedded systems. Can't find the term you are looking for here? Add it to the comments section below and I will research and add to this list. A ABIST-Array Built-In Self-Test ADAM-Advanced Doherty Alignment Module [a special module to do Doherty phase amplifers] ADMA-Asynchronous Direct Memory Access ADC - Analog to Digital Converter APU-Application Processor Unit AWIC-Asynchronous Wake-up Interrupt Controller B BLE or BTLE - Bluetooth Low Energy BME-Bit Manipulation Engine BOM-Bill of Materials BSP -Board support package. A group of files that are specific to a particular type of processor on a particular type of board. It includes drivers. C CAN-Controller Area Network CMSIS- Cortex™ Microcontroller Software Interface Standard CMT-Carrier Modulator Transmitter CPU-Central Processing Unit CRC-Cyclic Redundancy Check D DAC- Digital to Analog Converter DCSR-Debug configuration and status register DCU-Display Control Unit DIMM-dual in-line memory module DMA-Direct Memory Access DPA-Doherty Power Amplifier E eTPU-enhanced Time Processor Unit EWM - External Watchdog Monitor F FPGA-Field programmable gate array FPU-Floating Point Unit FRAM-Ferroelectric Random Access Memory FSM-Finite State Machine FTM-Flexible Timer Module G-H GPIO - General Purpose Input/Output HID-[USB] Human Interface Device HMI - Human Machine Interface I I2C-Inter Integrated Circuit I2S -Inter-IC Sound IDE-Integrated Development Environment IFC-Integrated Flash Controller IFTT-Inverse Fast Fourier Transform ICE-In-circuit emulator J-L JTAG - Joint Test Action Group LED-Light Emitting Diode LCD-Liquid Crystal Display LVD-Low Voltage Detect M MAC-Media Access Control mbed- Cloud based IDE for rapid prototyping MCG- Multi-Clock Generation MII-Media Independent Interface MOSFET-Metal Oxide Semiconductor Field Effect Transistor MPU-Memory Protection Unit MSD-mass storage device N-O NMI-Non-maskable interrupt NVIC-nested-vectored interrupt controller NVM-Non-volatile memory OpenSDA-Open-standard Serial and Debug Adapter. P PCIe-PCI Express (Peripheral Component Interconnect Express) PEx-Short form for the Processor Expert PEG - Portable Embedded GUI PGA- Programmable-gain amplifier PIT-Periodic Interrupt Timer PMC-Power Management Controller PSP - Processor Support Package PWM-Pulse Width Modulation R RNG - Random Number Generation RoHS-Restriction of Hazardous substances RTC - Real Time Clock RTOS-Real Time Operating System RRAM-Resistive Random Access Memory S SCI-Serial Communications Interface (see also UART) SDHC - Secure Digital Host Controller SIM - System Integration Module SPI-Serial Peripheral Interface T TDM - Tamper Detection Module TPMS-Tire Pressure Monitoring System TSI-Touch Sensing Interface U-W UART - Universal asynchronous receiver/transmitter WiMAX Worldwide Interoperability for Microwave Access

This educational application by Freescale teaches you about sensor fusion and lets you experiment with some of the routines already present in your Android™ device. It does not require that your device uses Freescale sensors. The app supports 6 and 9-axis fusion routines native to your device, as well as those on compatible development boards. This app just lets you experiment with what you already have. http://www.freescale.com/webapp/sps/site/overview.jsp?code=XTRSICSNSTLBOX

Students from the University Applied Sciences TDU Deggendorf gave yesterday a demonstration of their Freescale Cup cars. 10 teams had worked during the semester in getting their cars running on their homemade Freescale Cup track based on Tower K60 kits. They ran them with lights on, lights off, in both directions on the track. Solid performance overall. HDU Deggendorf's teams are led by Prof. Gerald Kupris and have enrolled for the 3rd consecutive season into the Freescale Cup EMEA Challenge 2014. They are preparing another set of cars to compete in the upcoming racing season.

University Programs Knowledge Base

University Programs Knowledge Base

Discussions

Training Presentations.zip

2014 Freescale Cup - USA Regional Rules

freescale cup India 2011 trials

K40: Drive DC Motor Tutorial

FRDM-KL25-Sample Code.zip

TFC2015 UCDavis Team Young Tortoise Final Report

Watch The Freescale Cup EMEA Finals LIVE

FRDM-OLED

Kinetis K40 Home Page

Kinetis L - UART.pdf

TFC2015 UCDavis Team DKnight Final Report

Qorivva: Drive DC Motor Tutorial

Kinetis L - OpenSDA.pdf

The Freescale Cup 2013 Brazil Results

Freescale Cup 2011 Malaysia ~ Summary

Acronym Decoder

TFC 2016 Worldwide Rules_v1.pdf

Freescale Xtrinsic Sensor Fusion Toolbox

FTF2011 - Freescale Cup Invitational - Finals Second Place Team

TDU Deggendorf University Freescale Cup Semester End Demonstration