AMANTYA 5GMNN261 Verizon Auto-Certification Platform User Manual
- June 6, 2024
- AMANTYA
Table of Contents
AMANTYA 5GMNN261 Verizon Auto-Certification Platform
Product overview
Product appearance
Table 1-1 shows the interface description of mmWave small cell.
Interface name| number| Interface type| Interface
definition| remarks
---|---|---|---|---
MGT| 1| RJ45| 1 1000Base-T,RJ45|
SFP| 1| SFP| 10G Optical interface SFP+| optional interface
DC 12V| 1| DC socket| DC12V|
RGPS| 1| RJ45| GPS / BeiDou synchronous input interface|
table 1-2 mmWave small cell indicator
LED| System LED| Green: on, the system starts normally
Green: off, system not started
---|---|---
Alarm LED| Red: on, Motherboard control failure Red: off, Motherboard is
normal
LAN management port| 100 / 1000 adaptive, green and yellow LEDs
Green (link): on, light port works normally
Green (link): off, faulty or not working
Red (ACT): flashing, with data transmission
Red (ACT): off, no data transmission NOT support 10Mbps
Backhaul port| Green (link): on, light port works normally
Green (link): off, faulty or not working
Synchronous port| Green: on, GPS or IEEE1588 synchronization successful
Green: off, no synchronization or synchronization failure
technical specifications
Hardware specifications
project | describe |
---|---|
Installation mode | Indoor scene: ceiling and wall |
Power dissipation | <65W |
Power module | DC12V |
CPU Spec | NXP LX2160A |
Modem | 1FSM10055+1QTM10028 |
FLASH | 8GByte eMMC Nand |
DDR | 4GByte DDR4 for CPU |
LAN management port | 1 1000Base-T,RJ45 |
Debug port | 1 RS232 |
Backhaul port | 1 10G SFP+ |
Synchronous input interface | GPS / BeiDou synchronous input interface: |
RJ45
business specifications
project | description |
---|---|
performance |
- Support 1 radiation surface
- Carrier bandwidth: single carrier 100MHz,
- Backhaul: 10G Optical interface SFP+
Compatible design| Supports distributed base stations (option2, split in
RLC)
Synchronization mode|
- RGPS synchronization
- IEEE1588 V2 synchronization
- SyncE synchronization
Key technology|
- High speed signal, RF requirements for PCB design
- Large power consumption of the system, natural heat dissipation of the system
Band and bandwidth| Support standard 3GPP 5g-nr rel-15 Support
TDD Spectrum: 27500~28350Mhz, Bandwidth: single carrier 100MHz, 4*100MHz
follow-up support Antenna: 128 Rx /TX Rate: DL6.5Gps, UL3.2Gps
Tx Spec| All requirements in the agreement shall be met, and the requirements
for key index margin are as follows in full load operation, 64QAM
modulation, and ACLR and EVM meet the requirements:
EIRP≥37dBm。The worst beam: ID 123 AZ -45° EL-38° EIRP -38.2dBm
Rx Spec| All requirements in the agreement shall be met, and the requirements
for key index margin are as follows Throughput loss shall not exceed 5%,
uplink signal g-fr2-a1-3: – 95dbm
Environmental specifications
project | description |
---|---|
Storage temperature / humidity | The equipment shall be able to work or store |
normally within the following temperature and humidity range: Operating
temperature: – 5°C to +45°C
Storage temperature: – 40° C to + 70°C
Relative humidity: 5% ~ 95% (no condensation)
Heat dissipation mode| Natural convection heat dissipation
Noise| NA
Atmospheric pressure| 86 Kpa~106 Kpa
Protection level| IP30
Surge| Indoor products, no surge requirements
Configuration
Ip address configuration
The default configuration is static with IP address 192.168.1.10, and you can
change this IP following below operations. Logon on board with SSH or serial
tool user:root password:root Vi /etc/netpaln/01-netcfg.yaml Edit
01-netcfg.yaml and enter the static ip address. Eth0 is for SFP interface Eth1
is for Ethernet interface. Execute netplan apply’ and
sync’ command will
save this configuration.
Synchronization configuration
Freedom configuration is as below
When GNB connect to a GPS you can set GPS synchronization GPS configuration is
as below
Upgrading
Upgrading Preparation
Upgrading Scenario
5G mmWave Small Cell product is a low-power and low-cost 5G mmW gNB. In this
document, it’s briefed as 5GmmW gNB.
This document and corresponding MP1.7.2s package only apply to 5G mmW gNB
whose login prompt shows it’s MP1.6 MP1.7.2 as the followings:
…
TW 5GmmW Devel MP1.6 //MP1.6 Version login prompt localhost login:root
Password:root … =====================================================
…
TW 5GmmW Devel MP1.7.2 //MP1.7.2 Version login prompt localhost login:root
Password:root
…
Upgrading Procedure
Procedure: ① Preparation-> ② Upgrading uboot-> ③ Upgrading system
application and running validation tests.
Tools
These tools will be used while upgrading system: WinSCP、PC(above windows 7)、Tera Trem or Xshell 6.
5GmmW gNB Interface Configuration
The parameters of COM connecting 5GmmW gNB and PC should be configured as:
Baud rate:115200、Data:8bit、Parity:none、Stop:1bit、Flow control none、Transmit
delay:1msec/char 0 & msec/line,
The IP of GE/FE of PC should be configured as: 192.168.1.100.
The IP of GE/FE of 5GmmW gNB should be configured as: 192.168.1.1 (defaut
setting of the system)
Creating tftpd32 Serving in PC
Uppack the MP1.7.2s package in PC and run tfepd32.exe. The GUI of tftp server
will be shown as following:
Backup 5GmmW gNB Calibration files
Connect PC and 5GmmW gNB via GE, run WinSCP in PC, and backup calibration
files “mdm1m9kefs1″,”mdm1m9kefs2”,”tfcs_nv”locatedunder /home/tetra/bootdevice
/by-name in 5GmmW gNB to MP 1.7.2s softerware directory, directory in PC, for
example, F:ubootbootdeviceby-name.
Upgrading u-boot
Checking tftpserver
Make sure there is a file named “firmware_lx2160ardb_rev2_uboot_xspiboot.img”
under directory”Current Directory”.
Current Directory: uboot image file directory Server interface: tftpserverip.
Operaton on u-boot interface
Step 1.
As gNB is booting, when there is a prompt”Hit any key to stop autoboot: “press
anykey to enter u-boot command line.
Step 2.
Setting the ethernet interface, local IP of the borad, and tftpserverIP.
=>setenv ethact DPMAC17@rgmii-id # set an available Ethernet interface.
=>setenv ipaddr 192.168.1.10 # set local IP of the board.
=>setenv serverip 192.168.1.100 # set server IP
=>saveenv # saveenv the variables
Step 3.
Test if the tftp server can connect to the board.
=>ping $serverip
The text in the red box means the the connection is successfully setup.
The text in the red Box in the following figure means the tftp server does not work. Please check the network or configuration.
Step 4.
Probe flash.
=>sf probe 0:0
SF: Detected mt35xu512g with page size 256 Bytes, erase size 128 KiB, total 64
MiB
or
SF: Detected mt25u51245g with page size 256 Bytes, erase size 64 KiB, total 64
MiB
=>
or
Step 5.
Download u-boot image. Please note the name of the image file should not be
changed. =>tftp 0xa0000000firmware_lx2160ardb_rev2_uboot_xspiboot.img
If it succeed, the prompt will show the following information:
Step 6.
Erase all contents in flash. Please note this step cannot be rolled back, so
please make sure your commands are exactly the same as the following example.
Please make sure the power is kept on and do not press enter key repeatedly
(otherwise, the u-boot will run the command repeatedly). The time of executing
the whole step is estimated about 1 min.
=>sf erase 0 +$filesize
Step 7.
Writing the downloaded u-boot image to the flash. Please note this step cannot
be rolled back, so please make sure your commands are exactly the same as the
following example. Please make sure the power is kept on and do not press
enter key repeatedly (otherwise, the u-boot will run the command repeatedly).
The time of executing the whole step is estimated about 1 min.
=>sf write 0xa0000000 0x0 $filesize
Step 8.
Power off 5GmmW gNB and then turn on it. Please note the “no link” warning in
the following picture is a normal log.
Enter the u-boot command, and put the following command to set the MAC
address, making sure the MAC address is unique in a subnet:
:
=>setenv ethaddr 00:04:9F:06:10:71
=>setenv eth1addr 00:04:9F:06:10:70
=>saveenv
Power off the gNB and restart it. Make sure the mac address is correct in
Linux, otherwise, repeat step 8.
root@localhost:~#ifconfig a
Upgrad system application and run validation tests
TinyLinuxlogin
Restart gNB, and input the following command under u-boot command line.
=>setenv boot_targets “usb0 mmc0 scsi0”
=>setenv bootcmd_mmc0 “devnum=0; run mmc_boot”
=>boot
Input user name: root
NXP LSDK tiny 2004 (based on Yocto)
TinyLinux login:root
Run upgrading script
root@TinyLinux:~#/bin/twupdate
After about 8 min, if it’s shown “Installation completed successfully”, the
upgrading is successful.
Restart 5GmmW gNB
root@TinyLinux:~#reboot
When the command prompt is shown,input user name/password as root/root
…
TW 5GmmW Devel MP1.7.2s
localhost login:root
Password:root
Last login: Sun Jan 28 15:58:20 UTC 2018 on tty7
Welcome to TW 5GmmW Devel MP1.7.2s (GNU/Linux 4.19.90-rt35-dirty aarch64)
…
Import 5GmmW gNBcalibrations files
Download the calibration files “mdm1m9kefs1”, “mdm1m9kefs2” and“tfcs_nv” which
are formerly backuped from PC to the gNB, under the directory
“/home/tetra/bootdevice/by-name”
Check the calibration files status
[Precautions]
After importing the calibration file, in order to avoid the error caused by
the
synchronization failure between the wcp tool and the operating system file,
you need to double-click the 【 】iconbutton on the right window of the wcp
tool. The specific operation is shown in the above figure. At the same time,
check and confirm the import of calibration files on 5gmmw GNB, and execute
the sync command. The specific operation is shown in the figure below.
root@localhost:~#ls /home/tetra/bootdevice/by-name/ -pla root@localhost:~#
sync
Restart 5GmmW gNB
root@localhost:~#reboot
When the command prompt is showninput user name/password as root/root
TW 5GmmW Devel MP1.7.2s
localhost login:root
Password:root
…
Welcome to TW 5GmmW Devel MP1.7.2s (GNU/Linux 4.19.90-rt35-dirty aarch64)
…
The green light near the center of the board (led 6) keeping green means the
FSM10055 is running normally.
root@localhost:~# ps -ef | grep syncMgr //The fsmver check and mac-e test can
be performed only after syncmgr process appears
Validation
root@localhost:~#fsmver
When the version information is the same as the figure above, the upgrading
is successfully completed.
FCC Regulations
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.
This device has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference in a
residential installation. This equipment generates, uses and can radiated
radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a particular
installation If this equipment does cause harmful interference to radio or
television reception, which can be determined by turning the equipment off and
on, the user is encouraged to try to correct the interference by one or more
of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
Caution: Changes or modifications not expressly approved by the party responsible for compliance could void the user`s authority to operate the equipment.
RF Exposure Information
This device meets the government’s requirements for exposure to radio waves. This device is designed and manufactured not to exceed the emission limits for exposure to radio frequency (RF) energy set by the Federal Communications Commission of the U.S. Government.
This device complies with FCC radiation exposure limits set forth for an uncontrolled environment. In order to avoid the possibility of exceeding the FCC radio frequency exposure limits, human proximity to the antenna shall not be less than 87cm (34 inches) during normal operation.
Amantya Technologies, inc
2803, Philadelphia Pike, Suite B 304,Claymont, DE 19703, United States
Anuradha Gupta
anuradha@amantyatech.com
This mmWave small cell, model no: 5GTP202MMN261 requires training professionals qualified by Service Provider to configure and install the product. This device complies with FCC rules and regulations for fixed-mounted on indoor permanent structure in commercial/business premises excluding private resident/property. This device is distributed through controlled distribution channel and requires that trained professionals to install this product, and this device will not be sold directly to the general public through retail stores.
This mmWave small cell, model no: 5GTP202MMN261 must be installed to provide at least 87cm separation distance from bystanders to comply with the General Population / Uncontrolled MPE limit and requirements. RF exposure compliance may need to be addressed at the time of licensing, as required by the responsible FCC bureau(s) including mitigation actions for fixed RF sources to the extent necessary to ensure compliance with FCC exposure limits per section §1.1307(b)(4).
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>