WeLink PER200 60Ghz Radio Module User Guide

PER200 60Ghz Radio Module

User Guide

60Ghz Radio Module User Guide
Product Code: PER200 Date: 2/26/2021

1. Introduction

This document will explain the steps required in order to create a network connection using the PRS4601, including driver installation, firmware upgrades, and network configuration.

1.1 Overview
Product Specification Creation
Operating Frequency: 57 – 66 GHz
Channel Bandwidth Setting: 2160 MHz
Channel 1: Fe = 58.32 GHz
Channel 2: Fe = 60.48 GHz
Channel 3: Fe = 62.64 GHz
Channel 4: Fe = 64.80 GHz
Module TX Power: 24.56 dBm nominal at RFIC output
TX EVM: -11 dBm for MCS6/-12 dBm for MCS7/-15 dBm for MCS12
RX Sensitivity: -63 dBm for MCS6/ -62 dBm for MCS7/ -53 dBm for MCS12
Highest Raw Data Rate: 1 -st ream MCS8 ( 2310 Mbps @ QPSK )
Throughput: 1500 Mbps typical with appropriate test setup
Interface: FPC Ribbon Cable
Power Consumption: 4 Watt typical
Module Operating Temperature: -20 to 55 °C

1.2 Definitions and Acronyms
ADC Analog-to-digital converter
AFE Analog Front End
ARC ARC 625D CPU
DWC Design Ware Core
GPIO
LMAC
General Purpose 10
Lower MAC
PIO Programmable 10
PWM Pulse Width Modulator
SSI Synchronous Serial Interface
UART
UMAC
Universal Asynchronous Receiver/ Transmitter
Upper MAC

1.3 Background
The PRS4601 MAC is designed around a pair of ARC 625 CPUs, referred to as Upper MAC (UMAC) and Lower MA
C
(LMAC). These CPUs utilize two independent buses for peripheral connection:

1. An AHB bus which connects to an AHB-Lite fabric and provides access to shared peripherals and memory

2. A dedicated ARC Peripheral Bus

The UMAC and LMAC CPUs share access to the following peripherals:
IPC: Provides atomic inter-processor communication with both locks and events
MAC Timer: Provides a precise over-the-air MAC time (at the MAC_CLK and 1 MHz)
AFE Test, Configuration and Control:

• The UMAC has access to AFE Test and Configuration
• The LMAC has access to AFE Control functions

The UMAC CPU has dedicated access to the following peripherals:
Host Interfaces

• USB 3.0 (and 2.0) Configuration

Other peripherals

• UMAC DMA: to assist in moving data between shared memory and DCCM
• UART: for test and debug
• SSI: for boot and configuration data (via serial flash or EEPROM)
• ARC Timer: general purpose timer (MOX)
• Interrupt control
• GPIO: for boot configuration (straps) and status/control/debug
• PWM: pulse width modulator for LEDs and other status/debug
• Top Level Chip Control: Reset, Power Down, etc.
• General Purpose ADC (not functional in PRS4601)
• A programmable 10 block that allows most 10 pins to be configured as GPIO

The LMAC CPU has dedicated access to the following peripherals:
MAC/PHY Interface Other peripherals

• TX DMA: Used to send data from shared MAC memory to the MAC/PHY

• RX DMA: Used to receive data from MAC/PHY to shared MAC memory

• UART: for test and debug

• SSI: for radio configuration, control and status

• ARC Timer: general purpose timer (MOX)

• Interrupt control

• GPIO: for radio control and status, and general status/debug

• PWM: pulse width modulator for status/debug

• Calibration Timer: to allow precise frequency locking of the crystal oscillator and to allowing
  locking of MAC t ime to an external clock

• A programmable 10 block that allows most 10 pins to be configured as GPIO

2. Functional Description

2.1 Enable Test Mode on Windows Host PC
Before installing drivers for the PRS4601, one must configure the Host to be able to install a test driver
2.1.1 Disable Driver Signing

1. Run command prompt as administrator (enter cmd.exe in search field, right click on it)
2. Enter the following two lines:
   a) bcdedit.exe – set load options DDISABLE_INTEGRITY_CHECKS

b) bcdedit.exe -set TESTSIGNING ON

2.1.2 Adding Test Certificate

1. Open Microsoft Management Console – Type mmc in search and press enter
2. File -> Add/Remove Snap-in
3. Select Certificates and press the Add > button

4. Select the Computer Account radio button
5. Choose Local computer then press the Finish Button
6. Import the prswigigusb certification to Trusted Root and Trusted Publishers
   a) The certificate can be found in \host\win\WinRelease_wlan\

b) To import the certificate, right-click Trusted Root or Trusted Publishers and then select All Tasks ·> Import.

2.2 Installing the Host and Network driver
.. – –
– l1 )(
Actions
Consol• Root …
Mort Actions ►
In order to creat e a network, the PRS4601 boards must be connected to a host computer which has the
appropriate device drivers installed. At the t ime of writing this document, only host computers running the
Windows 7 operating system was supported.

2.2.1 Installing driver on Windows 7
In order to install the host drivers, a user must have the PRS4601 device with a valid firmware image programm
ed.
The steps for inst alling the host driver are detailed below:

1. Plug in the PRS4601 device t o a USB3 port on the host computer. Immediately this provides power to the
   device and a flashing green status LED indicates that the device is ready for use.

2. Navigate to the Device Manager on the host computer (Right cl ick on My Computer and select Properties.
   A link to the Device Manager can be found in the left panel in the opened window)

3. Two unknown device should now be visible under “Other devices” (see Figure below)

Figure 2-1: Missing driver for plugged in PRS4601 device

4. Right click on the first unknown device and select Update Driver Software
5. Select “Browse my computer for driver software” then browse to the appropriate location of the drivers.
6. Select Next to start the installation
7. After the installation complet es, click the Close button
8. Repeat steps 4 t o 7 for the remaining unknown device.

2.3 Loading image onto boards
2.3.1 Loading image onto device for the very first time
The bootloader is used to program the boards for the very first time. The PRS4601 enables communication with
the bootloader via the USB interface assuming the Serial driver was installed (see Section 2.2.1). TeraTerm (or a
ny other terminal application that emulates communication with a CDC device) can be used to verify communication to the bootloader. The user can pressed the “Enter” key or enter the “version” command and view the response.

Before programming the image, the user must decide whether to load the image to:

1. RAM in which case the program would be lost after resetting the device
2. Flash in which case the program would be persisted even after resetting the device

Note: If the status LED on PRS4601 is blinking a green pattern, you can skip this step and go to section 2.3.2. When installing the firmware for the fi rst time the bootloader must be running- this is indicated with a flashing yellow LED.

The download_elf.exe utility is used to load the image to RAM only. This utility must be executed from the same
directory that has the firmware images. Note: Please ensure to ru n this utility as an administrator by right clicking
on the download_elf.exe file and selecting option to “Run as Administrator”.
The download_flash.exe utility is used to load the image to Flash. Similarly, this utility must be executed from the
same directory that has the firmware images. Note: Please ensure to ru n this utility as an administrator by right
clicking on the download_flash.exe fi le and selecting option to “Run as Administrator”.
Note: For the majority of user scenarios, opt ion #2 would generally be preferred.

2.3.2 Loading image onto device that already have a prior image
The image on the board can be upgraded or downgraded by double clicking the prs_flash_bin.bat script provided
with the fi rmware image. The board must be reset for the new image to take effect.

2.4 Creating a Network with two PRS4601s
When attempting to creat e a network between two PRS4601s (wired or wireless), the user may choose to
configure a specific node as the network coordinator (more appropriately known as the PCP in an 802.llad PBS
S network) while configuring the other node as a Stat ion (STA). Alternately, a user may also opt for having the P
CP and STA selections be negotiated allowing the devices to choose among themselves the role each node will p
lay.

2.4.1 Configuring PCP/STA Modes
In order to set the node to PCP or STA mode, we will need to use the Device Manager.
The Device Manager can be found under Control Panel -> Device Manager.
Find the correct network adapter, right click -> properties.

Figure 2-2: Device manager
Then, go to the advanced tab and set:
AMSDU -> ON
Device Mode ·> PCP or STA
Repeat these steps for both nodes, one with Device Mode set to PCP, the other with Device Mode set to STA.

2.4.2 Creatinga network profile
After configuring discovery mode on both host computers, the next step will be to create a profile for the netwo
rk.
This will need to be done on the node set to PCP mode. The steps for doing this is outlined below.
1. Open the Network and Sharing Center from Control Panel
2. Click on the “Manage wireless network” link on the left panel for the window
3. Click Add then choose “Create an ad hoc network”.
4. Choose the Next button after reading the description for setting up a wireless ad hoc network
S. Fill out the form which is used to provide details about network (see Figure below)

Figure 2-3: Creating a network profile
6. Click the Next button after filling form
7. Click the close button after network is ready for use (see Figure below)

Figure 3-2-4: Network profile successfully create

2.4.3 Starting and connect ing to created network
The network must be started from the node that is set to PCP. From the tray icons click on the icon for Wireless
Connection. This should display the network that was created above. Double click on the network name (or Right
Click and choose Connect) to start the network. Once started you should notice the status change to “Waiting for
users” (see Figure below)

The user can also know that the network has been started by looking on the PRS4601 device. There will be a fast
blinking pattern of the green TX LED indicating that frames (in t his case beacons) are being transmitted by the
device.

From the host computer configured to be a STA, the network should now be visible when the user clicks on the
wireless connect ion tray icon. The user can then double click on the network they wish to connect to. Note: this
step is the same as connecting to any wireless network.
If connection was successful, the status will be updated to Connected on both host comput ers.

2.4.4 Setting staticlP addresses for host machines
While each node on the network will be given an IP address automatically, static IP addresses can be configured
for each host. This is not required for traffic to be sent over the network. Setting static IP addresses can be done
from the Adapter properties for the device (same as any other network device) and select ing the Internet Protocol
Version 4 (TCP/1Pv4) properties. Ensure that different IP addresses are used for both devices. Figure# below shows the configuring of static addresses for one of the host machines

3. Appendix

3.1 Appendix A Enabling Driver Signing
If ever the user wants to stop using a computer as a host machine, they can disable test mode with the following
steps:

1. Run command prompt as administrator (enter cmd.exe in search field, right click on it)
2. Enter the following two lines
   a) bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
   b) bcdedit.exe -set TESTSIGNING OFF

3.2 Appendix B Setting up TeraTerm
The steps to configure TeraTerm on first use are described below.
1. Open the previously downloaded TeraTerm application
2. Navigate to Setup->Terminal and apply the following setting(s)
o Receive: AUTO
o Check “Local Echo”
3. Navigate to Setup->Serial Port and apply the following setting(s)
o Baud Rate: 115200

4. Save the changes by navigating to Setup- >Save Setup
Next, you will want to plug in PRS4601 via USB. If you see a flashing yellow light, you will need to inst all new
firmware. If you see a green light, you can updat e existing firmware. If there is no light visible, PRS4601 is not
powered on, and nothing will work.
In either case, open up TeraTerm and choose the correct serial port.
Press enter a few t imes. If there is no firmware, you will get a simple message after the second enter press, but no
commands will work.

If you have a green light on PRS4601, the following commands will give some output to TeraTerm:

FCC Statement:

This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) This device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation.

FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment.

IMPORTANT NOTE:
FCC Radiation Exposure Statement:
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 56 cm between the radiator & your body.

USERS MANUAL OF THE END PRODUCT:
In the users manual of the end product, the end user has to be informed to keep at least 56 cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the FCC radio- frequency exposure guidelines for an uncontrolled environment can be satisfied.

The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user’s authority to operate this equipment.

LABEL OF THE END PRODUCT:
The final end product must be labeled in a visible area with the following ” Contains TX FCC ID:
2A YX4-PER200″.

The FCC part 15.19 statement below has to also be available on the label: This device complies with Part 15 of FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference and (2) this device must accept any interference received, including interference that may cause undesired operation.

This Module may not be integrated into host devices that are addressed for operation inside airplanes/satellites.

Antenna list:

Others
This device is intended only for OEM integrators under the following conditions: 1. The antenna must be installed such that 20 cm is maintained between the antenna and users. 2. The transmitter module may not be co-located with any other transmitter or antenna. As long as the two conditions above are met, additional transmitter testing will not be required. However, the OEM integrator is still responsible for testing their end-product for any additional compliance requirements required for the installed module.

Important Note: In the event that these conditions cannot be met (for example certain laptop configurations or co-location with another transmitter), then the Federal Communications Commission of the U.S. Government (FCC) authorization is no longer considered valid and the FCC ID cannot be used on the final product. In these circumstances, the OEM integrator shall be responsible for re-evaluating the end -product (including the transmitter) and obtaining a separate FCC authorization in the U.S.

OEM Integrators – End Product Labeling Considerations: This transmitter module is authorized only for use in device where the antenna may be installed such that 20 cm may be maintained between the antenna and users. The final end product must be labeled in a visible area with the following: “Contains, FCC ID: 2AYX4-PER200” . The grantee’s FCC ID can be used only when all FCC compliance requirements are met.

OEM Integrators – End Product Manual Provided to the End User: The OEM integrator shall not provide information to the end user regarding how to install or remove this RF module in end product user manual. The end user manual must include all required regulatory information and warnings as outlined in this document.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>