background image

How To Reach
Us

Home Page:

nxp.com

Web Support:

nxp.com/support

Limited warranty and liability — Information in this document is provided solely to enable system and software implementers to use NXP
products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on
the information in this document. NXP reserves the right to make changes without further notice to any products herein.

NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does
NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability,
including without limitation consequential or incidental damages. “Typical” parameters that may be provided in NXP data sheets and/or
specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including
“typicals,” must be validated for each customer application by customer's technical experts. NXP does not convey any license under its
patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the
following address: 

nxp.com/SalesTermsandConditions

.

Right to make changes - NXP Semiconductors reserves the right to make changes to information published in this document, including
without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all
information supplied prior to the publication hereof.

Security — Customer understands that all NXP products may be subject to unidentified or documented vulnerabilities. Customer
is responsible for the design and operation of its applications and products throughout their lifecycles to reduce the effect of these
vulnerabilities on customer’s applications and products. Customer’s responsibility also extends to other open and/or proprietary
technologies supported by NXP products for use in customer’s applications. NXP accepts no liability for any vulnerability. Customer
should regularly check security updates from NXP and follow up appropriately. Customer shall select products with security features that
best meet rules, regulations, and standards of the intended application and make the ultimate design decisions regarding its products
and is solely responsible for compliance with all legal, regulatory, and security related requirements concerning its products, regardless
of any information or support that may be provided by NXP. NXP has a Product Security Incident Response Team (PSIRT) (reachable
at [email protected]) that manages the investigation, reporting, and solution release to security vulnerabilities of NXP products.

NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, COOLFLUX,EMBRACE, GREENCHIP, HITAG,
ICODE, JCOP, LIFE, VIBES, MIFARE, MIFARE CLASSIC, MIFARE DESFire, MIFARE PLUS, MIFARE FLEX, MANTIS, MIFARE
ULTRALIGHT, MIFARE4MOBILE, MIGLO, NTAG, ROADLINK, SMARTLX, SMARTMX, STARPLUG, TOPFET, TRENCHMOS,
UCODE, Freescale, the Freescale logo, AltiVec, CodeWarrior, ColdFire, C, the Energy Efficient Solutions logo, Kinetis,
Layerscape, MagniV, mobileGT, PEG, PowerQUICC, Processor Expert, QorIQ, QorIQ Qonverge, SafeAssure, the SafeAssure logo,
StarCore, Symphony, VortiQa, Vybrid, Airfast, BeeKit, BeeStack, CoreNet, Flexis, MXC, Platform in a Package, QUICC Engine, Tower,
TurboLink, EdgeScale, EdgeLock, eIQ, and Immersive3D are trademarks of NXP B.V. All other product or service names are the
property of their respective owners.  AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE, Cordio, CoreLink, CoreSight,
Cortex, DesignStart, DynamIQ, Jazelle, Keil, Mali, Mbed, Mbed Enabled, NEON, POP, RealView, SecurCore, Socrates, Thumb,
TrustZone, ULINK, ULINK2, ULINK-ME, ULINK-PLUS, ULINKpro, µVision, Versatile are trademarks or registered trademarks of Arm
Limited (or its subsidiaries) in the US and/or elsewhere. The related technology may be protected by any or all of patents, copyrights,
designs and trade secrets. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. The Power
Architecture and Power.org word marks and the Power and Power.org logos and related marks are trademarks and service marks
licensed by Power.org. M, M Mobileye and other Mobileye trademarks or logos appearing herein are trademarks of Mobileye Vision
Technologies Ltd. in the United States, the EU and/or other jurisdictions.

©

 NXP B.V. 2021.

All rights reserved.

For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: [email protected]

Date of release: 07 September 2021

Document identifier: AN12868

Summary of Contents for AN12868

Page 1: ...sferred This signal is often a way to indicate that one entire frame is transmitted Pixel Clock PCLK This pixel clock changes on every pixel The application note only focuses on Digital Video Port DVP...

Page 2: ...lay the 320 240 resolution LCD up to 30 fps 5 4 System clock The camera engine shares the system clock with Arm core To speed up the processing time the system clock must be configured to 150 MHz For...

Page 3: ...ution should be configured as QVGA 320 240 6 Pin description 6 1 Connection of interface Camera D0 D1 D2 D3 D4 D5 D6 D7 SIOC SIOD VSYNC HREF PCLK XCLK VCC GND P0 0 P0 1 P0 2 P0 3 P0 4 P0 5 P0 6 P0 7 P...

Page 4: ...presso IDE but not IAR 7 2 API routine The main purposes of the API routines include Enable the clock of engine Configure the IO as camera interface function Initial the I2C interface Enable the inter...

Page 5: ...put Camera engine function P0_6 15 Input Camera engine function P0_7 15 Input Camera engine function P0_18 15 Output Camera engine function p0_13 0 Input GPIO as VSYNC input P0_15 0 Input GPIO as Pixe...

Page 6: ...ed in the RAM by camera engine 7 4 6 Reserved 46_IRQHandler Same with other peripheral handler camera engine handler is implemented by Arm core once engine finishes the storage operation In the handle...

Page 7: ...r to 5 V Power only USB port P5 6 The LCD displays the video frame from camera as shown in Figure 4 If the code cannot execute after downloaded one of the reasons is that the MCU goes to ISP mode The...

Page 8: ...lease A Purchasing LCD module and camera module used in this demo You can purchase the LCD board and camera module from the below links 1 https www waveshare com 2 8inch tft touch shield htm 2 http ww...

Page 9: ...cts with security features that best meet rules regulations and standards of the intended application and make the ultimate design decisions regarding its products and is solely responsible for compli...

Reviews: