MICROCHIP AN4325 UHF ATA Product Application and Design User Guide

AN4325
UHF ATA Product Application and Design Quick Reference
Guide

Introduction

This application note describes the application and design guidelines of the ATA Ultra High Frequency (UHF) products. It is implicit to follow the application and design rules from the user manual and data sheet, while the information in the application note is helpful during the design process specifically. Therefore, it is highly recommended to refer to this application note while working on the application and design process of the ATA UHF products. The topics can help to speed up the application and design process.
In addition, the application note also provides helpful guidelines while designing the application for the following transceiver/receiver products:

• ATA5830, ATA5830N
• ATA5780, ATA5780N
• ATA5831, ATA5832, ATA5833 and ATA5835
• ATA5781, ATA5782, ATA5783, ATA5785 and ATA5787
• ATA8510, ATA8515
• ATA8210, ATA8215
• ATA8710
• ATA8535
• ATA8287

Quick references

1.1 Reference Documentation

• ATA5830/ATA5830N UHF ASK/FSK Transceiver Data Sheet (9208GX-RKE-09/15)
• ATA5780N UHF ASK/FSK Receiver Data Sheet (9207EX-RKE-09/15)
• ATA5831/ATA5832/ATA5833 UHF ASK/FSK Transceiver User Manual (9313GX-RKE-07/15)
• ATA5781/ATA5781N/ATA5782/ATA5783 UHF ASK/FSK Receiver User Manual (9314GX-KE-07/15)
• ATA5785 UHF ASK/FSK Receiver User Manual (9360BX-RKE-11/14)
• ATA5835 UHF ASK/FSK Transceiver User’s Guide (DS50003152A)
• ATA5787 UHF ASK/FSK Receiver User’s Guide (DS50003174A)
• ATA8510/ATA8515 Industrial User’s Guide (DS50003142A)

1.2 Acronyms and Abbreviations

System Behavior

2.1 RSSI Usage
The UHF products offer a digital Radio Signal Strength Indicator (RSSI) sampling, including history data, via the built-in 16-byte SFIFO buffer. Use the RSSI to obtain the signal strength over the received message. It is important to know that the transceiver/receiver starts the RSSI sampling immediately with the start of the active phase (except for ATA5830(N) and ATA5780(N)). Depending on the scenario and configuration, the buffer might be filled with 16 RSSI samples from noise, before the system detects a FIFO overflow. Therefore, the recommendation is to set the FIFO buffer over/underflow error disable option in the EEPROM configuration. Otherwise, an error is triggered, including for an IRQ event (optional), if an overflow happens. The FIFO buffer is organized as a ring buffer. This results in getting the RSSI values from the RF message, as the noise values are overwritten. To get useful data in the RSSI buffer, set the sampling rate according to the RF signal characteristics. Divide the number of transferred bytes by 16, and set the next larger sample value for the RSSI update period in the service configuration to get the RSSI characteristics of the whole RF message. Apply the same calculation with the reduced number of bytes for the signal strength of the payload. If the “stay in RX after EOT” option is enabled (or applied), ensure that the SFIFO content is not overwritten.
2.2 FIFO Corruption
In case of a mode switching, consider the buffer content from the Data FIFO (DFIFO) and Support FIFO (SFIFO). As the handling from the buffers differ, ensure consistent content between the RX mode and TX mode. Switch from RX mode to TX mode cautiously. There is no automatic clearance prior to the start of the TX mode, which means that any remaining information in SFIFO or DFIFO corrupts the transmission pattern. There are two options to clear the buffer and get a known state:

• The first option is to read all data, as this will reduce the fill level by the number of bytes read. Continue with the next operation mode if you have read all data from the buffer.
• The second option is to trigger a clearance by writing the DFCLR.DFL and SFCLR.SFL bits to ‘ 1’.

During the start of the RX mode, the firmware takes care of a buffer reset; therefore, there is no need for additional action. In the case of using the Continuous Receive mode, the user must carefully handle the buffer content. In Continuous Receiver mode, the device does not stop the reception after the End Of Telegram (EOT). Multiple message reception can lead to an overflow of the buffer, and this overflow can trigger an error event if it is not disabled in the EEPROM configuration. In addition, unprocessed data can be overwritten. Handle the data carefully to achieve a stable application.
2.3 Antenna Damping (RSSI Accuracy)
The transceiver or receiver supports strong RF signals in the application with an automatic damping to avoid saturation of the internal Low Noise Amplifier (LNA). Except for ATA5835 and ATA5787, the damping function is implemented in the Single Pole Double Throw (SPDT). The internal firmware corrects the RSSI calculation according to the state of the damping. Take care of the signal strength correction in the absence of SPDT, as the device does not detect SPDT usage. For the two products mentioned earlier, the damping is realized via LNA gain reduction, irrespective of whether the built-in-switch is used or not.
2.4 GPIO Driver Strength
The technical documentation of the UHF products specifies the current for a voltage drop of 10%. All GPIO pins from the supported products are protected against shortage. Therefore, larger current can be driven if a higher voltage drop is accepted. Calculate the available current and the corresponding voltage drop by calculating the RDS(on) with the given parameters from the data sheet.
Note: A shortage of multiple GPIO pins can lead to thermal overstress and damage the product.
2.5 Consistency Check
Reading the version of the product right after the start of the application system is recommended. This ensures that the right product with the right version is used. In addition to the version, reading the product ID from the NVM memory (EEPROM) is recommended also.
2.6 Considering Reset Behavior
The following are the three different ways to set or keep the product’s Reset state:

• Power-on-Reset (POR)
• External Reset (NRESET)
• Watchdog Reset (WDR)

For the reset behavior, two states must be distinguished. The first one is that the device is in the OFF state. In this case, the device will not react to a reset and stays in the OFF mode. In the second state, the device is active.
This happens if any wake conditions were triggered in the past and no reset or OFF mode instruction was triggered. The Microchip ATA UHF products can be set or kept in the Reset state in three different ways. Power-on-Reset (POR), External Reset (NRESET) and the Watchdog Reset (WDR) are available. The source that triggers the reset is available in the MCUSR register and, after the reset, the device will temporarily stay awake. During the system initialization, the firmware checks if a valid wake source is available or not. If the wake source is unavailable, the device is set to the OFF mode. If the application is reset, the device is not responsive to the main μC because no wake source is available after a reset. For a robust application, it is essential for the main µC to detect a reset of the ATA UHF product. For the NRESET as reset source, the main µC is the initiator of the event, which means it is a known event. The situation is similar if a POR reset happens. The main µC must be able to detect this event.
The situation becomes difficult in the case of a WDR. Without a valid wake source, the main μC is not aware of this reset and the subsequent OFF mode. In this situation, the main µC and the ATA UHF device are not synchronized because the main µC does not detect the WDR event. Use the OFF mode behavior of the wake pins to identify the WDR. In the OFF mode, all the I/O pins, except for the one with wake capability and NRESET, will be in tri-state. NPWRONx pins and NRESET are pulled to high level in the OFF mode. For example, configure the PC1 at a low level during normal operation, and a high transition indicates the OFF mode. The main µC can detect this.
Notes:

• The NRESET pin is pulled to high, independent of the state of the ATA UHF product (Off or Active). It is necessary to have a defined level for the NRESET pin, independent of the main µC state. This is documented in the user manual.
• As the NRESET functionality is essential for operation and program, only use the reset disable fuse (RSTDISBL) with the highest attention as this can block the system from further access via ISP or HVSP (High Voltage Serial Programing).

2.7 System Event Monitoring
Microchip ATA UHF products can work in different operation modes. Knowing the current mode is helpful for robust application design. The active operation mode is stored in the SystemModeConfig register copy located in the SRAM.
Whenever a mode change is triggered, the register is updated. The content of this register is described in the data sheet or the user manual. The address of the register for the different products is shown in the following table:

ATA5831, ATA5832, ATA5833, ATA5781, ATA5782, ATA5783, ATA8510, ATA8515, ATA8210, ATA8215, ATA8710| trxConf.
systemModeConfig| 0x02FB

Configuration Guidelines

Microchip offers a configuration tool to set up the characteristics of the ATA UHF products. The configuration can be stored in a .hex file and programmed to the EEPROM memory (except ATA5785).
3.1 GPIO Functionality
Some of the GPIO pins from ATA UHF products support multiple functions. Ensure that the port direction selected via the EEPROM device configuration matches the desired alternate function. For example, if using the TRPA signal for debugging, ensure the I/O pin is configured to be an output. Failure to follow this step might obstruct the expected function. The EEPROM configuration tool monitors the selection and indicates any mistake in the log window or by special marking of the function. Monitor the tool to detect the problem and find a solution.
3.2 Event Notification
Ensure there is a proper event notification configuration for an application. This includes all application-specific events, like a notification of the EOT, and general system events, like a power-on event (SYS_RDY) and error event (SYS_ERR). The system events identify specific events and give the capability to react on it, for example, an unexpected undervoltage below 1.9V followed by restoring of target voltage. This scenario triggers a POR, and is indicated by a system ready flag (SYS_RDY). Without the SYS_RDY event activated, this event cannot be detected and the application might get stuck in an unexpected state if the host controller does not react to the event. Another example is the occurrence of an unexpected system error. Without the SYS_ERR event activated, the system can be in an undefined state. Activated system events help during unexpected events by appropriately reacting and, therefore, help in designing a robust application.
3.3 Updating Recommended Values
Consider adapting other parameters for the application while tuning parameters like frequency, receiver bandwidth and data rate. Based on the input, the EEPROM configuration tool calculates recommended values for a particular parameter. Therefore, set the recommended values according to the new setup to ensure a proper operation.
Note: The recommended values ensure that the application is working. Fine tuning might be required during validation to meet all the requirements.
3.4 Bytes, Bits and Symbols
Bytes, bits and symbols are used in Microchip’s product naming conventions. Ensure bits and bytes are used appropriately, as the coding can be different for both, for example, in Manchester coding where 1 bit is coded by two symbols.
The following are some of the important functions that use symbol-based data handling:

• SFIFO usage as preamble buffer in TX mode
• WUP and SFID pattern definition in EEPROM configuration
• Signal check size setup in EEPROM configuration
• Carrier check parameter in EEPROM configuration
• Run-In and stop sequence Pattern in RX mode and TX mode

In transmit mode, the data FIFO is loaded byte-wise with the raw data. The configured coding is done in HW and handled automatically from the system. In receive mode, the received data will be decoded automatically from the HW, if it is enabled in the configuration. The resultant raw data are loaded to the data FIFO.

Design Guidelines

4.1 NRESET Control
It is required to have the connection and control of the NRESET pin. The main μC must be capable to trigger/restart the whole system when the UHF device does not perform accordingly. Under normal conditions this does not occur, but this can happen in the case of an Electrostatic Discharge (ESD) or any other external event. An unexpected and unpredictable external event can influence the system. Be sure to have control over the power supply of the UHF device if the NRESET functionality is not available or cannot be used. In this case, the main µC can apply a Power-on-Reset (POR).
4.2 Wake-up Control
In most applications, the UHF device from Microchip acts as a peripheral, controlled from central device. The central must handle the Wake-up source, to ensure proper conditions for the RF device. With this approach, proper supply conditions are present prior to the UHF part activation. Another advantage of this approach is that the start-up order is kept. The UHF device can operate with voltage down to 1.9-2.0V. That means, the UHF device can operate in a voltage range where the main μC is still not operative. Be sure to maintain control over the Wake-up to avoid unexpected effects in such situations.
4.3 Test Pads
A test pad at every available GPIO pin is recommended for debugging the application. A test pad can be used for verification or system optimization, even if it is not used in the application. It is suggested to have the 6-pin In-System Programming (ISP) header for in-system programming or debugging.
4.4 Use the Watchdog Timer
The embedded Watchdog Timer (WDT) provides an additional level of security. Using the feature to detect unexpected behavior of the application is recommended, especially when using the personal User Flash application software. The WDT can also be used if the system enters the Sleep mode. The user can achieve the periodical wake
up feature via the internal wake up Timer0 .
4.5 Memory Access
It can be helpful to implement this feature into the main μC even if the SRAM, the hardware register or all addresses of the EEPROM are not read in the final application from the customer. It can be necessary to read the additional data from the peripheral for debugging or optimizing the application.
4.6 Crystal Oscillator (XTO) Selection
All parameters in the data sheet are validated with the XTO frequency 24.305 MHz. This frequency was identified as usable for the typical applicable RF bands. However, it is possible to select another XTO frequency according to the specified parameter in the data sheet. If using another XTO frequency, verify and validate the following parameters:

• XTO harmonic influences to the RF
• System timings
• Interface timings
• Start-up behavior (in case of using other parameter or form factor)

For more details on how to calculate influences of the specified XTO frequency, refer to the AN3716_UHF_CrystalSelection Application Note.
4.7 RF Matching Network
Leaving footprint space for some spare matching elements during the design phase for the RF matching task is recommended. Depending on the complexity of the analog circuit, the task becomes much easier with the availability of additional components. Even if the additional components are not required in the final application, it is better to
have them available instead of re-designing the PCB to reach the target performance. For more details on matching practices, refer to the RF Matching Recommendation Application Note (DS00004061A and DS00003566A).
4.8 Suppressing Unwanted Signals
The UHF products provide strong suppression against unwanted signals. This covers radiated signals as well as the external signals. Preparing the design for shielding while dealing with strict requirements is recommended to provide the capability later without requiring a redesign, even if not required in the final application.
4.9 API usage
Using API function calls is highly recommended when using a user Flash application inside the UHF product. This ensures that the handling of the internal flags is according to the product specification. For example, if the events are accessed and modified in a direct way, they can end up in a corrupted state of the flags. Submit a support request for assistance through www.microchip.com/support in case there is a need to control the device without API functions.
4.10 External Static Wake for Software Development
Having HW-based wake-up capability is recommended while developing user Flash software for the transceiver, transmitter or receiver. After connecting the Voltage Supply (VS), the devices stay in the OFF mode, waiting for a wake event from an external source. It can be difficult to implement a static wake function to the host controller.
Therefore, it can be helpful to have a jumper or something similar, to keep the device awake all the time. This can help in achieving a suitable operation in ISP mode. Between the ISP steps, the NRESET line releases and the device enters the OFF mode and requires a wake prior to the start of the next ISP operation.

Important Information

5.1 ATA578x Signature
The product numbering that is listed in the ATA578x User Manual Rev 9314GX in the table in chapter 3.9.12.4 is mixed. The numbering must start with 1 followed by 2 and end with 3. Ensure the part numbers are not mixed while using the signature.
5.2 Invalid Mode Transitions
The firmware of the products covers many invalid transitions and potential issues. The error IRQ and a specific error code indicate all those invalid transitions and potential issues. During the development phase, not all possible scenarios are known, and there can be scenarios that are not valid but not indicated by an event. Therefore, ensure suitable implementation of all the functions. Known actions that will not lead to an error IRQ and an error code entry are:

• Mode transition from Polling mode to RX mode
• Antenna tuning without signal at the antenna tuning pin

Document Revision History

The Microchip Website
Microchip provides online support via our website at www.microchip.com/. This website is used to make files and information easily available to customers. Some of the content available includes:

• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online discussion groups, Microchip design partner program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives

Product Change Notification Service
Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will receive email notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.
To register, go to www.microchip.com/pcn and follow the registration instructions.
Customer Support
Users of Microchip products can receive assistance through several channels:

• Distributor or Representative
• Local Sales Office
• Embedded Solutions Engineer (ESE)
• Technical Support

Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in this document. Technical support is available through the website at: www.microchip.com/support
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip products:

• Microchip products meet the specifications contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.
• Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright Act.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable”. Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.

Legal Notice
This publication and the information herein may be used only with Microchip products, including to design, test, and integrate Microchip products with your application. Use of this information in any other manner violates these terms. Information regarding device applications is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your local Microchip sales office for additional support or, obtain additional support at www.microchip.com/en-us/support/design-help/client-support- services.

THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND  HETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE. IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP’S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.
Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, Adaptec, AnyRate, AVR, AVR logo, AVR Freaks, BesTime, BitCloud, CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB,
OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed Control, HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus, ProASIC Plus logo, Quiet- Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider, TrueTime, WinPath, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching, BlueSky, BodyCom, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, GridTime, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, maxCrypto, maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, NVM Express, NVMe, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, RTAX, RTG4, SAMICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, TSHARC, USBCheck, VariSense, VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. The Adaptec logo, Frequency on Demand, Silicon Storage Technology, Symmcom, and Trusted Time are registered trademarks of Microchip Technology Inc. in other countries.
GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
© 2021, Microchip Technology Incorporated and its subsidiaries. All Rights Reserved.
ISBN: 978-1-5224-9383-9
Quality Management System
For information regarding Microchip’s Quality Management Systems, please visit www.microchip.com/quality.

Worldwide Sales and Service

Corporate Office
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support:
www.microchip.com/support
Web Address: www.microchip.com
Atlanta Duluth, GA
Tel: 678-957-9614
Fax: 678-957-1455
Austin, TX
Tel: 512-257-3370
Boston Westborough, MA
Tel: 774-760-0087
Fax: 774-760-0088
Chicago Itasca, IL
Tel: 630-285-0071
Fax: 630-285-0075
Dallas Addison, TX
Tel: 972-818-7423
Fax: 972-818-2924
Detroit Novi, MI
Tel: 248-848-4000
Houston, TX
Tel: 281-894-5983
Indianapolis Noblesville, IN
Tel: 317-773-8323
Fax: 317-773-5453
Tel: 317-536-2380
Los Angeles Mission Viejo, CA
Tel: 949-462-9523
Fax: 949-462-9608
Tel: 951-273-7800
Raleigh, NC
Tel: 919-844-7510
New York, NY
Tel: 631-435-6000
San Jose, CA
Tel: 408-735-9110
Tel: 408-436-4270
Canada – Toronto
Tel: 905-695-1980
Fax: 905-695-2078| Australia – Sydney
Tel: 61-2-9868-6733
China – Beijing
Tel: 86-10-8569-7000
China – Chengdu
Tel: 86-28-8665-5511
China – Chongqing
Tel: 86-23-8980-9588
China – Dongguan
Tel: 86-769-8702-9880
China – Guangzhou
Tel: 86-20-8755-8029
China – Hangzhou
Tel: 86-571-8792-8115
China – Hong Kong SAR
Tel: 852-2943-5100
China – Nanjing
Tel: 86-25-8473-2460
China – Qingdao
Tel: 86-532-8502-7355
China – Shanghai
Tel: 86-21-3326-8000
China – Shenyang
Tel: 86-24-2334-2829
China – Shenzhen
Tel: 86-755-8864-2200
China – Suzhou
Tel: 86-186-6233-1526
China – Wuhan
Tel: 86-27-5980-5300
China – Xian
Tel: 86-29-8833-7252
China – Xiamen
Tel: 86-592-2388138
China – Zhuhai
Tel: 86-756-3210040| India – Bangalore
Tel: 91-80-3090-4444
India – New Delhi
Tel: 91-11-4160-8631
India – Pune
Tel: 91-20-4121-0141
Japan – Osaka
Tel: 81-6-6152-7160
Japan – Tokyo
Tel: 81-3-6880- 3770
Korea – Daegu
Tel: 82-53-744-4301
Korea – Seoul
Tel: 82-2-554-7200
Malaysia – Kuala Lumpur
Tel: 60-3-7651-7906
Malaysia – Penang
Tel: 60-4-227-8870
Philippines – Manila
Tel: 63-2-634-9065
Singapore
Tel: 65-6334-8870
Taiwan – Hsin Chu
Tel: 886-3-577-8366
Taiwan – Kaohsiung
Tel: 886-7-213-7830
Taiwan – Taipei
Tel: 886-2-2508-8600
Thailand – Bangkok
Tel: 66-2-694-1351
Vietnam – Ho Chi Minh
Tel: 84-28-5448-2100| Austria – Wels
Tel: 43-7242-2244-39
Fax: 43-7242-2244-393
Denmark – Copenhagen
Tel: 45-4485-5910
Fax: 45-4485-2829
Finland – Espoo
Tel: 358-9-4520-820
France – Paris
Tel: 33-1-69-53-63-20
Fax: 33-1-69-30-90-79
Germany – Garching
Tel: 49-8931-9700
Germany – Haan
Tel: 49-2129-3766400
Germany – Heilbronn
Tel: 49-7131-72400
Germany – Karlsruhe
Tel: 49-721-625370
Germany – Munich
Tel: 49-89-627-144-0
Fax: 49-89-627-144-44
Germany – Rosenheim
Tel: 49-8031-354-560
Israel – Ra’anana
Tel: 972-9-744-7705
Italy – Milan
Tel: 39-0331-742611
Fax: 39-0331-466781
Italy – Padova
Tel: 39-049-7625286
Netherlands – Drunen
Tel: 31-416-690399
Fax: 31-416-690340
Norway – Trondheim
Tel: 47-72884388
Poland – Warsaw
Tel: 48-22-3325737
Romania – Bucharest
Tel: 40-21-407-87-50
Spain – Madrid
Tel: 34-91-708-08-90
Fax: 34-91-708-08-91
Sweden – Gothenberg
Tel: 46-31-704-60-40
Sweden – Stockholm
Tel: 46-8-5090-4654
UK – Wokingham
Tel: 44-118-921-5800
Fax: 44-118-921-5820

© 2021 Microchip Technology Inc. and its subsidiaries Application Note DS00004325A-page 16

Documents / Resources

| MICROCHIP AN4325 UHF ATA Product Application and Design [pdf] User Guide
AN4325 UHF ATA Product Application and Design, AN4325, UHF ATA Product Application and Design, Application and Design
---|---

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>