Producto dirigido para terapias visuales y motrices. Consiste en una matriz de 6x3 LEDs, una columna verde, una amarilla y una roja. Aleatoria mente, se encenderá un LED que se encuentra hasta arriba, y ese irá bajando por la columna de su color hasta llegar al ultimo. Cuando eso suceda, se deberá presionar el botón del color correspondiente. Si esto se realiza correctamente, se suma un punto, de lo contrario se restan tres y suena un buzzer. Los puntos se despliegan en pantalla. La velocidad del juego se puede controlar con un potenciometro y un motor Servo se mueve dependiendo del puntaje.

To do: In this exercise, you realize a windscreen wiper with the Tower. The LEDs simulate the moving wiper by running from left to right and back again. The user interface is simple: With pushbutton1, the time delay interval is increased in steps of 1 second starting from 5 seconds delay down to 1 second and further to continuous wiping. With pushbutton2 the delay is decreased in the same way. If the delay is decreased, the wiper should start immediately, because right now there is a need for wiping. This is not true for increasing the delay. In this case, wait till the current delay time is over, set the new delay. In technical terms: Use asynchronous interval reset for decrease and synchronous reset for increase. Use active wait loops instead of the timer in this Kinetis exercise. Hint: Have you already switched a case? Result: TWR_K60_wiper_poll.zip

using the TAD tool

You probably have heard of what's new on Kinetis side of the house. YES, talking about KL02, measuring only 1.9mm x 2.0mm. Take a look at the picture in which this powerful ARM based chip gets compared real scale, and being this tiny yet delivers 60 percent more GPIO than the nearest competing MCU. :smileygrin:!!!

This sample is to use two FRDM-KL02Z to testing the I2C.  By working at 400KHz baud rate, some customer may found the I2C_SDA will generating a dig when failing edge of the I2C_CLK.  Actually it should related with I2C port layout and the question is why this happen and how to get rid of the dig? The truth is I2C pins are open drain, so no one actually drives a high value. The high value is only there because of a pullup resistor on the lines. For the case to connect two of FRDM-KL02Z using the I2C0_SCL and I2C0_SDA lines that are available on J7, these lines are also used for connecting to the inertial sensor that is on the board, and there are 4.7K pullups on both lines. Problem is that there are 4.7K pullups on the lines on both boards, so the pullups are weaker than intended. So customer should remove the pullup resistors from one of the two boards that should help. We even recommend customer might need to replace the 4.7K pullups with an even stronger pullup though when they have more devices on the I2C bus that are all adding loading.

To do: Same as exercise 5 but now with interrupts.   In this exercise, you realize a windscreen wiper with the Tower. The LEDs simulate the moving wiper by running from left to right and back again. The user interface is simple: With pushbutton1, the time delay interval is increased in steps of 1 second starting from 5 seconds delay down to 1 second and further to continuous wiping. With pushbutton2 the delay is decreased in the same way. If the delay is decreased, the wiper should start immediately, because right now there is a need for wiping. This is not true for increasing the delay. In this case, wait till the current delay time is over, set the new delay. In technical terms: Use asynchronous interval reset for decrease and synchronous reset for increase.   Use the timer and the port interrupts for the pushbuttons in this Kinetis exercise.   Result: TWR_K60_wiper_int.zip Original Attachment has been moved to: TWR_K60_wiper_int.zip

For Jorge_Gonzalez Subject: MKE04 interrupt latency in Kinetis microcontrollers This is the code I was using to measure interrupt latency. David Hollinrake

Gracias a la excelente respuesta por parte de los concursantes, les informamos que daremos a conocer los proyectos finalistas el próximo martes 26 de Noviembre de 2013, a través de la comunidad Freescale y redes sociales; recibimos proyectos con gran potencial que aún están siendo evaluados por nuestros jueces. A continuación te compartimos los criterios a evaluar: • Alineación con las tendencias del futuro (Salud y Seguridad, Efecto Net,Going Green) • Creatividad • Innovación • Utilidad de la aplicación • Beneficio ambiental potencial para el uso del producto. Los finalistas seleccionados tendrán la oportunidad de presentar su prototipo en el evento Freescale Cup 2013 el día 7 de Diciembre de 2013 en el Tecnológico de Monterrey, Campus Guadalajara; donde el proyecto ganador será elegido por los asistentes al evento, a través de la comunidad Freescale y redes sociales. Recuerda que el ganador viajará con todos los gastos pagados al Freescale Technology Forum (FTF) en Dallas, Texas. Mantente atento el próximo martes 26 de Noviembre de 2013 y descubre los proyectos finalistas, tú puedes ser uno de ellos.

Using a MK70FN1M0VMJ15 processor with MII and ADC2_SE16 enabled. Also using Codewarrior 10.6 and MQX4.022. Anytime I initialize the ADC2_SE16 the webserver stops working. I have delayed the initialization of the ADC2_SE16 and found that webserver works fine till initialization. I have also noticed that when the ADC2_SE16 is initialized first the webserver never gets link active. My question is that even though these are different ports and no pin is shared could the possibly be affecting each other? Hi Lee: I have been looking for information related to this problem but at this moment I have not find anything, In this case I would like to know if you are using a development board from Freescale or if you are using a custom board? Have a nice day, Perla Moncada ----------------------------------------------------------------------------------------------------------------------- Note: If this post answers your question, please click the Correct Answer button. Thank you! ----------------------------------------------------------------------------------------------------------------------- It is a custom board, with MII setup instead of RMII. I am concerned that it may be a chip issue, and have no real way to test that possibility with the Development board. This document was generated from the following discussion: