Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Edge Gateway5000 Series Installation and Operation Manual

PDF

Wind River Linux Basic Functions

Preinstalled Packages

Run the root@WR-IDP-xxxx:~# rpm -qa command to list all the packages installed on the Wind River Linux OS.

  • NOTE: If you are looking for a specific package, you have to pipe the output of the root@WR-IDP-xxxx:~# rpm -qa command to search for that specific package.

Expected result: Device: xxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxx

UEFI Capsule update capability

Run the fwupgmgr tool/commands are used to update UEFI BIOS firmware on the system. The UEFI BIOS for this system is released through online Linux Vendor File System based methods.

Operation command: root@WR-IDP-xxxx:~# fwupdmgr get-devices

Expected result: (Device found) Device: xxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxx

Watchdog Timer

Running the root@WR-IDP-xxxx:~# systemctl status watchdog command displays the status of Watchdog timer service.

Expected result: Example of the output is shown below.

Image: Watchdog Timer

TPM support (HW TPM module dependency)

Run the root@WR-IDP-xxxx:~# tpm_statistic command displays the status of TPM service.

If the TPM is functional and enabled in the BIOS, below would be the expected results, when tpm_statistic command is executed.

Expected result: The expected result is for TPM Chip Presence: Normal. Example of the response to the above command should be similar to the output shown below.

Image: TPM Statistics

System reboot

To reboot the system, as a root user logged in to the system, enter the root@WR-IDP-xxxx:~# reboot reboot at the command prompt.

Expected result: System reboots back to the login prompt successfully.

System PowerOff

Run the root@WR-IDP-xxxx:~# shutdown now command to shuts down the system.

Expected result: System shuts down successfully.

Network Interface

To determine the default supported network interface, type the root@WR-IDP-xxxx:~# ifconfig at the command prompt.
Expected result: The following are the default network interfaces supported out of the box.
  • br-lan
  • eth0
  • eth1
  • lo
  • wlan0

Network configuration and default setup

The following commands can be used to configure different network interfaces on the system with Wind River Linux on it.

Network configuration on Wind River Linux IDP 3.1 environment can be performed through the LuCi web interface.
  • NOTE: The LuCi web interface supported in the default OS image.

The user can reach the LuCi web interface on the system using the https:// < IP-Address-of-eth0-interface-of-the-gateway > following URL from a different system with a web browser and the system should be on the same network or connected to the system’s network through proxy.

The default login credentials to the LuCi web interface are root/root. The IP address of the eth0 network port can be identified by performing the ifconfigcommand on the Linux terminal.

Image: LuCi web interface

Network interface configuration

The Edge Gateway contains the following default network configurations:
  • br-lan — Bridged LAN Interface
  • eth0 — Wired LAN interface 0
  • eth1 — Wired LAN Interface 1
  • lo — Loop back interface
  • wlan0 — Wireless LAN (or Wi-Fi) interface mode

eth0 — Wired LAN Interface. By default eth0 interface is configured to be DHCP client interface. When this ethernet port is connected to a DHCP server, this interface obtains an IP address from the DHCP server.

Run the root@WR-IDP-xxxx:~# ifconfig eth0 command to identify the IP address. The network IP interface information is available under inet addr: x.x.x.x where x.x.x.x is the IP address of the system.

eth1 — Wired LAN interface. The default configuration for the second wired ethernet interface eth1 serves as DHCP server and provides IP addresses to any device requesting IP address from the system. The devices requesting DHCP addresses get IP addresses in the range of 192.168.1.x subnet. The default DHCP server is at 192.168.1.1 address. For reconfiguring this network interface by logging in to the LuCi web interface.

Wlan0 — Wireless LAN or Wi-Fi interface. The default configuration for the WLAN0 interface on the system with Wind River Linux is in access point (AP) mode. The mode can be changed to client mode through LuCi web interface.

Br-lan — The bridged LAN interface. By default, the bridge interface is configured to bridge ethernet eth1 and the WLAN0 interface, so any devices that would like to connect to the system in WiFi mode or through eth1 wired mode can obtain IP addresses through the system. The issued IP addresses by the access point and eth1 interface are in the 192.168.1.x subnet. The default access point SSID for the access point is IDPDK-5591. The bridge configuration can be modified using LuCi web interface. Follow Intel/Wind River’s documentation for more details on configuring, WAN, WLAN, and br-LAN network interfaces using LuCi web interface.

Bluetooth configuration

The system supports an integrated Bluetooth network interface. The Bluetooth network can be configured using LuCI web interface on the Wind River Linux OS. To configure Bluetooth interface on the system with Wind River Linux OS.
  1. Log in to the LuCI web interface as identified in the steps referenced in the previous sections.
  2. Bluetooth configuration is supported under Network tab drop-down menu Bluetooth of the Web Interface.

    Image: Bluetooth configuration

  • Enable Bluetooth interface in this page and hit Scan to identify nearby other Bluetooth enabled devices.

Wireless WAN network interface configuration

Add-on modules can be installed on the edge gateway system to get Wireless WAN (WWAN) connectivity.
  • 4G-LTE — Interface using Telit LE910 module for carrier AT&T
  • 4G-LTE — Interface using Telit LE910 module for carrier Verizon
  • HSPA+ — Interface using Telit HE910 module

LE910 WWAN connection configuration

Follow the Service Manual to install the LE910 module and the corresponding carrier SIM card in the system. After the module and SIM card is installed, activate the WWAN connectivity by:
  • NOTE: The default Wind River Linux OS image currently uses AT commands to configure WWAN interface and LTE connectivity.
  • NOTE: LuCi web interface currently does not support configuring the WWAN interface.

Identifying installed WWAN module and Carrier

To identify the serial interface on the installed LE910 module’s tty ACM interface, using dmesg command: # dmesg | grep –i ttyacm

The system may contain more than one USB ACM device other than Telit LE910 or Telit HE910 module. Based on the output for the dmesg command, identify the ttyacm ports that were enumerated, for example, below is the output for dmesg | grep –i ttypacm command for more than one USB ACM device on the system.
Image: Identifying installed WWAN module and Carrier
Launch minicom terminal utility on the system with one of the USB ACM device port to identify that we have the correct USB ACM device for Telit LE910 device before configuring the device, e.g. below shows how to launch minicom with ttyACM1 as interface:
  • # minicom –D /dev/ttyACM1
  • Inside minicom, type the following AT command to identify if it is the “Telit” device AT+GMI
  • If the response to the above command is Telit, then you have identified the correct device ttyacm port.
  • If the output is not Telit or Error, then you have to exit out of minicom and start minicom with a different port like e.g. /dev/ttyACM0 or /dev/ttyACM3 etc,
  • Example of starting minicom with /dev/ttyACM1 as port of communication below.

    root@WR-IDP-0A1D:~# root@WR-IDP-0A1D:~# minicom -D /dev/ttyACM1

Configuring the WWAN carrier parameters

Inside minicom terminal, the following AT commands have to be issued in sequence to configure the LTE module, the line with DESCRIPTION are references to the AT commands to type and are not to be entered as a part of the AT commands themselves

DESCRIPTION: Check that the SIM is inserted and PIN is unlocked using the at+cpin? command

DESCRIPTION: If the SIM is locked with a PIN the at+cpin=”1234” AT command can be used to unlock the SIM. Where the SIM PIN is 1234, if the PIN is different, use appropriate PIN number in the command below.

DESCRIPTION : Setting up the APN. NCM can be activated using every available CID,
  • NOTE: Skip this step for Verizon as it is preprogrammed (use AT+CGDCONT? to identify if the CID3 is vzwinternet).

The at+cgdcont=3,"IP","broadband" command has to be issued for AT&T based SIM. In the command, 3 is the CID(Connection ID), this can be between 1 to 5, 3 is shown to keep the value consistent between VZ and ATT based solution. IP in the command indicates the TCP-IP protocol. broadband in the command is the name assigned by AT&T as a network ID or APN to connect to logically, this name is assigned by the carrier.

DESCRIPTION : Check the state of the modem
at+cops?
                                    at+cgatt?
                                 

DESCRIPTION: Run the at#ncm=1,3 command to enable NCM on CID 3 (this command must be sent on a USB instance (in this case USB0 or USB3)

DESCRIPTION: Run the at#ncm=1,3 to activete the PDP context.

DESCRIPTION: Read IP address, Gateway address and DNS address from the module
at+cgcontrdp=3
                                    REPONSE:
                                    +CGCONTRDP:
                                    3,6,"vzwinternet.mnc480.mcc311.gprs","100.176.244.64.255.255.255.0","100.176.244.65","10.133.17.210","0.0.0.0","0.0.0.0","0.0.0.0"
                                    OK
                                 

Establishing LTE WWAN connectivity

Description: The following are a capture from a sample session that was performed on a Dell Edge Gateway platform with default Wind River Linux OS image to establish LTE connectivity using Verizon LE910 module and Verizon SIM card. The commands highlighted were typed and the other is response from the system. For AT&T LE910 module and AT&T SIM environment use “ broadband” to replace “ vzwinternet” in the following set of commands.

In order to open up additional Linux terminal in Wind River Linux, press Alt-F2 key, this will take you to another Linux login prompt. Login using your root/root credentials.

Command typing is highlighted in Itlaics

root@WR-IntelligentDevice:
                                 ~# minicom -D /dev/ttyACM0
                                 Welcome to minicom 2.7
                                 OPTIONS: I18n
                                 Compiled on  16:20:45.
                                 Port /dev/ttyACM0, 21:33:05
                                 Press CTRL-A Z for help on special keys
                                 
                                 at+cgdcont=3,"IPV4V6","vzwinternet"
                                 OK
                                 
                                 at+cgdcont?
                                 +CGDCONT: 1,"IPV4V6","vzwims","",0,0
                                 +CGDCONT: 2,"IPV4V6","vzwadmin","",0,0
                                 +CGDCONT: 3,"IPV4V6","vzwinternet","",0,0
                                 
                                 OK
                                 
                                 at#ncm=1,3
                                 OK
                                 
                                 at+cgact=1,3
                                 OK
                                 at+cgcontrdp=3
                                 +CGCONTRDP: 3,7,"vzwinternet.mnc480.mcc311.gprs","100.106.47.7.255.0.0.0","100.1
                                 06.47.8","198.224.157.135","0.0.0.0","0.0.0.0","0.0.0.0"
                                 +CGCONTRDP: 3,7,"vzwinternet.mnc480.mcc311.gprs","254.128.0.0.0.0.0.0.0.0.0.71.4
                                 6.110.1.1.255.255.255.255.255.255.255.255.0.0.0.0.0.0.0.0","0.0.0.0.0.0.0.0.0.0.
                                 0.0.0.0.0.0","198.224.157.135","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0","0.0.0.0.0.0.0.
                                 0.0.0.0.0.0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
                                 
                                 OK
                                 
                                 ^A X Y
                                 
                                 root@WR-IntelligentDevice:~# 
                                 ifconfig wwan0 100.106.47.7 netmask 255.0.0.0 up
                                 root@WR-IntelligentDevice:~# 
                                 route add default gw 100.106.47.8 wwan0
                                 root@WR-IntelligentDevice:~# 
                                 echo nameserver 198.224.157.135 >>/etc/resolv.conf
                                 root@WR-IntelligentDevice:~# 
                                 minicom -D /dev/ttyACM0
                                 Welcome to minicom 2.7
                                 OPTIONS: I18n
                                 Compiled on Dec 17 2015, 16:20:45.
                                 Port /dev/ttyACM0, 21:33:05
                                 Press CTRL-A Z for help on special keys
                                 
                                 at+cgdata="M-RAW_IP",3
                                 CONNECT
                                 OK
                                 ^
                                 A X Y
                                 root@WR-IntelligentDevice:~# 
                                 ping 8.8.8.8
                                 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
                                 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=36.9 ms
                                 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=33.5 ms
                                 64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=31.2 ms
                                 64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=32.6 ms
                                 
                                 ^C
                                 --- 8.8.8.8 ping statistics ---
                                 5 packets transmitted, 4 received, 20% packet loss, time 4004ms
                                 rtt min/avg/max/mdev = 31.276/33.585/36.903/2.078 ms 
                              

Disable WWAN0 Connection

Description: The following method can be used to disable or delete the WWAN connection that was setup using the descriptions mentioned in the previous sections.
  1. Launch minicom as defined in the other sections and choose the appropriate ttyACM port for the Telit module
  2. Inside the minicom terminal send the following AT commands
    At+gmi   (to make sure it is the Telit module)
                                              At+cgatt=0 (Response should be NO CARRIER)
                                              AT+cgatt=1 
                                           
  3. Exit out of the minicom terminal by pressing Ctrl-A, Z and X.
  4. On the Linux prompt enter the # ifconfig wwan0 down command to disable wwan0.
Sample Session to disable WWAN0 Connection:
root@WR-IntelligentDevice:~# 
                                    minicom -D /dev/ttyACM0
                                    Welcome to minicom 2.7
                                    OPTIONS: I18n
                                    Compiled on Dec 17 2015, 16:20:45.
                                    Port /dev/ttyACM0, 21:33:05
                                    Press CTRL-A Z for help on special keys
                                    at+cgact=0,3
                                    OK
                                    
                                    ^A X Y
                                    root@WR-IntelligentDevice:~# 
                                    ifconfig wwan0 down

HE910 (HSPA+) WWAN connection configuration

Description: Follow the hardware installation guide to install the HE910 module and the corresponding carrier SIM card in the system. Once the hardware module and the SIM are installed follow the instructions below to activate 3G HSPA+ connectivity.

The HSPA connection on Wind River Linux can be activated using the following UCI command set or through LuCi web interface. Below are samples steps to configure 3G WWAN interface:
  1. Checking the network configuration.
    root@WR-IDP-XXXX:~# cat /etc/config/network
                                              ...
                                              
                                              config interface 'wwan'
                                              option ifname '3g-wwan'
                                              option proto '3g'
                                              option device '/dev/ttyACM0'
                                              option ppp_redial 'demand'
                                              option defaultroute '1'
                                              option peerdns '1'
                                              option service 'umts_first'
                                              option sconnservice 'UMTS'
                                              option dialnumber '*99***1#'
                                              
                                              config device 'modem_cell'
                                              option name 'modem_cell'
                                              option present 'Yes'
                                              option protoall '3g'
                                              option pppddev '/dev/ttyACM0'
                                              option statedev '/dev/ttyACM3'
                                              option Manufacturer 'Telit'
                                              option Product 'HE910'
                                              option Vendor '1bc7'
                                              option ProdID '0021'
                                              option SerialNumber '357164040868450'
                                              option Rev '12.00.004'
                                              
                                              config device 'sim_card'
                                              option name 'sim_card'
                                              option present 'No
                                              
                                           
  2. Add apn according to the SIM card operator. For e.g. "3gnet" for China Unicom
    root@WR-IDP-XXXX:~# uci set network.wwan.apn="3gnet"
                                              root@WR-IDP-XXXX:~# uci commit network
                                              root@WR-IDP-XXXX:~# uci get network.wwan.apn3gnet
                                           
  3. Setup WWAN interface.

    restart wwan interface: root@WR-IDP-XXXX:~# ifdown wwan ; ifup wwan

    or

    restart all interfaces: root@WR-IDP-XXXX:~# systemctl restart netifd

  4. Step 2 and Step 3 can also be performed through in LuCi web interface.

    On the WWAN tab. Set APN first, and then click Save & Apply button to apply the changes as shown in the sample LuCi web interface.

    Image: LuCi interface for WWAN connection configuration

  5. Check the 3g-wwan interface is ready.
    root@WR-IDP-XXXX:~# ifconfig 3g-wwan
                                              3g-wwanLink encap:Point-to-Point Protocol  
                                              inet addr:10.3.203.207  P-t-P:10.3.203.207  Mask:255.255.255.255
                                              UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
                                              RX packets:238 errors:0 dropped:0 overruns:0 frame:0
                                              TX packets:322 errors:0 dropped:0 overruns:0 carrier:0
                                              collisions:0 txqueuelen:3 
                                              RX bytes:35017 (34.1 KiB)  TX bytes:35054 (34.2 KiB)
                                              
                                           

Register Edge Gateway at Intel Developer Hub

The Dell Edge Gateway 5000 series with Wind River Linux IDP 3.1 supports Developer Hub portal within the Gateway. This portal can be used for performing variety of configuration functions on the Gateway along with using it for developing software layers on top of the base Wind River Linux OS Image, sensor devices integration to the gateway and hardening of the combined application / base OS image for deployment.

The developer portal has to be used for registering the Edge Gateway 5000 at Intel Marketplace to obtain credentials to connect to the software package update repository. The following are the two key URLs required for developer solutions on the Edge Gateway using Wind River Linux IDP.

http://shopiotmarketplace.com : This is registration site for registering your Gateway device with Wind River Linux and obtaining credentials for Windshare repository access for package updates.
  • NOTE: For Dell Edge Gateway with Wind River Linux OS image solution, your (customer’s) Dell point of contact should have already registered your contact information at Intel IoT Marketplace and you should have received notification from Intel marketplace on procedure for you to get login credentials to Windshare repository from where software packages and updates to Wind River Linux OS can be obtained. If you have not received notification from Intel IoT Marketplace, contact your Dell sales point of contact to get you registered.

Some of the detailed documentation on how to develop for Wind River Linux OS image based Gateway 5000 solution and how to utilize built in Developer Hub are available at www.intel.com/gatewaytraining please refer to that site for more details.

The following steps gives basic guidelines to follow once you receive your Dell Edge Gateway 5000 product with Wind River Linux IDP 3.1 base OS image.

The Dell Edge Gateway 5000 product with Wind River Linux IDP 3.1 base image from the factory is shipped with particular version of the RCPL package(RCPL 13) from Wind River. The RCPL versions from Wind River are periodically updated by the Wind River team and it is recommended for the Edge Gateway user/customers to upgrade to the latest version of RCPL by following the procedure/steps indicated below before developing software stack and middleware on top of the OS image. The latest RCPL image provides security updates and other bug fixes for the software packages.
  • Connect the Ethernet WAN port ETH1 of your Dell Edge Gateway 5000 series platform that came with factory installed Wind River Linux OS image to an internet connected router that can assign a DHCP address to the Gateway’s ETH1 interface. Make sure this connection has direct internet access outside of firewall and proxy connection during initial setup.
  • Login into the OS using default root/root credentials on the Gateway. Find out the IP address of the ETH1 interface using ifconfig.
  • In the linux prompt enter the root@WR-IDP-XXXX:~# smart update command to update the package cache and default repository channel. The smart update command updates the cache of already included update channels and repository.
  • Enter the root@WR-IDP-XXXX: smart channel --list to list the default channels supported by the factory image on the Edge Gateway.
  • At this point, with another browser enabled PC system connected to the same network as the Gateway , type in the IP address of ETH1 interface on the browser URL address, i.e. http://<IP-Address-ETH1-Interface>. Default evaluation of this was performed using Google Chrome browser, if available use Chrome browser.
  • A pop-up window shows up with requiring the user to login. Log in to the browser window using " gwuser" as username and " gwuser" as password.

    Image: Login screen

  • Read license agreement and follow instructions to continue.

    Image: License agreement

  • Select the packages tab inside the IoT Developer Hub, search for iot-developer-hub package and select to update that package only, it is not necessary to update other packages at this time. Give few minutes for package to download and update.
  • After update if the browser session terminates or logs the user out, follow the procedure above to log back in into the web interface. Since the update might be happening it might take couple of minutes to re-connect for the web interface to respond, wait until the interface allows to log the user back in.
  • Once logged back into the developer hub, go into the "Administration" tab and choose "Upgrade to Pro" option. This tab updates all the Pro Packages from Wind River that are already licensed and available free to install with the Gateway 5000 series product with Wind River OS license.
    • When Upgrade to Pro is selected, the user will be asked to enter Wind River credentials for Windshare repository. The user’s sales contact at Dell should have already registered your contact information with Intel/Wind River and the user should have received email notification from Intel / Wind River describing the procedure and process to obtain the Windshare repository credential from Intel/Wind River.

      Image: Wind River upgrade credentials

      Image: OS upgrade credentials

    • If you have not gotten such email, contact your sales contact at Dell to get you through the registration process to obtain credentials for the Windshare repository.
    • When the WindShare credentials are entered, additional set of repositories from where packages can be downloaded are added to the channel list. The additional set of channels can be reviewed by using the smart command in the Linux prompt – smart channel –-list .
  • Once the Wind River credentials are entered during the Upgrade to Pro package selection, the upgrade process should continue and would take some amount of time to complete. Wait for few minutes for the upgrade to complete.
  • Once upgrade to Pro packages are complete, exit out of the browser and clear browser cookies and cache, re-login back into the Developer Hub using the procedure described above and under "Administration " tab choose "Install OS Updates". The system might ask for Windshare Pro credentials, re-enter the Windshare repository credentials obtained as describe in the steps above.
  • At this point the system should check for update availability in the Windshare repository and would indicate if any updates are available, if available initiate the update process using the Install OS Updates. Such updates could take possibly up to an hour or more depending on your network connection. Let the system update to complete and make sure the internet connection is continuous.

    Image: OS updates

    Image: OS update installation progress

  • Once the update of the OS is complete, the Gateway should reboot and now the system should be upgraded to the latest RCPL release available for the Gateway 5000 product at the Windshare repository. At this point the user should have an environment ready to develop other layers of applications on top of the Gateway 5000 system.

    Below are some of the sample screenshots of the Developer Hub web interface described in the steps above.

    Below are some of the sample screenshots of the Developer Hub web interface described in the steps above.

    Image: Developer Hub web interface

    Image: Developer Hub web interface

  • The package tab indicates installed packages on the platform, update to the packages can be performed and additional repository channels can be added through the developer hub portal.

Common port mappings on Edge Gateway 5000 with Wind River OS

Serial Port Mapping

Description: The following table show the serial port mapping on the Edge Gateway 5000 platform installed with Dell factory installed Wind River Linux OS image. For dip switch setting on the Edge Gateway for RS422 and RS485 ports please refer to appropriate hardware installation guide document.
  • NOTE: Device nodes are ordered by port position starting from the leftmost RS232 port.
Table 1. Device nodes of serial ports on the Dell Edge Gateway 5000 series
No.Port TypeConnectorDevice Node
1RS232DB9/dev/ttyS0
2RS422_4855 pin terminal/dev/ttyS4
3RS4853 pin terminal/dev/ttyS5
4RS4853 pin terminal/dev/ttyS2

Edge Gateway I/O Module GPIO Mapping

Description: The GPIOs on the Gateway are managed through GPIO driver on the OS. The cloud LED on the Gateway is attached to one of the GPIOs and below are the steps on how to control the cloud LED in Wind River Linux OS.
  1. Export Cloud LED PIN:
    root@WR-IDP-XXXX:~# echo 346 > /sys/class/gpio/export
                                              root@WR-IDP-XXXX:~# echo out > /sys/class/gpio/gpio346/direction
                                           
  2. Turn on Cloud LED:
    root@WR-IDP-XXXX:~# echo 1 > /sys/class/gpio/gpio346/value
  3. Turn off Cloud LED:
    root@WR-IDP-XXXX:~# echo 0 > /sys/class/gpio/gpio346/value

Edge Gateway I/O Module based GPIO Mapping

Description: The GPIOs on the external I/O module for the Edge Gateway are behind PIC microcontroller. The PIC microcontroller is exposed to the host system and to the host OS as a USB-HID device. Software application developed to communicate with the GPIOs may use the protocol defined in following set of references to communicate with the GPIO modules. There are no native application software available on the factory OS image that communicates with the IO module GPIOs.

The I/O module GPIO mapping and references will be provided as a separate technical sheet and article and will be released at the support web portal for user/customer reference.

Edge Gateway I/O Module PCIe expansion mapping

Description: The PCIe slot on the external I/O module for the Edge Gateway are driven directly from the host PCIe bus. Since it is generic PCIe expansion there are no PCIe device specific drivers integrated into the Wind River Linux OS image. If there are specific PCIe card used on this slot, contact the vendor of that PCIe card to verify if they have Linux drivers and if that is a kernel mode driver such driver may have to be ported to Wind River Linux OS environment which uses 3.14 Linux kernel version on the Wind River Linux OS image shipped from the factory on the Gateway.

Edge Gateway Zigbee Module Functions

Description: The Edge Gateway supports a USB Zigbee dongle as an optional add-on hardware. When the Zigbee dongle is present on the system it is enumerated to the OS as a USB device and accessed through cdc_acm kernel driver layer on the Wind River Linux host. There are no native application software on the factory installed OS image to perform Zigbee protocol for this device. A basic communication with the Zigbee module can be verified using minicom terminal interface application as well as to get basic information from the Zigbee dongle.

For example: The following command would launch minicom with device /dev/ttyACM6 assuming the Zigbee dongle is enumerated into /dev/ttyACM6 port.
root@WR-IDP-XXXX:~# minicom –D /dev/ttyACM6
The Screenshot below shows the response from the Zigbee dongle when the Zigbee USB dongle is enumerated under /dev/ttyACM6 port.
  • Sending an AT command inside minicom session should return an OK from the device.

    Image: Sending AT commands

  • Sending an ATI command inside the minicom session should return the module information like “Telegesis ETRX 3588” etc.

    Image: AT return

Edge Gateway CAN Module Functions

Description: The Edge Gateway supports an optional CAN module that is mounted inside the Gateway itself. The CAN module is enumerated to the OS as a USB device as USB HID device to the Linux kernel driver layer on the Wind River Linux host. There are no native application software on the factory installed OS image to perform CAN protocol for this device.

The CAN module presence on the Gateway can be identified by issuing “lsusb” command in the Linux prompt and looking for “Microchip Technology Inc.,” based device.

For CAN communication protocols and software API references a separate set of references and articles will be provided outside of this document.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\