Intel Model 7260M2NA and 7262M2WW User Guide Revision 1.
Revision History Revision History Revision Number Description Revision Date 1.0 Initial version of the document 17‐Dec‐2012 1.1 Revise to add model 7260M2NA Nov 2014 1,2 Revise to add model 7262M2WW Feb 2015 Rev. 1.
Revision History Contents 1 Introduction ................................................................................ 9 2 Software Framework ............................................................. 12 2.1 Driver Installation................................................................... 12 2.1.1 General Considerations ........................................................ 12 2.1.2 Intel High Speed Modem Driver (ecm200) .................. 14 2.1.2.1 Client offset configuration. ...
Revision History 2.3.1 Setup and Configuration ...................................................... 33 2.3.1.1 Entering AT Commands ....................................................... 33 2.3.1.2 Board Configuration and required AT Commands ..... 34 2.3.2 Connecting the UE.................................................................. 35 2.4 AT Commands Examples ..................................................... 37 3 Test Cases .............................................................
Revision History Appendix A ................................................... Definitions/Explanations ....................................................................................................... 53 Figures Figure 1. Location of the Prolific serial to USB driver, the Flash USB driver and the FTDI diver within the flash tool folder. ................................................................. 13 Figure 2. Use the already installed driver. ................... 15 Figure 3.
Revision History Figure 6. On Win7: Select “Start:Control Panel:Network and Sharing Center” followed by “Change adapter settings”. ............................................ 18 Figure 7. Open the properties dialog of the new network device (right click)........................................... 18 Figure 8. Select the configuration dialog. ..................... 19 Figure 9. Set the client offset to 1 and press “OK”. . 20 Figure 10. Press “OK” to save these settings. Otherwise these settings get lost. ..
Revision History Figure 14. Congratulations. Your ecm200 driver and its IP connection are now properly configured. ..... 25 Figure 15. Use the already installed driver. ................. 26 Figure 16. Install the driver. .............................................. 27 Figure 17. Comneon suspend and six COM ports are now appearing at the device manager. .................... 28 Figure 18. USIF1 Device Manager Prolific USB-toSerial COM Port ..................................................................
Revision History Table 3. Terminal Port Settings ........................................ 38 Table 4. AT Commands to check ARM software version ................................................................................... 38 Table 5. AT Commands to Register on the Network 38 Table 6. AT Commands for an Incoming Call .............. 38 Table 7. AT Commands for an Outgoing Call .............. 39 Table 8. AT Commands for SMS Management............ 39 Rev. 1.
Revision History 1 Introduction This document provides a brief description of the NGFF Carrier Board development kit. Including: - Hardware interfaces with FIH board - NGFF Carrier Board User Guide V2.0 Rev. 1.
Revision History Rev. 1.
Revision History Rev. 1.
Revision History 2 Software Framework 2.1 Driver Installation 2.1.1 General Considerations The two different test and debug configurations always require a Win PC where up to five different drivers must be installed accurately. This are: 1. the Intel High Speed Modem Driver (ecm200), 2. the Comneon High Speed Modem Driver, 3. the Prolific serial to USB driver (part of the flash tool folder), 4. the Flash USB driver (part of the flash tool folder) and 5. the FTDI diver. Rev. 1.
Revision History Figure 1. Location of the Prolific serial to USB driver, the Flash USB driver and the FTDI diver within the flash tool folder. Pls note that Win does not always complain if the drivers 4 to 5 are not installed. If one of these drivers is missing flashing problems are occurring. The ARM software and LTE firmware releases are linked to individual driver revision numbers that were used for release testing.
Revision History M:\Software\XMM7060_tools at IMC DRS Flash Tool : \\musdsara001.imu.imc.local\SW_builds\xmm6360\tools\flashtool Socmondll : \\musdsara001.imu.imc.local\SW_builds\xmm7060\Release\Tools\Socmondll\socmondll_100.150.001.dll 2.1.2 Intel High Speed Modem Driver (ecm200) Take the recommended driver, see Subsec. 2.1.1, (folder e.g. WMC_ecm200_3.61.0) and follow the instructions from the installation wizard. Enable the IP forwarding: run the sriptenable_ip_forwarding.reg from: \\musdsara001
Revision History Win XP asks now it’s typical questions and gets the common answers see below. Win 7 does not ask and loads the driver automatically. Figure 2. Use the already installed driver. Rev. 1.
Revision History Figure 3. Install the driver again. Figure 4. The network modem and four COM ports are now appearing at the device manager. Rev. 1.
Revision History Now open the network manager and configure the network settings of the modem. Figure 5. Open the network connections dialog. Win XP : Start:Settings:NetworkConnectios. A new network device did pop up. It is not yet connected. Rev. 1.
Revision History Figure 6. On Win7: Select “Start:Control Panel:Network and Sharing Center” followed by “Change adapter settings”. Figure 7. Open the properties dialog of the new network device (right click). Rev. 1.
Revision History 2.1.2.1 Client offset configuration. This must be done before the IP settings. If the order is flipped the IP settings get lost. Figure 8. Select the configuration dialog. Rev. 1.
Revision History Figure 9. Set the client offset to 1 and press “OK”. Figure 10. Press “OK” to save these settings. Otherwise these settings get lost. Rev. 1.
Revision History 2.1.2.2 Static IP Address Configuration The given example IP number at Figure 12 is for a simplified test and debug setup, see Error! Reference source not found., where the octave or java client runs on the Win PC that also carries all necessary Win drivers and is connected to the DUT. The ecm200 driver runs in a subnet that is only visible from this PC. The complete setup, see Error! Reference source not found.
Revision History the desktop PC. The example below helps to find proper static route settings: test PC with static IP: 10.1.0.126 ecm200 client at test PC with IP: 172.16.126.1 (client offset set to 1) run as root at the PC where the Octave is running on. route print #read out route settings route add 172.16.126.0 mask 255.255.255.0 10.1.0.126 test the configuration: ping 172.16.126.1 #response from the ecm200 driver ping 172.16.126.
Revision History Figure 11. Open the Internet Protocol TCP/IP settings. Rev. 1.
Revision History Figure 12. Set the static Network IP and press OK. Rev. 1.
Revision History Figure 13. To close the properties dialog and save the settings press “OK”. Figure 14. Congratulations. Your ecm200 driver and its IP connection are now properly configured. If desired it is now also possible to rename the network device from “Wireless Connection2” to something more convenient e.g. ecm200 + IP address. 2.1.3 Comneon High Speed Modem Driver Take the recommended driver, \\musdsara001.imu.imc.local\SW_builds\x mm6360\tools\usb_drivers See also SMS02534274: ‐ Please u
Revision History version and not WMC_comneon2_3.55.0, see Subsec. 2.1.1, (folder Comneon_High_Speed_Modem_Driver) and follow the instructions from the installation wizard. Now connect the cable to the USB-HS connector. Win XP asks now it’s typical questions again and gets the common answers, see below. Win 7 does not ask and loads the driver automatically. Figure 15. Use the already installed driver. Rev. 1.
Revision History Figure 16. Install the driver. Rev. 1.
Revision History Figure 17. Comneon suspend and six COM ports are now appearing at the device manager. Congratulations, your driver installation has finished successfully. 2.1.4 Flash USB driver and FTDI Driver These drivers are mandatory to flash new ARM software and LTE firmware images at the modem board. Take the recommended Rev. 1.
Revision History drivers, see Subsec. 2.1.1, (flash tool subfolder) and follow the instructions from the installation wizards. Note: If this drivers are not installed correctly instabilities at the flash process are occurring without substantial error information from Win XP or Win 7. 2.1.5 Prolific Serial to USB Driver The Prolific driver is mandatory to access all modem board UART (USIF) ports. Take the recommended driver, see Subsec. 2.1.
Revision History Figure 18. USIF1 Device Manager Prolific USB‐to‐Serial COM Port 2.2 LTE debug UART configuration After the preliminary setting, run any AT terminal application (e.g. HyperTerminal) on your PC’s communication port, with the following settings. Rev. 1.
Revision History Table 1. Terminal Port Settings 115200 bps Data rate 8 Data Bits N Parity 1 Stop Bits HW Flow Control on UNIX xterm use this with uucp: %docing station serial port, uucp chown uucp /dev/ttyUSB0 cu -l /dev/ttyUSB0 -s 115200 If putty http://www.putty.org is used this looks like this: Rev. 1.
Revision History Figure 19. Putty configuration. Rev. 1.
Revision History 2.3 System Trace Box 2.3.1 Setup and Configuration 2.3.1.1 Entering AT Commands The AT commands mentioned below must be sent to the COM port that corresponds to the Intel Mobile (USB3) COM port in case the ecm 200 driver is used or to the COM port that corresponds to the Comneon High Speed Modem, see Error! Reference source not found.. The COM port that corresponds to the USIF‐1 USB port, see Error! Reference source not found. may also work.
Revision History 2.3.1.2 Board Configuration and required AT Commands Reset the board in a way that is booting from the flash Enable tracing using: at+xsystrace=0,"lte_l1_sw=4" Reset the board again in a way that is booting from the flash Now the initialization at commands to switch to Service Mode (that is the mode to use RCTTH) can be sent if needed: ARM for Inc2.8: ‘at@ecal:’ ’at@ecal_init():’ ARM for Inc3.
Revision History b. Route traces through UE's "OCT‐Block", which creates the ISTP format: at+xsio=3; c. Select the traces from specific sources, use at+xystrace command. For example, to configure the traces from specific to select ONLY the 3g_sw traces: at+xsystrace=0,"3g_sw=1",,"oct=4" d. make sure your SIM is not waiting for entering a PIN: at+cpin? If it is, send the PIN at at+cpin= e.
Revision History 7. Find the com‐port in which UE is connected using comtest tool. Run the command comtest –l. It will list the ports. Carefully evaluate the port for tracing and port for control. 8. To check whether PC is connected to UE properly, try connecting the control port with the terminal emulator and send “AT” command, If the response is OK, UE is connected successfully. This can be done via AT Console in SystemTraceTool. 9. Send the below AT commands: a.
Revision History the traces from specific to select ONLY the 3g_sw traces: at+xsystrace=0,"3g_sw=1",,"oct=4" d. make sure your SIM is not waiting for entering a PIN: at+cpin? If it is, send the PIN at at+cpin= e. make sure, the 3G protocol stack is sending traces: at+cops=0; (this command triggers the phone to (re‐)register to the network) 2.4 AT Commands Examples After the preliminary setting, run any AT terminal application (e.g.
Revision History Table 3. Terminal Port Settings Data rate Data Bits Parity Stop Bits Flow Control 115200 bps 8 N 1 HW AT Command to check ARM Software version Table 4. AT Commands to check ARM software version Command sent by DTE Response of DCE Description at+xgendata The device will reply with the running ARM software version Register on the network (GSM/UMTS) Table 5.
Revision History Outgoing Voice Call Table 7. AT Commands for an Outgoing Call Command sent by DTE DCE Response Description AT OK AT+CLIP=1 Activation of Caller line ID presentation OK ATD+862161019000; Outgoing voice call OK Voice call is accept from network ATH Hang up OK SMS Management Table 8. AT Commands for SMS Management Command sent by DTE DCE Response AT+CMGF=1 OK Description Set the text mode as the format that will be used.
Revision History Rev. 1.
Revision History Rev. 1.
Revision History 3 Test Cases 3.1 Protocol Test (CMW500) Figure 20. CMW 500 In general it needs to be checked that CMW500 setup are identically to the reference. The components to be checked are : The test scenario configurations (xml files) and The firmware versions for the tester hardware itself. 3.1.1 CWM 500 Firmware The firmware version can be checked and maintained in the R&S Version Manager.
Revision History CMW500 Protocol Testing" quick start guide (1202.3857.62). The R&S Version Manager help provides more details on R&S Version Manager functions and handling of software units. This document assumes that all required software units can be installed by the user. The R&S Version Manager can be opened via the START menu: Once opened there are two ways to verify similarity of firmware versions: by hand via stepping through the license options or by exporting the firmware (software status).
Revision History The next picture shows the menu from which the status export can be called: After this a pop‐up window appears with three possible choices. Only the top one has to be selected as shown in the picture: After this the location of the status export file needs to be chosen. Once done the file can be compared to the reference file which is located under: ..\version\lab2\lab2_cfg.html 3.1.
Revision History The directory “msg” is part of the CDK delivery and contains several xml files. It has to be noted that the xml version of the xml files needs to be compliant to the installed tester firmware. Otherwise strange errors occur during test case execution! http://www2.rohdeschwarz.com/en/products/test_and_measurement/m obile_radio/CMW500-|-Demo-|-48-|-5420.html 3.1.3 AT Commands Network attach in CallBox Mode, LTE band 7. at+xact=6,2,1,107 at+cgdcont=1,"IP",”www.rohde-schwarz.
Revision History The Data Application Unit (DAU) package has to be installed on the CMW. In case the DAU hardware is populated, the software (SW) should already be installed as well. Check this in "SetupSW/HW‐ EquipmentInstalled software". Before installation: Terminate the CMW BaseSW application – close the window with ‘X’ In the task manager kill the process "ComponentEnvironmentServer_2.5.exe". Installation: Install the DAU‐SW package "SetupCMW_DAU_Support (Release)‐V1.0.15.
Revision History Activate DHCP in Data Application Control After complete startup of the CMW BaseSW application, follow the steps below to configure the DAU for DHCP: Make sure your Router is connected to the "LAN DAU" ETH port at the back side of the CMW. Open the SETUP menu on the right side. Open the DAU configuration via menu: Data Appl.
Revision History Switching UPC from PPC (SUW) to DAU In order to let the scenario use the UPC (=Uplane Control) on the DAU (and not as per default on the PPC), two XML files have to be replaced in the topology: sequencer.xml, pipe.xml Copy these two files to C:\Rohde‐ Schwarz\Scenarios\16.6\APPL\MLAPI\rstopology\LTE\. NOTE: It is recommended to make a back‐up of the original files before. Start the LTE scenario Start the LTE scenario now.
Revision History Manual DNS settings On the LTE host which connects to the internet, the DNS server has to be configured manually, because the DAU does not yet support automatic DNS provisioning (ask your IT). In case of a LTE notebook adapter, the DNS server will be configured on the IP properties pane: Rev. 1.
Revision History 4 Regulatory Notice Japanese Radio Law and Japanese Telecommunications Business Law Compliance. This device is granted pursuant to the Japanese Radio Law (電波法) and the Japanese Telecommunications Business Law (電気通信事業法) This device should not be modified (otherwise the granted designation number will become invalid) Manual Information to the End User : The OEM integrator has to be aware the end user manual shall include all required regulatory information/warning as show in this manual.
Revision History 5 Abbreviations / Terminology A A‐GPS Assisted‐GPS (Global Positioning System) AP Application Processor B BB Baseband C CMOS Complementary Metal Oxide Semiconductor CN Comneon D DigRF v4 Digital RF interface v4 (rmainly used for 4G) DigRF 3.
Revision History L LDO Low dropout (regulator) LED Light‐emitting diode M MIPI Mobile Industry Processor Interface MMC(I) Multimedia Card (Interface) MPU Microprocessor unit O P PA Power Amplifier PCL Port Control Logic PMU Power Management unit PTI Parallel Trace Interface S SD‐Card Secure Digital Card SMT pin header Surface Mount Technology pin header SPI Serial Peripheral interface S4G SMARTi™ 4G ST MIPI System Trace MIPI STT System Trace Tool SVB System verification
Revision History Appendix A Definitions/Explanations Eval Board special processor socket board for X‐GOLD™ 716 component verification Lauterbach Supplier of Debug and Trace environment for X‐GOLD™ 716 (e.g. JTAG, ETM7/11, ST MIPI) Modem board Main part of XMM™ 7160 platform hardware (see Error! Reference source not found.) XMM™ 7160 Project name of Intel platform with key component X‐GOLD™ 716 RF‐ Engine RF part of platform (RF‐transceiver, Power amplifiers, LNA, Filter bank, antenna switch etc.
Revision History Appendix B Regulatory Statements USA FCC Radio Frequency Exposure The FCC with its action in ET Docket 96-8 has adopted a safety standard for human exposure to radio frequency (RF) electromagnetic energy emitted by FCC certified equipment. The wireless adapter meets the Human Exposure limits found in OET Bulletin 65, supplement C, 2001, and ANSI/IEEE C95.1, 1992.
Revision History Use On Aircraft Caution Caution: Regulations of commercial airline operators and the FCC may prohibit airborne operation of certain electronic devices equipped with radio-frequency wireless devices (wireless adapters) including cellular devices because their signals could interfere with critical aircraft instruments. The Wireless Adapter and Your Health The wireless adapter, like other radio devices, emits radio frequency electromagnetic energy.
Revision History REGULATORY INFORMATION USA ‐ Federal Communications Commission (FCC) No configuration controls are provided for Intel® wireless adapters allowing any change in the frequency of operations outside the FCC grant of authorization for U.S. operation. Intel® wireless adapters are intended for OEM integrators only. If Intel® wireless adapters are to be co-located with any other transmitter additional testing and/or approval by the FCC will be required.
Revision History Consult the dealer or an experienced radio/TV technician for help. NOTE: The adapter must be installed and used in strict accordance with the manufacturer's instructions as described in the user documentation that comes with the product. Any other installation or use will violate FCC Part 15 regulations. Canada – Industry Canada (IC) This device complies with Industry Canada licence-exempt RSS standard(s).
Revision History isotrope rayonnée équivalente(P.I.R.E.) ne soit pas supérieure à celle qui est nécessaire pour une communication réussie. Safety Approval Considerations This device has been safety approved as a component and is for use only in complete equipment where the acceptability of the combination is determined by the appropriate safety agencies.
Revision History Changes or modification to Intel® wireless adapters by OEMs, integrators or other third parties is not permitted. Any changes or modification to Intel® wireless adapters by OEMs, integrators or other third parties will void authorization to operate the adapter. Simultaneous Transmission of Intel® Wireless Adapters with Other Integrated or Plug‐In Transmitters Based upon FCC Knowledge Database publication number 616217 https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.
Revision History cables and equipment other than that specified by Intel Corporation. The correction of interference caused by such unauthorized modification, substitution or attachment is the responsibility of the user. Intel Corporation and authorized resellers or distributors are not liable for any damage or violation of government regulations that may arise from the user failing to comply with these guidelines. Rev. 1.
