View the Webinar Recording

************************************************************************************************** * The PCF2129AT is a CMOS Real Time Clock (RTC) and calendar with an integrated * Temperature Compensated Crystal Oscillator and a 32.768 kHz quartz crystal * optimized for very high accuracy and very low power consumption. * * This simple example code has been written for the FRDM-KL25Z + OM13513 * boards and demonstrates how to set and read the time/date on the PCF2129AT * using the SPI (do not forget to remove the JP1 jumper) interface. It also * illustrates how to use a second interrupt to generate an interrupt on the * INT pin once per second when the Seconds register increments. * * In this example the time to be set is Wednesday, February 26 2020, 10:30 AM. * * Connection:      FRDM-KL25Z           OM13513 * VDD                 J9-4                           P2-2 * GND                 J9-14                         P2-1 * MOSI               J2-8                            P2-5 * MISO               J2-10                          P2-6 * SCLK               J2-12                          P2-4 * CS                   J2-6                            P2-7 * INT                  J1-6                            P2-8 ************************************************************************************************** Enabling the second interrupt by writing 0x01 to the Control_1 register (0x00): Second interrupt generated on the INT pin once per second: Setting the time and date by writing to registers Seconds (0x03) - Years (0x09):  Actual time and date shown in the Debug window:

/************************************************************************************************************* * This simple example code has been written for the FRDM-KL25Z + FRDM-FXS-MULT2-B * boards and illustrates: * * 1. How to read both the altitude (pressure) and temperature data from the MPL3115A2 * using the polling technique. * * 2. How to convert the raw data to real values in meters (Pascals) and degrees Celsius. *************************************************************************************************************/

Hi    For MCAL, S32R27X-37X_MCAL_4.2_RTM_2.0.1, its default configuration is for S32R372, not for S32R274.    If you want to config with S32R274, you should change the configuration at Resource and disable z7_0 in Mcu.   Before run Launch.bat in cmd window, you'd better execute the follow instructions. del .\cfg\include\*.h del .\cfg\src\*.c copy .\Tresos\workspace\Sample_app_S32R274\output\generated\include\*.h .\cfg\include copy .\Tresos\workspace\Sample_app_S32R274\output\generated\src\*.c     .\cfg\src    After compiled successfully, enjoy the debugging!!! Cheers! Oliver

Because of sometimes customer test fail on CAN short GND function, below shows the test step and result for verify. So need emphasize that EVB only works on debug mode.  Do not confuse about Debug/Normal mode and INIT/Normal mode in the state machine. You can short CAN on EVB every CAN points to GND, but actual in application customer boards sometimes the distance between CAN points and GND is so long and with more noise on bus line. so please take care of this short function should be meet the spec in datasheet.  ----Test 1: Test under INIT mode, CAN short GND function works well. Short CAN_L to GND, has a flag on CANL_.     We can’t write the CAN_LIN_MODE register, only can read.  After read CAN_LIN_MODE register, we find that CAN works on the normal mode.         ----Test 2: Test under normal mode operation after configure INIT_INT register. Short CANL to GND, the CANL_ flag set ‘1’ ,this CAN short to GND works well, without re-set the CAN_LIN_MODE register, then we read the information that CAN works on normal mode.     Setting the CAN in sleep mode then short CANL to GND,can’t detect the fault bit.  

In this publication, an example project using the PCF8523 is shown to demonstrate the easy use of the RTC devices from NXP. The PCF8523 is a real-time clock based on an ultra -low power oscillator and using an I2C- bus for interfacing. Some of its features are shown below: Has an ultra -low power consumption Provides time and calendar from seconds to years Accuracy is based on a 32.768 kHz quartz crystal Clock operating voltage: 1.0 V to 5.5 V Low backup current: typical 150 nA at VDD = 3.0 V and Tamb = 25 °C 2- line bidirectional 1 MHz Fast-mode Plus (Fm+) I2C interface, slave address: read D1h, write D0h Battery backup input pin and switch-over circuit Freely programmable timer and alarm with interrupt capability Integrated oscillator load capacitors, programmable for quartz crystals with CL=7pF or CL=12.5 pF Programmable offset register for frequency adjustment Internal Power-On Reset (POR) In this example, the PCF8523 is configured using the I2C interface based on the document UM10760 to generate an interrupt every second. Once the interrupt is generated, the time is read and stored into different variables.   The project was created using the FRDM-KL25Z platform and the OM13511 (I²C-bus RTC PCF8523 demo board). The complete source code is written in KDS IDE. You may find the complete project attached to this post. I highly recommend using the OM13511 as a reference for your projects.

****************************************************************************************************** * The PCF2127T is a CMOS Real Time Clock (RTC) and calendar with an integrated * Temperature Compensated Crystal Oscillator and a 32.768 kHz quartz crystal * optimized for very high accuracy and very low power consumption.   * This simple example code has been written for the FRDM-KL25Z + OM13513 * boards in MCUXpresso IDE v10.1.0 and demonstrates how to set and read * the time/date on the PCF2127T using the SPI (do not forget to remove the * JP1 jumper) interface. It also illustrates how to use a minute interrupt to * generate an interrupt on the INT pin once per minute when the Minutes * register increments. * * In this example the date/time to be set is Wednesday, January 17 2018, 2:45 PM. * * Connection:     FRDM-KL25Z        OM13513 * VDD               J9-4                         P2-2 * GND               J9-18                       P2-1 * MOSI              J2-8                         P2-5 * MISO              J2-10                       P2-6 * SCLK             J2-12                       P2-4 * CS                  J2-6                        P2-3 * INT                 J1-6                        P2-8 ******************************************************************************************************

********************************************************************************************************* * This simple example code has been written for the FRDM-KL25Z + FRDM-FXS-MULT2-B * boards and demonstrates how to use the embedded magnetic threshold detection * function in conjunction with the auto-wake/sleep mode for reducing current * consumption of the FXOS8700CQ. * * The magnetic threshold is set to 100uT (1000 counts) on the X and Y axis. * Once this threshold is exceeded, the FXOS8700CQ is waken up and an interrupt * is generated on the INT1 pin. If the magnetic field is below this threshold * within the 20ms period, the FXOS8700CQ goes back to sleep mode and also * generates an interrupt on the INT1 pin. *********************************************************************************************************

****************************************************************************************************** * This code has been written for the NXP FRDM-KL25Z + FRDM-STBC-AGM04 boards * and demonstrates how to read the acceleration (MMA8652FC), magnetic (MAG3110) * and angular rate (FXAS21002C) data using an interrupt technique. * * All sensors are controlled via I2C by default. * * I2C slave addresses: * MMA8652FC -> 0x1D * MAG3110 -> 0x0E * FXAS21002C -> 0x20 * * J7 selects MCU I2C bus for SDA: * 2:3 -> I2C_SDA1 (PTC2) * * J8 selects MCU I2C bus for SCL: * 2:3 -> I2C_SCL1 (PTC1) * * INT1_8652 connected to PTD4, INT1_MAG3110 connected to PTA5 pin and * INT1_21002 connected to PTA4 pin. ***************************************************************************************************** Original Attachment has been moved to: FRDM-KL25Z-FRDM-STBC-AGM04-Basic-read-using-I2C-and-interrupts.rar

*************************************************************************************************** * The PCF2129AT is a CMOS Real Time Clock (RTC) and calendar with an integrated * Temperature Compensated Crystal Oscillator and a 32.768 kHz quartz crystal * optimized for very high accuracy and very low power consumption. * Detailed Description: * This simple example code has been written for the FRDM-KL25Z + OM13513 * boards and demonstrates how to set and read the time/date on the PCF2129AT * using the SPI (do not forget to remove the JP1 jumper) interface. * * In this example the time to be set is Wednesday, February 8 2017, 2:45 PM. * * Connection:    FRDM-KL25Z       OM13513 * VDD               J9-4                       P2-2 * GND               J9-18                    P2-1 * MOSI              J2-8                      P2-5 * MISO              J2-10                    P2-6 * SCLK              J2-12                    P2-4 * CS                  J2-6                      P2-7 ***************************************************************************************************

Hi, Trying download and debug in IAR for MAC57D54H from NXP but get an error as: "Warning:Stack pointer is setup to incorrect alignment.Stack addr=0xFFFFFFFF" What would be the reason?

Subject:  Info on FET BUK7909-75AIE Description:  The datasheet for part number BUK7909-75AIE describes it as qualified to AEC standard for use in automotive critical applications.  It also says it is Q101 compliant.  We are not familiar with these automotive standards but would like to know if samples have been tested for either these or similar qualification tests: Lifetesting Tempeature Cycling HAST or 85/85. I am expecting the automotive qual to meet or exceed these requirements, but need to be sure that device samples or devices from the same process have had qualification testing performed.  Please comment. Also, we need to know if there is an MSL rating for this part?  Finally, what is the terminal finish?  What is the long-term availability.  WE are looking to use these to replace an obsolete FET from IR/Infineon, and we want to be sure it will remain available.

Four live demonstrations are presented: Timing Attack; Simple Power Analysis; Fault Attack, and finally an RFID Relay Attack demo. Timing Attack demo The Timing Attack demo shows the importance of securely implementing a PIN verification. If a PIN verification is implemented with operations which are not time-invariant - for example an if-else construction - it is possible to identify when an incorrect PIN digit is being compared by observing the timing information of the corresponding EM side-channel measurement. By iterating through all possible values of a PIN digit the correct character will be identified in a maximum of 10 attempts. To make the PIN query secure, a time-invariant comparison has to be implemented. For example, a bitwise XOR comparison and subsequent OR operation for all PIN digits, ensures the same time is taken for all possible comparisons. This scheme is illustrated in the block diagram.             Simple Power Analysis demo The RSA-Algorithm implemented in the Simple Power Analysis demo application is reduced to a simple 8-Bit implementation for illustrative purposes. The physical smart card interface used is contact-based. By monitoring the voltage drop across a shunt resistor it is possible to measure the power consumption of an RSA operation on a digital oscilloscope. Observation of the resulting measurements reveal that it is possible to visually distinguish  single square operations from square and multiply operations. By iteratively logging this sequence of operations, the bits of the exponent, that is the secret key, can be directly identified. By using countermeasures like the square and always multiply algorithm, the decoding of the exponent bits can be prevented and the key protected. The square and always multiply algorithm is illustrated in the block diagram.    Fault Attack demo The Fault Attack demo shows what can happen at software execution, if a flashlight is fired on a decapsulated chip which has no security measures. With simple tools – a mechanical grinding tool and some chemical etchant - it is possible to expose the surface of the chip and crudely inject photons into the sensitive silicon substrate. In this case the flashlight causes a skip in the execution of the PIN verification code if the flash is discharged close to the surface at the correct moment. In normal function expiration the UserPin is either correct or incorrect and access to the data is granted or denied accordingly. With a successful flashlight attack it doesn’t matter which value for UserPin is entered - after several tries the attacker skips the query and has access to the secret data.    RFID Relay Attack demo The RFID Relay Attack demo demonstrates a new paradigm in relay attacks in the context of software emulated smartcards on mobile devices. Previous conditions about proximity of the attacker to the victim and the time when the victim is approached, are negated. With a software emulated smartcard on a mobile device an attacker can intercept and relay the transaction of a potential victim remotely. This new attack paradigm greatly enhances the value of this attack for criminals, and consequently will result in greater malware development efforts. Additional Information on the individual attacks

******************************************************************************** * Detailed Description: * This example shows how to use the CTU module triggered from eTimer0 module channel 2. * * For closer details on how CTU works I suggest you to check application note * MPC5643LPWM_ADC_concept * https://community.freescale.com/docs/DOC-102559 * * This example sets eTimer0 channel2 for PWM signal generation. * This signal is than used to send MSR trigger to CTU module * Example contains also simple CTU module driver initialization * CTU scheduler submodule is toggling with external pin based on CTU triggers * * ------------------------------------------------------------------------------ * Test HW:  MPC57xx Motherboard + MPC5744PE257DC minimodule, MPC5744P, * silicon mask set 1N65H * Target :  internal_FLASH* ******************************************************************************** Original Attachment has been moved to: Example-MPC5744P-CTU-eTimer-v1_1-GHS614.zip

This video shows the necessary configurations to flash a binary file to a target, in this case the FRDM-KL25

This simple method, commonly used by RF engineers every day, is effective for creating a fast change of frequency range in a demo circuit, when you only have something close to work with. Your ability to use Freescale RF Power products as drop-ins is increased! In addition to being able to purchase a demonstration board, you can download any of the available DXF files for the PCB layout and order the board and list of materials for your production line. In many cases, you may be able to save money by choosing, testing, and qualifying your own list of less costly components. The initial design work is done with a Freescale demo board! The tuning, manufacturing and qualification process is all that is left to you. Thanks for choosing Freescale RF Power!

In Window Builder the string table is one of the key elements of the resource manager. This application notes gives tips and tricks to ease the use of string tables.

With the release of PEG 2.3.13 a newly created widget is available in PEG, called the "Swipe" widget. This application note describes features of the widget and how to make use it with Window Builder and PEG runtime library.