background image

How To Reach Us

Home Page:

nxp.com

Web Support:

nxp.com/support

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.

©

 NXP B.V. 2020-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: March 2, 2021

Document identifier: AN12919

Содержание Boundary Scan

Страница 1: ...ndary scan cell These cells are connected to a shift register which is referred to as the boundary scan register This register can be used to read and write port states In normal mode these cells are...

Страница 2: ...a general purpose port and it can provide access to many test support functions built into the component It has four or five signals as described in Table 1 NXP Semiconductors Overview Introduction to...

Страница 3: ...ling software The TRACE32 installation package can be found on the Lauterbach page Download the TRACE32_201909 7z to the computer and install it 1 Because the installation package is relatively large...

Страница 4: ...n to prevent damages to the debugger or target It is recommended to press F1 to enter the on line help system to get familiar with debugger 1 Taking RT1064 EVK board as an example the hardware connect...

Страница 5: ...2 3 0 to burn one bit 0x460 Boot Cfg1 in eFuse to enable JTAG It can t go back to SWD after eFuse burn Figure 4 shows the setup information NXP Semiconductors Hardware connection diagram Introduction...

Страница 6: ...ANCE_PATTERN part of the BSDL file They should have the same status 011 on the EVK board Figure 5 is compliance_patterns part of the BSDL file Figure 6 shows test mode and the por_b connection Figure...

Страница 7: ...DCDC_3V3 Figure 7 GPIO_AD_B0_08 connection 5 We used OPENSDA circuit on the RT1064 EVK board which will affect the JTAG signal level during the Boundary Scan test So we should disconnect the SWD jump...

Страница 8: ...r Lauterbach JTAG debugger recommended is LA 4533 Debug USB3 with LA 7960 4513 Related information can be found on the lauterbach page NOTE 2 Open the TRACE32 software and choose ARM32 USB NXP Semicon...

Страница 9: ...he BSDL state window Figure 9 BSDL state window 5 After loading the file type in command as below BSDL SOFTRESET 6 Switch to the Check tab of the BSDL state window Click BYPASSall and IDCODEall button...

Страница 10: ...eck Intern to filter out the internal registers The remaining contents are the sampled value on each signal pins Use a multimeter to measure voltage of at least three signal pins and see if the logic...

Страница 11: ...shown in Figure 13 Then switch to the BSDL state window and check SetAndRun and TwoStepDR as shown in Figure 14 Figure 13 BSDL SET window EXTEST set up NXP Semiconductors BSDL file validation using La...

Страница 12: ...check pass other pins as shown in Figure 15 Figure 15 BSDL SET window enable and toggle signal level The following uses GPIO_AD_B0_14 as an example It connects U1 H14 RT1064 chip as shown in Figure 1...

Страница 13: ...own resistor R303 of the JTAG_MOD pin and connect it to the DCDC_3V3 power supply 3 Ensure independent JTAG topology avoid level interference of other multiplexed signals and disconnect the headers J6...

Страница 14: ...n test delete the R21 resistor and mount R16 with 100 K resistor 4 Ensure independent JTAG topology avoid level interference of other multiplexed signals disconnect the headers J35 J36 J37 and J38 5 U...

Страница 15: ...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 desi...

Отзывы: