WILCS02IC and WINCS02IC Programming and ...

Programming and Calibration User's Guide - WILCS02IC ...

4 days ago — This user guide provides a comprehensive overview of the programming and calibration processes for the. WILCS02IC (Wi-Fi Link Controller) and WINCS02IC ...

WILCS02IC and WINCS02IC Programming and ...

WILCS02IC and WINCS02IC Programming and Calibration User's Guide

PDF Viewing Options

Not Your Device? Search For Manuals or Datasheets below:

File Info : application/pdf, 0 Pages, 1.63MB

Document DEVICE REPORTProgramming-and-Calibration-WILCS02IC-and-WINCS02IC-User-Guide-DS50003815

Programming and Calibration User's Guide
WILCS02IC and WINCS02IC
www.microchip.com Product Pages: WILCS02IC, WINCS02IC
Introduction
This user guide provides a comprehensive overview of the programming and calibration processes for the WILCS02IC (Wi-Fi® Link Controller) and WINCS02IC (Wi-Fi Network Controller) devices. Although these devices serve different functions, one as a link controller and the other as a network controller, the programming and calibration steps are identical for both.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 1

WILCS02IC and WINCS02IC
Table of Contents
Introduction........................................................................................................................................................................... 1
1. Quick References...........................................................................................................................................................3 1.1. Hardware Prerequisites.................................................................................................................................... 3 1.2. Software Prerequisites...................................................................................................................................... 3 1.3. Acronyms and Abbreviations........................................................................................................................... 3
2. Device Programming.................................................................................................................................................... 4 2.1. Programming Unsecured Device: Boot Mode Disabled................................................................................4 2.2. Programming Secured Device........................................................................................................................10
3. Calibration....................................................................................................................................................................12
4. External Calibration Flow........................................................................................................................................... 14 4.1. Powering ON the Device................................................................................................................................. 15 4.2. Firmware Programming.................................................................................................................................. 15 4.3. RF Setup Loss Estimation................................................................................................................................ 15 4.4. Erase Flash Configuration............................................................................................................................... 15 4.5. RF TX Calibration.............................................................................................................................................. 15 4.6. RF RX Calibration..............................................................................................................................................17 4.7. Set Parameters.................................................................................................................................................17 4.8. Test Rate Condition......................................................................................................................................... 17 4.9. Commit Result to Device.................................................................................................................................17 4.10. Save Result to File............................................................................................................................................ 17
5. Appendix A................................................................................................................................................................... 18
6. Document Revision History....................................................................................................................................... 24
Microchip Information....................................................................................................................................................... 25 Trademarks.................................................................................................................................................................. 25 Legal Notice..................................................................................................................................................................25 Microchip Devices Code Protection Feature............................................................................................................25

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 2

WILCS02IC and WINCS02IC Quick References

1. Quick References
1.1 Hardware Prerequisites
· MPLAB Programmers: MPLAB® SNAP MPLAB® PICkitTM 5 In-Circuit Debugger MPLAB® ICD 5 In-Circuit Debugger/Programmer
1.2 Software Prerequisites
· WILCS02IC/WINCS02IC firmware image The latest version of the combined firmware can be downloaded from the respective product pages of WILCS02IC and WINCS02IC.
1.3 Acronyms and Abbreviations

Table 1-1. Acronyms and Abbreviations
Acronyms and Abbreviations DFU DUT EVM HUT ICSPTM IPE JTAG LNA PGC PGD RSSI SDADC TSSI UART

Description Device Firmware Update Device Under Test Error Vector Magnitude Hardware Under Test In-Circuit Serial ProgrammingTM Integrated Programming Environment Joint Test Action Group Low-noise Amplifier Programming Clock Programming Data Received Signal Strength Indicator Sigma-Delta Analog-to-Digital Converter Transmit Signal Strength Indicator Universal Asynchronous Receiver-Transmitter

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 3

WILCS02IC and WINCS02IC Device Programming
2. Device Programming
The WILCS02IC and WINCS02IC parts are shipped with the Secure Boot mode disabled. Perform calibration and RF testing and enable the Secure Boot mode to ensure secure operation of the final product. Note:Enabling the Secure Boot mode is irreversible.
The programming process and tools vary depending on whether the Secure Boot mode is enabled or disabled. This section outlines these differences and details the required tools and interfaces for each scenario.
Figure 2-1. Programming and Firmware Update vs Interface

2.1 Programming Unsecured Device: Boot Mode Disabled
By default, the WILCS02IC and WINCS02IC devices ship from the factory with Secure Boot mode disabled and no firmware pre-loaded. Follow these steps to program the device in this mode:
1. Connect the Device: Connect the device to the programming interface using a 2-wire interface and a hardware programmer tool.
2. Use MPLAB® IPE: Open the Microchip MPLAB Integrated Programming Environment (IPE) tool.
3. Select the Device: Choose the appropriate device model (WILCS02IC/WINCS02IC) in the MPLAB IPE.
4. Load Firmware: Load the WILCS02IC/WINCS02IC combined (HUT and Mission mode) firmware file to program onto the device.
5. Program the Device: Initiate the programming process through the MPLAB IPE interface.

Figure 2-2. Programming Interface (Unsecured Device)

WILCS02IC/ WINCS02IC
PGC4 34

WILCS02_VDD/ WINCS02_VD D

VDD\VTG PGC

PGD4 35 MCLR 36

PGD MCLR

Microchip MPLAB
Programmer

GND

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 4

2.1.1 2.1.2

WILCS02IC and WINCS02IC Device Programming
2-wire JTAG (ICSPTM) Interface
The In-Circuit Serial ProgrammingTM (ICSP) interface uses two lines, data and clock, to perform programming.

The table below details the pinout of the 2-wire ICSP interface:

Table 2-1. 2-wire JTAG (ICSPTM) Interface
WILCS02IC/WINCS02IC Pin No Signal

#34

PGC4

#35

PGD4

VCC

#36

MCLR

GND

Function Programming Clock (Clock signal for data synchronization)
Programming Data (Data line for programming and reading)
Power Supply
Master Clear
Ground

Description
The PGC line provides the clock signal that synchronizes data transmission between the programmer and the target device. It is typically driven by the programmer.
The PGD line carries the data being sent to or received from the target device. It is bidirectional, allowing for both programming and reading operations.
This pin supplies the necessary voltage to the target device during programming (or) to read the target voltage.
This pin is used to reset the device. It is typically driven by the programmer.
This pin serves as the reference point for the voltage levels in the circuit. It is essential for establishing a common ground between the programmer and the target device.

Programmer (Hardware Tool)
To program the device through the 2-wire JTAG (ICSPTM) interface, use any of the following hardware tools: · MPLAB® ICD 5 In-Circuit Debugger/Programmer · MPLAB PICkitTM 5 In-Circuit Debugger
· MPLAB SNAP

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 5

Figure 2-3. MPLAB® Programmer

WILCS02IC and WINCS02IC Device Programming

Following figure details the pinout of the MPLAB SNAP and PICkit5 tool Figure 2-4. MPLAB® PICkit5/SNAP Pinout
ICD5 comes with a Target connector RJ-45/RJ-11. Figure 2-5. MPLAB® ICD5 Programmer

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 6

Figure 2-6. 8-Pin Modular Connector

WILCS02IC and WINCS02IC Device Programming

The following table details the pinout of the ICD5 modular RJ-45/RJ-11 target connector:

Table 2-2. ICD5 Modular Connector Pinout
Pin# 8 7 6 5 4 3 2 1

Pin Name TTDI TVPP TVDD GND PGD PGC TAUX TTMS

Debugger Adapter Board
The Debugger Adapter Board is a connectivity board that gives MPLAB ICD 5 or MPLAB PICkit 5 debuggers cable compatibility to target boards.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 7

Figure 2-7. Debugger Adapter Board

WILCS02IC and WINCS02IC Device Programming

2.1.3

The user can have a programming SMD test points on the board, or they can have a separate programming header that is compatible with the MPLAB SNAP and Pickit5 or with ICD5.
For detailed instructions on using the programmer, refer to the corresponding user guide.
MPLAB® Integrated Programming Environment (IPE)
Support for programming the WILCS02IC and WINCS02IC devices are available on the MPLAB IPE. Select WILCS02IC/WILCS02IC for the "Device" based on the device used on the target board.
Figure 2-8. MPLAB IPE WILCS02IC Device Programming

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 8

Figure 2-9. MPLAB IPE WINCS02IC Device Programming

WILCS02IC and WINCS02IC Device Programming

2.1.4

For more details on the configuration option to select the 2-wire JTAG (ICSPTM) interface on the MPLAB IPE, refer to the Knowledge Base Article (KBA) on Programming/debugging Microchip microcontrollers using JTAG.
WILCS02IC/WINCS02IC Firmware Image File
The firmware to be used for programming the WILCS02IC and WINCS02IC devices is a combined firmware. Combined firmware means that it integrates two application functions in a single firmware. The first part consists of a dedicated Hardware Under Test (HUT) application, supporting RF testing and calibration. The other part contains the mission mode application, enabling the WILCS02IC to function as a link controller and the WINCS02IC as a network controller.
Download the latest version of this combined firmware (factory firmware) from the respective product pages for WILCS02IC and WINCS02IC.
Note:Ensure the correct firmware (factory firmware) is used for each device type. The WILCS02IC requires the link controller firmware, while the WINCS02IC requires the network controller firmware. Flashing the wrong firmware may lead to device malfunction and performance issues.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 9

Figure 2-10. HUT Firmware vs Mission Mode Firmware

WILCS02IC and WINCS02IC Device Programming

HUT Application

HUT Mode - Enabled
HUT Application - Hardware Under Test - For RF Calibration & RF Testing during validation, regulatory certification and production tests.

Mission Mode Application

HUT Mode - Disabled
Mission Mode Application - Device function as an link-controller/network controller in an application mode.

After loading the combined firmware, the device initially boots in HUT mode. The MCHPRT3 Radio Test tool, which supports both WILCS02IC and WINCS02IC, includes a special command to disable HUT mode. Disabling HUT mode allows the device to boot in Mission mode, where it runs the link or network controller application firmware. Note:No command exists to revert the device back to HUT mode. To switch it back, reprogram the device with the same combined firmware file.
2.2 Programming Secured Device
When Secure Boot mode is enabled, the 2-wire JTAG (ICSPTM) interface becomes inaccessible for further programming. In this case, perform any firmware updates using the Device Firmware Update (DFU) utility through the DFU UART interface. The PGC4/PGD4 pins function as DFU_RX and DFU_TX.
The WILCS02IC/WINCS02IC devices provide a fail-safe device firmware upgrade by utilizing two image slots in the Flash map. By default, the initial firmware programmed via the 2-wire ICSP uses the Image1 partition to store the default firmware.
The standard firmware for WILCS02IC and WINCS02IC is available on their respective product pages. The release package includes the firmware image binary file.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 10

Figure 2-11. Flash Map

WILCS02IC and WINCS02IC Device Programming

2.2.1

These firmware images contain a 4-byte sequence number in the header that is used by the boot ROM to determine which image to boot on every power-up. The boot ROM always selects the firmware image with the lowest sequence number among the two partitions. If both images have the same sequence number, the boot ROM boots the image in the higher memory address (0x600F0000) or from the Image 2 partition.
The sequence numbers with all zeros and all 0xFFs are reserved and considered invalid. During DFU programming, the boot ROM validates the firmware and checks its authenticity by verifying the signature. If the firmware is not authentic (in other words, not signed by Microchip), the boot ROM invalidates the image by setting the sequence number to zero, thereby rejecting the firmware image.
DFU Utility
The DFU utility is a Python-based tool that supports the erase and write operations on the WILCS02IC/WINCS02IC device's Flash memory. It also enables the modification of the image sequence number and source address in the header section. The DFU utility is available in the WILCS02IC/WINCS02IC product page. For more details on using this DFU utility, refer to the DFU Utility section on the following application developer guides:
· WILCS02 Wi-Fi Link Controller Application Developer's Guide
· WINCS02 Application Developer's Guide

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 11

WILCS02IC and WINCS02IC Calibration

3. Calibration
Calibration is essential for ensuring high performance in both transmission (TX) and reception (RX) stages. Proper calibration optimizes power levels and frequency stability, and minimizes distortion, which enhances overall signal quality and range. Calibration aligns the device with intended specifications, compensates for manufacturing tolerances and adjusts for environmental factors like temperature changes.

Calibration can be classified into Internal Calibration and External Calibration based on the approach:

Table 3-1. Calibrations
Internal Calibration
This process is conducted entirely within the system, leveraging the device's own circuitry and software. The WILCS02IC and WINCS02IC devices have built-in selfcalibration capabilities that adjust performance parameters based on internal sensors and control loops. Internal calibration is often automated, triggered on device start-up and periodically to compensate for drift due to factors like temperature.

External Calibration
This calibration relies on external measurement equipment, such as spectrum analyzers and signal generators like Litepoint IQXEL, to accurately measure and adjust RF performance. It is usually more precise because specialized equipment provides a high level of accuracy and sensitivity, making it ideal for initial calibration during manufacturing.

Calibration data is stored in a Non-Volatile Memory (NVM) and read back by the firmware during the boot-up sequence and while performing periodic calibration.
This document focuses only on external calibration, as the internal calibration process is automated and handled by the firmware.
External calibration must be performed in a controlled environment by powering the device with a 3.3V operating voltage and an ambient temperature of +25°C with a 50 matched load connected to the device RF port.
External calibration can be performed only when the device is in the HUT Firmware mode. To control the device with HUT firmware, use the MCHPRT3 Radio Test Tool, which supports the GUI interface and also the CLI/DLL interface. UART1 is the interface needed to connect the WILCS02IC and WINCS02IC to the MCHPRT3 tool for calibration and RF testing. The pin out of the UART1 interface is as detailed below.

Table 3-2. WILCS02IC and WINCS02IC - UART1 Interface Pinout

Pin#

Pin Name

UART1_TX

UART1_RX

Pin Function UART1 Transmit (Output) UART1 Receiver (Input)

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 12

Figure 3-1. Calibration Test Setup Power Supply

2-wire

Test Jig or

Pin#34 - PGC4 Pin#35 - PGD4

JTAG inetrface

Programmer

USB

Custom board

Pin#9 - UART1_TX Pin#4 -UART1_RX

UART

USB to UART Converter

USB

WILCS02IC and WINCS02IC Calibration
Test PC

DUT (WILCS 02IC/WINCS02IC )
RF Test Point or u.FL connector
on the board

RF test point probe Or u.FL connector probe

~10dB Attenuator

RF Coaxial Cable

Control
RF Test Equipment

· Test Jig or Custom Board: Custom PCB designed with WILCS02IC/WINCS02IC · Programming and Control Interface: 2-wire JTAG (ICSPTM) interface for firmware programming and
UART1 interface for calibration and RF testing control · Test Equipment: Wi-Fi® tester like Litepoint IQXEL
· RF Test Setup Connection: Conducted RF test setup via RF test point or through an RF connector U.FL
· Test PC: with MPLAB® IPE tool for programming and MCHPRT3 tool for calibration and RF testing
Note:For designs using a PCB antenna with an RF test point, test fixture tuning is required. For more details, refer to Appendix A.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 13

WILCS02IC and WINCS02IC External Calibration Flow
4. External Calibration Flow
The MCHPRT3 Radio Test Tool User Guide (for more details on the MCHPRT3 tool, refer to the product-specific user guide available on the MCHPRT3 Product page) for WILCS02IC and WINCS02IC devices outlines the calibration flow and available GUI control options. For initial validation, users must follow the same GUI steps. To automate this process for production, users need to implement the corresponding CLI/DLL control functions in a test script. Figure 4-1. WILCS02IC and WINCS02IC Recommended Production Test Flow
Power ON
Firmware Programming
RF Setup Loss Estimation Erase Flash
Configuration
RF TX Calibration
RF RX Calibration
Test Rate Condition
Commit Result to Device
Save Result to File

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 14

4.1 Powering ON the Device

WILCS02IC and WINCS02IC External Calibration Flow

Power up the device in a controlled environment with an operating supply voltage of 3.3V, ambient temperature of +25°C and a 50 matched load connected to the device.
4.2 Firmware Programming
To program the combined firmware, use the 2-wire JTAG (ICSPTM) interface for the unsecured device through MPLAB® IPE. For the secured device, utilize DFU_UART through the DFU Utility.
4.3 RF Setup Loss Estimation

To run the calibration, measure the setup loss first, which includes the insertion loss of the test probe, attenuator and cable loss. Adjust the setup loss value using all the measurement values or configuration settings.
4.4 Erase Flash Configuration

The calibration process starts with erasing the Flash configuration, such as calibration parameters and gain table offset. This is a mandatory step to ensure the proper calibration values are stored.

By default, erasing the Flash Configuration removes the factory-stored MAC address and switches the device to a different operating mode. To address this, the MCHPRT3 tool follows a specific sequence to restore the factory MAC address and return the device to HUT mode. The MCHPRT3 tool executes the following steps in the background when erasing Flash configurations:
1. Read the MAC address.

2. Erase the Flash configuration.

3. Reset the device.

4. Write the MAC address back to the device.

5. Set the app mode to HUT.

6. Reset the device again.
4.5 RF TX Calibration

Device calibration is performed under the following test conditions unless specified otherwise:

· Channel: 2442 MHz

· Data Rate: MCS7 (802.11n mode)

4.5.1 Start TX Calibration
1. Configure SDADC: The internal Sigma-Delta Analog-to-Digital Converter (SDADC) is configured for temperature and voltage calibration automatically when the Start TX Process begins.
2. Set Conditions: Set the operating voltage to +3.3V, and maintain the ambient temperature at +25°C.
3. Wait for Response: After initiating the calibration process, wait for a Success response from the MCHPRT3 tool before proceeding to the next step.
4.5.1.1 First Tune
1. Initiate First Tune: Begin the First Tune process to transmit the Device Under Test (DUT) on the specified channel (2442 MHz) using the MCS7 data rate.
2. Measure Power: Measure the RF transmit power with a Wi-Fi® tester and calculate the total transmit power, including any setup loss.
3. Input Power Feedback: Enter the total power (in dBm) as feedback into the input power field and initiate the Check First Tune Result process.
Success: If the required target power of +15.5 dBm (with a tolerance of ±0.25 dB) is achieved, the second and third tune processes are not necessary. The MCHPRT3 tool will display a success response.

User Guide
© 2024 Microchip Technology Inc. and its subsidiaries

DS50003815A - 15

WILCS02IC and WINCS02IC External Calibration Flow
Not Success: If the target power is not achieved, the MCHPRT3 tool will display Not Success. Proceed to the Second Tune process.
4.5.1.2 Second Tune
1. Initiate Second Tune: Start the Second Tune process by transmitting the DUT on the same channel and data rate with a calculated offset from the First Tune.
2. Measure Power: Measure the RF transmit power again and calculate the total transmit power, including any setup loss.
3. Input Power Feedback: Enter the total power (in dBm) as feedback into the input power field, then initiate the Second Tune Result process.
Success: If the required target power of +15.5 dBm (with a tolerance of ±0.25 dB) is achieved, the third tune process is not needed. The MCHPRT3 tool will display a success response.
Not Success: If the target power is not achieved, the MCHPRT3 tool will display Not Success. Proceed to the Third Tune process.
4.5.1.3 Third Tune
1. Initiate Third Tune: Start the Third Tune process by transmitting the DUT on the same channel and data rate with a calculated offset from the Second Tune.
2. Measure Power: Measure the RF transmit power and calculate the total transmit power, including any setup loss.
3. Input Power Feedback: Enter the total power (in dBm) as feedback into the input power field, then initiate the Third Tune Result process.
Typical Outcome: If the test setup functions correctly, the targeted TX power of +15.5 dBm (with a tolerance of ±0.25 dB) is usually tuned during the Second or Third Tune process.
Retry: If the target power is not achieved even after the third tuning attempt, proceed with a fourth tuning attempt. If multiple retries still fail to achieve the target power, abort the calibration process. Check the test setup thoroughly, then restart the calibration process from the beginning.

4.5.2

Read Base TX Gain Index
This shows the baseTxGainIndex corresponding to the last successfully tuned TX power level of +15.5 dBm.

4.5.3

Transmit Signal Strength Indicator (TSSI) and Power Detector Reference Tuning
This step involves tuning the Transmitter Signal Strength Indicator (TSSI) and the power detector offset across a range of TxGainIndex values. The goal is to achieve optimal performance by evaluating the power levels and Error Vector Magnitude (EVM) at various gain indices. The tuning process involves seven specific TxGainIndex offsets from the calculated baseTxGainIndex. Each gain index is expected to yield variations in the transmitted power level.
1. Initiate Read TSSI and PDREF1: DUT transmits the signal with an adjusted gain offset 1 from the baseTxGainIndex value.
2. Measure Power Level and EVM: Use a Wi-Fi® tester to measure the TX Power Level (including the setup loss) and EVM.
3. Feedback and Set Power: Input the measured TX power and EVM values into the MCHPRT3 tool and trigger Set Power 1. This completes the first TSSI and PDREF1 tuning process and provides a Success response.
4. Repeat for Remaining TxGainIndex Steps: Follow the same procedure for the remaining six TxGainIndex offsets.
5. Stop TX Calibration: Initiate the Stop TX Calibration process and wait for a success message response from the MCHPRT3 tool.

DS50003815A - 16

4.6
4.7 4.8
4.9 4.10

RF RX Calibration

WILCS02IC and WINCS02IC External Calibration Flow

RF receiver calibration fine-tunes and adjusts a Radio Frequency (RF) receiver to ensure optimal performance in terms of sensitivity, selectivity and signal accuracy. To run the RX calibration, configure the Wi-Fi ® tester in Signal Generator mode. Generate a Wi-Fi pattern with an 802.11n MCS7 data rate on the 2442 MHz channel and feed it to the DUT (WILCS02IC/WINCS02IC) at different power levels at the DUT port (including the setup loss) as follows:

1. Feed a -20 dBm signal from the Wi-Fi tester and read the Received Signal Strength Indicator (RSSI) level. The MCHPRT3 tool will provide the RSSI value read by the device and the corresponding LNA configuration, along with the test status as Success.
2. Repeat the same process for power levels of -35 dBm, -45 dBm, -50 dBm and -65 dBm.

Ensure that the LNA configuration sequence matches 0, 3, 3, 4, 7 or 0, 3, 4, 4, 7 for each level of the RSSI tests. Also, ensure that the read RSSI values are closer to the signal power level from the Wi-Fi tester.

Finally, process the stop RX calibration steps, which shows the calculated Gain correction for each RSSI test case, along with a success response.
Set Parameters

The Set Parameter configures the device for the next step of the test.
Test Rate Condition

The test rate condition evaluates the performance of channel-1 (2412 MHz) and channel-13 (2472 MHz).

1. Start the Test Rate Cond Prepare process. The MCHPRT3 tool will provide a success message.

2. Start the Test Rate Cond Start CH1 process. The DUT will transmit on the Channel 1 MCS7 data rate. Measure the transmit power and EVM on the Wi-Fi® tester, then feed the measurements back to the MCHPRT3. Trigger the Set Power 1 command, and wait for a success response. Follow the same steps for Channel 13.
3. After completing both CH1 and CH13, check the test status by initiating Test Rate Cond Check Result. If the response is Success and the result is 1, proceed with the next step of the calibration.
If the response is Not success or the result is not 1, repeat the Test Rate Condition for CH1 and CH13.
Commit Result to Device

After completing all the tests, commit the calibration test results to the Flash.
Save Result to File

Save the calibration test results to a file and load them again. This feature proves useful during initial validation and helps maintain a log during production calibration and testing.

DS50003815A - 17

WILCS02IC and WINCS02IC Appendix A
5. Appendix A
Tuning a Production Test Fixture for Efficient RF Measurement Using RF Test Points
1. Conduct RF calibration and testing to ensure optimal performance in production. 2. For designs with u.FL or similar connectors, use a compatible RF probe for calibration and
measurements. u.FL provides conducted RF test data directly; therefore, no additional steps are required. This appendix details the additional tuning process required for a PCB antenna-based design with an RF test point; so u.FL-based designs can ignore this additional tuning process.
Figure 5-1. Module/Board with u.FL Connector and Test Probe

3. For designs with a PCB antenna, include RF test points for calibration and RF TX/RX performance testing. Figure 5-2. Board with PCB RF Test Point
Below is the reference schematic featuring a PCB antenna and an RF test point.

DS50003815A - 18

Figure 5-3. Design with RF Test Point

WILCS02IC and WINCS02IC Appendix A

Test Fixture RF Test Point Measurement Calibration
This section provides detailed instructions on setting up and calibrating the production test fixture with an RF test point to ensure efficient measurements prior to deployment. Figure 5-4. Test Fixture RF Test Point Measurement Calibration
1. RF Testing in bench setup: Measure TX Power and TX EVM from a Golden Reference Unit a. Isolate the PCB Antenna: · Disconnect the PCB antenna from the RF front end circuitry by removing its matching component R404. b. Attach RF Pigtail for Measurements: · Solder a semi-rigid RF pigtail to the RF front-end output, specifically to the C408 pad connected to the chip.

DS50003815A - 19

Figure 5-5. RF Semi-Rigid Pigtail

WILCS02IC and WINCS02IC Appendix A

c. Reference Measurement: · Perform RF calibration and measure RF TX power and EVM with the RF pigtail attached, using the Device Under Test (DUT) in TX mode on channel-6 MCS7 data rate. · This Golden Reference Unit provides reference values for tuning the production test fixture.
2. Stub Tuner adjustment and S11 measurement: a. Restore the Antenna Matching Network: Remove the RF pigtail, solder the antenna matching components (R404) back onto the board. b. Preparing for Conducted RF Testing: As conducted RF testing with the PCB radiated antenna connected is challenging, detune the antenna by placing a copper shield tape or a copper plate near the PCB antenna as illustrated in the following figure. Figure 5-6. Reference Setup with Copper Shield Tape
Copper Tape (Cap)
Copper Tape Module
RF Pigtail Sockets with 2 Module Holders
Note:The image displays a production setup that includes two sockets covered with copper shield tape. c. Connect to Stub Tuner Setup: Attach the custom board or load board of WILCS02IC/ WINCS02IC to the stub tuner setup.

DS50003815A - 20

Figure 5-7. Stub Tuner Setup

WILCS02IC and WINCS02IC Appendix A

d. Tune the Stub Tuner: i. Adjust the three stub tuner legs (A1, A2 and A3) until the DUT TX power and TX EVM levels closely match the golden reference setup. ii. Stop tuning and lock the knobs when the TX EVM improves to better than -29.5 dB.
Figure 5-8. Recreating Golden Setup Performance Result

e. Measure S11 of Stub Tuner:
i. After achieving the required TX Power and TX EVM values that match the golden reference unit, remove the stub tuner connection from the RF test point end. Retain

DS50003815A - 21

WILCS02IC and WINCS02IC Appendix A
the other end connection to the 10 dB attenuator, then connect to a 50 load in place of Litepoint IQxel. ii. Measure the S11 of the stub-tuner setup as illustrated in the following figure. Figure 5-9. Tuner S11 Impedance Measurement
3. RF Network Matching: a. Remove the stub tuner from the setup. b. Ensure the load board includes pi-section components for RF matching. c. Adjust the load board tuning components to match the stub-tuned S11 impedance value.

DS50003815A - 22

Figure 5-10. Replace Stub Tuner by Tuning Components

WILCS02IC and WINCS02IC Appendix A

d. After tuning, remove the VNA setup and connect the load board tuning components to the RF Test Point. Verify that the RF TX power and TX EVM match the previous golden reference and stub tuner measurements.
Figure 5-11. Replace Stub Tuner by Tuning Components

4. Ready for Production: After the TX Power and TX EVM are confirmed through the RF test point measurements and meet the required standards, the test fixture is ready for mass production. It is recommended to keep a golden unit to periodically validate the setup for each new production batch.

DS50003815A - 23

WILCS02IC and WINCS02IC Document Revision History

6. Document Revision History
The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.

Table 6-1. Document Revision History

Revision

Date

12/2024

Section Document

Description Initial Revision

DS50003815A - 24

WILCS02IC and WINCS02IC
Microchip Information
Trademarks
The "Microchip" name and logo, the "M" logo, and other names, logos, and brands are registered and unregistered trademarks of Microchip Technology Incorporated or its affiliates and/or subsidiaries in the United States and/or other countries ("Microchip Trademarks"). Information regarding Microchip Trademarks can be found at https://www.microchip.com/en-us/about/legalinformation/microchip-trademarks.
ISBN: 979-8-3371-0342-6
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 WHETHER 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.
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 products are 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.

DS50003815A - 25