This document provides detailed information about the MCHPRT2 tool, which allows the user to easily
configure, evaluate and test an RF system. This tool simplifies the effort during the early stage of
development, regulatory certification and production testing. The MCHPRT2 tool with v1.0 is used for this
demonstration. MCHPRT2 is a Windows®-based software program.
Note: The ATWINC, ATWILC, ATBTLC, and ATSAMB denotes the following:
• ATWINC15x0
• ATWINC3400
• ATWILC1000
• ATWILC3000
• ATBTLC1000
• ATSAMB11
Features
The MCHPRT2 tool includes the following functions for the ATWINC/ATWILC and ATBTLC/ATSAMB
devices:
• Flexible Graphical User Interface (GUI) configuration Options
• Inbuilt Command Line Interpreter (CLI)
• Wi-Fi® RF Performance Evaluation
• Bluetooth® Low Energy (BLE) RF Performance Evaluation
• Continuous Wave (CW) Transmitter
• RF Frequency Offset Calibration
• e-Fuse Programming
• Register Read/Write
• Register Range Dump
• Received Signal Strength Indicator (RSSI) Reading
This chapter provides the hardware and software prerequisites for using MCHPRT2 tool with the
ATWINC/ATWILC series and ATBTLC/ATSAMB series.
1.1 Hardware Prerequisites
This section provides the hardware tools that are required to test the RF system. ATWINC/ATWILC is
connected to the GUI using Aardvark™ or serial bridge. SAM-ICE™ is used to connect ATBTLC/ATSAMB
to GUI.
1.1.1 Aadvark I2C Host Adapter
Aardvark I2C/HCI Host adapter is used to interface PC via USB to I2C pins of ATWINC/ATWILC. The
same is shown in the following figure. For more information, refer to http://www.totalphase.com/products/
aardvark-i2cspi/.
Figure 1-1. Aardvark I2C/HCI Host Adapter
ATWINC/ATWILC/ATSAMB/ATBTLC
Prerequisite
1.1.2 USB - UART Converter
This USB-UART converter (MCP2200) Breakout Module) will be used to interface PC to the UART DTM
interface of ATWINC3XXX, ATBTLC1000 and ATSAMB11 devices. Any generic USB-UART converter can
also be used.
The AT91SAM-ICE is a JTAG emulator designed for ARM® core based MCUs and MPUs. It is used to
program test firmware. For more information, refer to http://www.microchip.com/DevelopmentTools/
ProductDetails.aspx?PartNO=at91sam-ice
Figure 1-3. AT91SAM-ICE JTAG Emulator
ATWINC/ATWILC/ATSAMB/ATBTLC
Prerequisite
1.2 Software Prerequisite
1.2.1 Serial Bridge Connection (ATWILC/ATWINC)
MCHPRT2 GUI can be operated without the Aadvark tool with the help of serial bridge application from
Atmel Studio. In the GUI, instead of I2C select UART. Enter the valid Com port, baud rate and click Init to
start evaluating the RF test system. For more information, see the Serial Bridge Application Note.
1.2.2 MCHPRT2 GUI Tool
The MCHPRT2 tool allows the user to easily configure, evaluate and test an RF system. It simplifies the
effort during the early stage of development. The later sections have a detailed explanation on how the
tool is used to test the RF system.
1.Click the tab for Initialization, eFuse, Wi-Fi, BLE or Register read and write option.
2.It is a function block for the selected tab.
3.CMD command line block.
4.Com port block.
5.Device connectivity status:
– Close: Sub process "MCHPRT" is close.
– Ready: "MCHPRT" is waiting for the command.
– Processing: "MCHPRT" is running.
1.2.2.1 MCHPRT2 Software Architecture
MCHPRT2 is a C# program using MCHPRT command line function for RF test or automation test
example. The following link has an example of process function to open, send and receive the command.
Connect the UART or I2C to PC, and power on the ATWINC/ATWILC/ATBTLC/ATSAMB. Ensure that
ATWINC/ATWILC/ATBTLC/ATSAMB is in the right test mode with the correct pins.
The following table provides the I2C connection for ATWINC/ATWILC 1XXX and 3XXX series.
Table 1-1. I2C Connection
Connections1XXX Module series 1XXX Chip series 3XXX Module series 3XXX Chip series
I2C Slave DataPin 3Pin 33Pin 10Pin 16
I2C Slave clockPin 2Pin 32Pin 11Pin 17
BT_TXDNANAPin 8Pin 14
BT_RXDNANAPin 9Pin 15
Connect the J-Link and power on the ATBTLC/ATSAMB-ZR series. Connect the BT_TXD and BT_RXD
lines to the UART input pins of an USB-UART converter.
ATWINC/ATWILC/ATSAMB/ATBTLC
Prerequisite
The following table provides the J-Link connection for ATBTLC/ATSAMB series. Pin 41-49 is ground
exposed paddle; it must be soldered to system ground.
Table 1-2. J-Link Connection
ConnectionsATBTLC ZR
Module series
SWCLKPin 12Pin 35Pin 12Pin 35
SWDIOPin 13Pin 36Pin 13Pin 36
BT_TXDPin 15Pin 38Pin 15Pin 38
BT_RXDPin 14Pin 37Pin 14Pin 37
Note: MCHPRT/MCHPRT2/HCI_Command tools have DTR enable or disable function on UART.
For example:
SAMB11 Xpro board serial port setting is different, which only supports the following conditions:
serialport.DtrEnable = true;
serialport.Handshake = Handshake.RequestToSend;
serialport.RtsEnable = true;
In MCHPRT/MCHPRT2/hci_command tools DTR must be enabled.
ATBTLC ZR Chip
series
ATSAMB ZR
Module series
ATSAMB ZR Chip
series
1.4 Power-Up/Down Sequence
This section provides the power-up/down sequence for ATWINC/ATWILC/ATSAMB/ATBTLC.
• VDDIO must not fall before RESETN. RESETN and CHIP_EN
can fall simultaneously.
User Guide
DS50002893A-page 8
ATWINC/ATWILC/ATSAMB/ATBTLC
It is mandatory that the ATWINC/ATWILC chip is in the right bootloader state for establishing connection
from GUI through I2C. To do that, the host MCU must power-up the ATWINC/ATWILC chip and then
perform the reset sequence as defined in the figure Power-up/down Sequence (ATWINC/ATWILC). This
is done very easily from the host MCU by calling the nm_bsp_init() and nm_bsp_reset() function. The
code snippet for the same is as shown below,
int main(void)
{/* Initialize the board. */
system_init();
/* Initialize the BSP. */
nm_bsp_init();
nm_bsp_reset();
while(1) {
}
}
1.4.2 Power-up/down Sequence (ATBTLC/ATSAMB)
The power-up/down sequence for ATBTLC/ATSAMB is shown in the following figure. The timing
parameters are provided in following the table. For SAMB11, ensure that the steps referred in Appendix
A5 Erase and Program SAMB11 are followed before establishing connection with MCHPRT2 GUI.
This chapter provides the steps to follow to put the device in Wi-Fi and Bluetooth test mode, and set
registers, eFuse bits and perform firmware upgrade using the MCHPRT2 tool.
2.1 Wi-Fi
2.1.1 Initialization
Perform the following steps for Wi-Fi initialization.
1.Double-click to open the MCHPRT2.exe executable file and, select the interface as “I2C” when
using “I2C” connection. Select the interface as ‘UART’ when using serial bridge UART connection.
2.Select the device from the Device series drop down box.
3.Choose Wi-Fi as the mode from the drop down box.
4.Click Connect to initialize the device.
5.After initialization is complete, the status of the process bar displays Ready.
Figure 2-1. Wi-Fi Initialization
ATWINC/ATWILC/ATSAMB/ATBTLC
Graphical User Interface
Note: The CLI information is displayed on the right hand side.
3.Select the desired data rate from the drop down box and choose the Gain mode (Dynamic/Bypass/
FLASH(WINC1500/WINC3400 only).
Note: In Bypass mode, PPA, PA, and Digital Gain are enabled. The value is set within the
specified value besides PPA, PA, and Digital Gain. In Dynamic and Flash gain mode, PPA, PA, and
Digital Gain are disabled.
4.Enter PPA.
5.Enter PA.
6.Enter Digital Gain (-7 ~ -15).
7.XO offset.
8.Length (0~1024).
9.Frames ( 0 for con’t TX mode).
10. For CW mode of transmission select the check box before Normal, to enter CW mode.
1.Click RSSI start to start receiving the signal strength displayed in the tab next to ccaRSSI.
Note: If a valid Wi-Fi packet is received, the indicator next to the ccaRSSI text box displays as
selected.