Other NXP Products Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

Other NXP Products Knowledge Base

Discussions

Q1: Why DisplayPort to LVDS adapter? DPRX-LVDS is an (embedded) DisplayPort to LVDS bridge device that enables connectivity between an (embedded) DisplayPort (eDP) source and LVDS display panel. It processes the incoming DisplayPort (DP) stream, performs DP to LVDS protocol conversion and transmits processed stream in LVDS format.   NXP offers two eDP-LVDS devices: 1. PTN3460 is commercial grade, 0 – 70 C. It is in 56-pin HVQFN package, 7 mm x 7 mm, 0.4 mm pitch. Supports pixel clock frequency from 25 MHz to 112 MHz. 2. PTN3460I is industrial grade, -40 – 85 C. It is in 56-pin HVQFN package, 7 mm x 7 mm, 0.4 mm pitch. Supports pixel clock frequency from 6 MHz to 112 MHz.   Q2. How to configure eDP-LVDS device?   The eDP-LVDS has embedded microcontroller and on-chip Non-Volatile Memory (NVM) to allow for flexibility in firmware updates.   Both PTN3460 and PTN3460I have a built in configuration table in internal 1K SRAM, which allows users to program seven EDID and 128 configuration registers through M/S I2C-bus. Please follow the programming guides below for these devices. 1. AN11128 – Programming Guide for PTN3460 2. AN11606 – Programming Guide for PTN3460I   Q3. What is maximum resolution DP-LVDS can support? The available bandwidth over a 2-lane HBR DisplayPort v1.4 link limits pixel clock rate support to: 1. 1-lane DP with single LVDS bus supports 800x600 @ 60 Hz display, 40 MHz pixel clock. 2. 1-lane DP with dual LVDS bus supports 1366x768 @ 60 Hz display, 85.5 MHz pixel clock. 3. 2-lane DP with single LVDS bus operation up to 112 mega pixel per second – supports 1440x900 @ 60 Hz resolution display. 4. 2-lane DP with dual LVDS bus operation up to 224 mega pixel per second – supports 1920x1200 @ 60 Hz resolution display.   Q4. How to update the FW? FW for eDP-LVDS devices can be updated by the following methods: 1. Flash over AUX (FoA) – This is an executable window utility that can only run under Windows OS. FW is updated through DP AUX channel. AN11133 – PTN3460 FoA utility user’s guide. 2. Flash over DOS (FoD) – This is an executable DOS utility that can run under DOS without OS. FW is updated through M/S I2C bus. 3. Flash over I2C – FW is updated through external I2C device that is plugged in a M/S I2C header.   Q5. How to check the FW version? FW version can be read out with DPCD utility that runs under Windows OS. Please follow DPCD Tool User Manual V1.0.   Q6. How many DP lanes supported in NXP DP to LVDS bridge device? NXP DP to LVDS bridge device supports 2 lanes HBR/RBR.   Q7. What does HBR/RBR mean? HBR means “High Bit Rate”, it runs 2.7 Gbit/s. RBR means “Reduced Bit Rate”, it runs 1.62 Gbit/s.   Q8. What is DP AUX channel? DP AUX channel is used for communication channel between DP source and DP sink device.   Q9. What is DP source device? DP source device is DP signal transmitter.   Q10. What is DP sink device? DP sink device is DP signal receiver.
View full article
Q1. What is the difference between A and B? CBTL02043A has input and output pins on the opposite of the package, and is suitable for edge connector(s) with different signal sources on the motherboard. CBTL02043B has outputs on both sides of the package, and the device can be placed between two connectors to multiplex differential signals from a controller.     Q2. Can CBTL02043 be used for HDMI applications? No, CBTL02043 cannot be used for HDMI applications. HDMI TMDS signal has its DC termination supply voltage at 3.3V +/-5%. CBTL02043 maximum input voltage at differential pins is limited at 2.4V, only.   Q3. How does CBTL02043 affect the system channel loss budget? CBTL02043 will brings in extra insertion loss to the system. CBTL02043 has −1.3 dB loss at 4 GHz, which is equivalent to about 1.5 inch (3.81 cm) to 2 inch (5.08 cm) FR4 PCB loss. The system designers need to take this MUX insertion loss into account when planning the system loss budget.   Q4. Are there SPICE, IBIS or S-parameter models available for CBTL02043? There is no SPICE model. IBIS/S-parameter models can be found below in attachments.   Q5. How to bias the high-speed switch?   PCIe, DP, USB3, and SATA electrical signals require AC coupling between the transmitter and receiver. The AC coupling capacitors are usually placed close to the transmitter. CBTL02043 requires a bias voltage, less than 2 V, applied to its switches. There are several AC coupling capacitor placement options:   A. The capacitors can be placed between the MUX and the downstream controller, and the MUX is biased by the upstream controller.   B. The capacitors can be placed between the upstream transmitter and the MUX. RX signals on the motherboard sides usually do not require AC coupling capacitors since those capacitors are located on the add-in card. The TX MUX is biased by the downstream controller, and the RX MUX is biased by the upstream controller.   C. Do not place capacitors at both side of MUX, unless a bias voltage is provided. In case of that both upstream and downstream controllers’ common-mode voltage is higher than 2 V, a bias voltage, which is less than 2 V, is needed for CBTL02043. The following figure shows an implementation in this case.
View full article
Hi Everyone, I would like to share with you a simple bare metal example for the the SC16IS752 to demonstrate NXP Bridge IC for SPI/ I 2 C host to Dual Uart/IrDa/GPIO interface. This example is based on the OM6273 demo board for the SC16752/762. I made this example working with the NXP FRDM-KL25Z development platform. The example shows the device functionality by creating a simple echo transmission, where you are able to read what you just write into the device. This example illustrates: 1. Initialization of the MKL25Z128 MCU (I 2 C and port modules) 2. I 2 C data write and read operations 3. Initialization of the bridge to perform the communication 4. Transmission and the reception done with interrupt technique 5. Visualization of the echo function using the serial terminal 1. As you can see in the FRDM-KL25Z schematics and the image below, I 2 C signals are routed to the I2C1 module (PTC1 and PTC2 pins) of the KL25Z MCU and the INT1 output is connected to the PTA16 pin. The INT1 output of the SC16IS752 is configured as a push-pull active-low output, so the corresponding PTA16 pin configuration is GPIO with an interrupt on falling edge.                                               Therefore, this is the MCU configuration: void MCU_Init ( void ) {      //I2C1 module initialization      SIM_SCGC4 | = SIM_SCGC4_I2C1_MASK ;           // Turn on clock to I2C1 module      SIM_SCGC5 | = SIM_SCGC5_PORTC_MASK ;           // Turn on clock to Port E module      PORTC_PCR1 = PORT_PCR_MUX ( 2 ) ;                // PTC1 pin is I2C1 SCL line      PORTC_PCR2 = PORT_PCR_MUX ( 2 ) ;                // PTC2 pin is I2C1 SDA line      I2C1_F  = 0x14 ;                                // SDA hold time = 2.125us, SCL start hold time = 4.25us, SCL stop hold time = 5.125us      I2C1_C1 = I2C_C1_IICEN_MASK ;               // Enable I2C1 module      //Configure the PTA16 pin (connected to the IRQ of the SC16IS752) for falling edge interrupts      SIM_SCGC5 | = SIM_SCGC5_PORTA_MASK ;                // Turn on clock to Port A module      PORTA_PCR16 | = ( 0 | PORT_PCR_ISF_MASK              // Clear the interrupt flag                    | PORT_PCR_MUX ( 0x1 )                     // PTA16 is configured as GPIO                    | PORT_PCR_IRQC ( 0xA ) ) ;                // PTA16 is configured for falling edge interrupts      //Enable PORTA interrupt on NVIC      NVIC_EnableIRQ ( PORTA_IRQn ) ;                 // Enable interrupts      NVIC_ClearPendingIRQ ( PORTA_IRQn ) ;           // Clear pending interrupts } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ 2. To perform the read or write operation we'll make use of an  I 2 C library which contains to main functions: void I2C_WriteRegister(unsigned char u8SlaveAddress, unsigned char u8RegisterAddress, /*unsigned*/ char u8Data); unsigned char I2C_ReadRegister(unsigned char u8SlaveAddress, unsigned char u8RegisterAddress) Before any data is transmitted or received, the master must send the address of the receiver via the SDA line. The first byte after the START condition carries the address of the slave device and the read/write bit. Table 32. shows how the SC16IS752/SC16IS762’s address can be selected by using A1 and A0 pins. In the demo board OM6273, these  2 pins are connected to JP4 and JP3 and in this example there are two jumpers plugged so A1 = VDD and A2 = VDD, then the SC16IS752’s address is set to 0x90(Write) and 0x91(Read), and the master communicates with it through this address.                                                 The second parameter in the read or write function is the internal register address, these are defined in the SC16IS752.h attached to this document and explained with greater detail in the SC16IS752 datasheet.                                                           3. The SC16IS752 is set to work at 115, 200 baud/s , the Receive Holding Register interrupt is enabled and routed to the INT1 pin that is configured to be a push-pull, active-low output. The registers are shift 3 positions left because the UART's internal register select are the bits 3:0, as shown in table 33. In the example channel 0 is used. This initialization is based in the application notes AN10587 and AN10462, where is possible to find additional information in regards the SC16IS752 // Program channel A for I2C-UART void SC16IS752_Init_ChA ( void ) {      I2C_WriteRegister ( SC16IS752_ADDRESS , LCR_REG     << 3 , 0x80 ) ;             // 0x80 when LCR[7] = 1 DLL and DLH are accessible      I2C_WriteRegister ( SC16IS752_ADDRESS , DLL_REG     << 3 , 0x08 ) ;          // 0x08 = 115,200 baud rate when XTal = 14.7456 MHz      I2C_WriteRegister ( SC16IS752_ADDRESS , DLH_REG     << 3 , 0x00 ) ;          // 0x00 = 115,200 baud rate when XTal = 14.7456 MHz      I2C_WriteRegister ( SC16IS752_ADDRESS , LCR_REG     << 3 , 0xBF ) ;             // Access special features register      I2C_WriteRegister ( SC16IS752_ADDRESS , EFR_REG     << 3 , 0x10 ) ;             // enable enhanced functions      I2C_WriteRegister ( SC16IS752_ADDRESS , LCR_REG     << 3 , 0x03 ) ;             // 8 data bit, 1 stop bit, no parity           I2C_WriteRegister ( SC16IS752_ADDRESS , IODIR_REG   << 3 , 0xFF ) ;             // set GPIO [7:0] to output (input by default)      I2C_WriteRegister ( SC16IS752_ADDRESS , IOSTATE_REG << 3 , 0x00 ) ;             // set GPIO [7:0] to 0x00 (Turn LEDs on)      I2C_WriteRegister ( SC16IS752_ADDRESS , IER_REG     << 3 , 0x01 ) ;             // enable Rx data ready interrupt } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ 4. In the interrupt service routine the program reads the interrupt identification register, and it's ready to add a different task for each interrupt, for now it simply enables the data ready flag when the interrupt was generated by the RHR. It also cleans the flag that generated the interrupt. We also have the write function and the read function of the SC16IS752, these two functions access the corresponding THR or RHR registers. void PORTA_IRQHandler ( ) {      //Interrupt service routine      Interrupt_Source iir = I2C_ReadRegister ( SC16IS752_ADDRESS , IIR_REG << 3 ) ;    //read IIR to retrieve the interrupt source      // IIR[5:1] 5-bit encoded interrupt      switch ( iir & 0x3E ) {           case RHR : DataReady = 1 ; break ;           default : break ;      }      PORTA_PCR16 | = PORT_PCR_ISF_MASK ;                // Clear the interrupt flag } void writeSC16IS752 ( char data ) {      I2C_WriteRegister ( SC16IS752_ADDRESS , FCR_REG << 3 , 0x04 ) ;               //clears the contents of the transmit FIFO      while ( ! ( I2C_ReadRegister ( SC16IS752_ADDRESS , LSR_REG << 3 ) & 0x40 ) ) ;     //Is it able to transmit? - Poll Transmit empty indicator      I2C_WriteRegister ( SC16IS752_ADDRESS , THR_REG << 3 , data ) ;              //Write to the transmit holding register to start transmission } unsigned char readSC16IS752 ( void ) {      return I2C_ReadRegister ( SC16IS752_ADDRESS , RHR_REG ) ;                   //Read receive holding register } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ 5. We connect the I 2 C lines with each other in the board, JP6 contains INT1, SDA and SCL in that order, then P1 is connected to EVBUSB2SER (USB to serial device), and this last one to a computer. In the computer must be installed a serial terminal,   for this example Teraterm is used                 We set up Tera Term going to Setup > Serial Port and then select corresponding port to the EVBUSB2SER and baud rate 115,200 This is the main, that should be executed to perform the echo function char DataReady ; int main ( void ) {      unsigned char echo = 0 ;      MCU_Init ( ) ;      Pause ( 500000 ) ;      SC16IS752_Init_ChA ( ) ;      for ( ; ; ) {           if ( DataReady ) {                DataReady = 0 ;                echo = readSC16IS752 ( ) ;             //Read RHR, since FIFO is disable it only reads the first location                writeSC16IS752 ( echo ) ;             //Send back the value received           }      }      return 0 ; } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ After this, every character written in the serial terminal will appear in the serial terminal as you were writing in the command prompt Attached you can find the complete source code written using KDS IDE and some other relevant documentation   If there are any questions regarding this simple application, do not hesitate to ask below. Your feedback or suggestions are also welcome.   Thanks to a major collaborator for this document david_diaz‌. Regards, Darío Arias
View full article
Hi,      Some of PowerPC cores contain time base which could be the ruler to measure the running time of codes.     Generally, e200z4, e200z7 have such registers, RBL and TBU. They are SPR284 and SPR285.      Sample codes could be taken the reference within AN2865SW(Timebase project) .   Enjoy the measuring! Cheers! Oliver BTW, measure the running time of one function on S32K could also be gotten through the link. 
View full article
Hi,       NXP changes the documents' structure and user could get the unified information for the same package.     For example, S32R family.     1. You should search data sheet to get the package type and document number, as the snapshot  2.  Search on www.nxp.com for the document, 98ASA00081D 3. Download the file and open it to check. You can get the package's information as your will. Cheers! Oliver
View full article
View the Webinar Recording
View full article
************************************************************************************************** * 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:
View full article
/************************************************************************************************************* * 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. *************************************************************************************************************/
View full article
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
View full article
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.  
View full article
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 I 2 C- 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.
View full article
****************************************************************************************************** * 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 ******************************************************************************************************
View full article
********************************************************************************************************* * 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. *********************************************************************************************************
View full article
****************************************************************************************************** * 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
View full article
*************************************************************************************************** * 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 ***************************************************************************************************
View full article
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?
View full article