After storing the files in USB storage, plug the USB storage into the USB port on the WB45 breakout board

Type the following commands to upgrade via the USB interface:

Summit Data Communications

summit login: root

Password:

#

#

# /etc/init.d/opt/S91g_ether stop

Disabling USB gadget ethernet

# /etc/init.d/opt/S37usbhost start

Enabling USB host-mode for Mass Storage

# sd 0:0:0:0: [sda] No Caching mode page present

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] No Caching mode page present

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] No Caching mode page present

sd 0:0:0:0: [sda] Assuming drive cache: write through

# cd /media/usb0/

# cd wb45n-laird_fips-3.4.1.106/

# ls

bootstrap.bin  fw_select      kernel.bin     u-boot.bin

fw.txt         fw_update      rootfs.bin

# ./fw_update

Accessing images via locally attached media.

# wb45nbt update

Checking Bootstrap Loader...OK

Updating bootstrap from local...    à Choose Yes

  /media/usb0/wb45n-laird_fips-3.4.1.106/bootstrap.bin

  erasing, writing...(0s) OK

Checking U-Boot Loader... OK

Updating bootloader from local...    à Choose Yes

  /media/usb0/wb45n-laird_fips-3.4.1.106/u-boot.bin

  erasing, writing...(0s) OK

Checking Linux Kernel...

Updating kernel-a from local...    à Choose Yes

  /media/usb0/wb45n-laird_fips-3.4.1.106/kernel.bin

  erasing, writing...(1s) OK

Checking Root Filesystem...

Updating rootfs-a from local...    à Choose No

  /media/usb0/wb45n-laird_fips-3.4.1.106/rootfs.bin

  erasing, writing...(12s) OK

Sync'ing updated_% at91bs=x u_boot=x kernel=a rootfs=a

Done.

fw_select v20130313

Stopping LigHTTPd

Stopping inetd services.

Stopping network interfaces... wl eth0 lo

Stopping system message bus: done

Saving random seed... done

Stopping execution of events, via udev...

Stopping logging services: syslogd klogd

The system is going down NOW!

Sent SIGTERM to all processes

RomBOOTGKILL tRestarting system.

 ba_offset = 0xb ...

Loading 1-Wire info...

Enumerate all roms:

Done, 0x0 1-wire chips found!

sn: 0x0;   rev: 0x0

AT91Bootstrap 3.4.4-laird2 ( Mon Apr 14 12:50:28 EDT 2014 )

Downloading image...

Nand: ONFI not supported

NAND device: NAND 128MiB 1,8V 8-bit, Manufacturer ID: 0x0 Chip ID: 0xa1

Nand: Copy 0x80000 bytes from 0x20000 to 0x23f00000

Done!

 U-Boot 2013.01-laird2 (Apr 14 2014 - 12:50:30)

CPU: AT91SAM9G25

Crystal frequency:       12 MHz

CPU clock        :      400 MHz

Master clock     :  133.333 MHz

DRAM:  64 MiB

WARNING: Caches not enabled

NAND:  128 MiB

MMC:   mci: 0

In:    serial

Out:   serial

Err:   serial

Net:   macb0

Hit any key to stop autoboot:  0

NAND read: device 0 offset 0xe0000, size 0x280000

 2621440 bytes read: OK

## Booting kernel from Legacy Image at 22000000 ...

   Image Name:   Linux-3.8.0-laird15

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2150254 Bytes = 2.1 MiB

   Load Address: 20008000

   Entry Point:  20008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

gluebi (pid 1): gluebi_resized: got update notification for unknown UBI device 0 volume 0

Starting logging services: syslogd klogd

Starting udev daemon, populating /dev

Initializing random number generator... done

Checking platform... wb45n-laird_fips-3.4.1.106

  updated bootstrap: (-?-)

  updated u-boot: (-?-)

  updated kernel-a (95fbed43d075ff3050e7e5bb00e632cb)

  updated rootfs-a (b4645e745a88e3cdf68b2749efecbd83)

Starting system message bus: done

Starting network interfaces... lo eth0 wl usb0

Starting inetd services...

  tftp is setting up...

  ssh is setting up...

  ftp is setting up...

Starting LigHTTPd

Summit Data Communications

summit login:

The FTP firmware upgrade daemon will send notifications with the firmware update status to UDP server port 2012. This is sent as a UDP datagram and XML formatted with: ethaddr, fw-build-version, status-word, and an optional message.

The status text is one of the following: update_success,  update_pending,  update_failure, update_error

Following the re-flashing of all images on the WB, an "update_pending" is sent back to the server. Upon reboot of the pending WB update, a platform init-script processes any updated settings. If the update is successful and the WB rebooted correctly, then the text “update_success” is sent to the server.

If you don't want simultaneous ap/sta, you can run the commands:

nmcli conn add type wifi ifname wlan0 con-name softAP autoconnect no ssid softAP

nmcli conn modify softAP 802-11-wireless.mode ap 802-11-wireless.band bg 802-11d

nmcli conn up softAP

You can also do it via wpa_supplicant .conf files if you do not have nmcli.

By default, it will show annoSUMMIT as outer ID to protect the ID not showing in public. If really need to show the real ID in outer ID, then need to add semicolon (;) at the end of ID configuration to make it happen.

Here are the commands to disable AP Mode in CLI: sdc_cli iface set hostapd wlan0 off ifrc wlan0 restart

Here are the instructions to disable AP Mode: Quick Start Guide - WB45NBT.pdf

After running the fw_update script and reboot.  If you're unable to complete the boot sequence and your terminal screen matches the attachment/image, there might be an issue with the u-boot not recognizing the kernel version you updated to.  In this case, we recommend reaching out to our support team for assistance. 

Copy/paste each (whole) line needed into u-boot, one-at-a-time:

#To revert to kernel-a and rootfs-a: setenv bootargs 'console=ttyS0,115200 loglevel=4 rw noinitrd mem=64M rootfstype=ubifs root=ubi0:rootfs ubi.mtd=6' setenv bootcmd 'nand read 0x22000000 0x000E0000 0x00280000; run _mtd; bootm' saveenv #To revert to kernel-b and rootfs-b: setenv bootargs 'console=ttyS0,115200 loglevel=4 rw noinitrd mem=64M rootfstype=ubifs root=ubi0:rootfs ubi.mtd=7' setenv bootcmd 'nand read 0x22000000 0x00360000 0x00280000; run _mtd; bootm' saveenv

The responsibility for providing the QDID for a host system is with the provider of the stack that is used on that system. If for instance the host system uses a module that requires the Bluetooth stack to run on that system (e.g. Lairds Sterling-LWB in a Linux platform) the QDID must be provided by the stack vendor who's stack is running on that Linux platform. Challenges might occur when an open-source, community based stack is used. If a module with integrated stack us used (e.g. Lairds BL652) the QDID is provided by the module vendor.  

Yes, we can position our WB as a system on module.  Technically speaking, the WB is a SoM, but we historically haven?t marketed it as such. Our Wireless Bridges are suitable for instance as the main processing unit for a headless (no screen) IoT product. The WBs have everything needed for a SoM except graphics/screen capabilities.   

The answer basically is "no, not really". The SPI port isn't a serial tty in  Linux. To interface with SPI on the WB45NBT (or 50): 1. A DEVICE to connect to the SPI port. The WB is always the MASTER. 2. The Atmel SPI master driver needs to be loaded. 3. Either a driver specific to the connected device needs to be loaded or the SPIDEV driver needs to be used. 4. If the SPIDEV driver is used, a small c program could be written to read/write the SPI device and put the data out as a socket. At that point it should be easy to connect that across WiFi. It might be possible to use it as a character device directly, and in that case that using ?socat? can work. But very rarely is it appropriate to "bridge" SPI data to WiFi. SPI devices don't directly talk UDP or TCP over IP. So, while you absolutely can connect SPI devices, gather and process their data and then send that data over WiFi, you can't simply "connect" SPI to WiFi and bridge it. (curtesy Steve deRosier)  

Issue command setenv bootdelay s where ?s? needs to be replaced by an integer number for the time you wish to delay in seconds. Please note, setting ?s? to 0 results in the U-boot environment not being accessible anymore through key strokes during start-up.

Both the WB45 and WB50 implement very significant power saving modes, including all of the modes supported by the processor. In particular the WB50 supports the low-power features of the SAMA5D3x processors as outlined in the Atmel datasheet.

All this can be controlled through standard Linux commands/programs like ?iw?, ?hostapd?, ?wpa_supplicant?, ?wpa_cli?, etc.

The ECCN for the radios listed, which comprise the "Summit" line of Wi-Fi radios, is 5A002.

We highly do not recommend conformal coating the radio module. If you plan on encapsulating the radio module in a potting compound or conformal coating, you must assure that the compound in liquid or solid form does not enter under the shield where there are sensitive RF components. Some of the capacitive and inductance values are as low (pF and nH) and could be sensitive to contacting materials such as potting compounds. There are potting compounds and conformal coatings which have very good dielectric constants and are suitable for 2.4 GHz potting applications, however, when you apply any of these, they were not accounted for in the circuit design and might reduce performance of the device (or all together cause it not to function).  You should run tests on their particular potting compound and evaluate radio's performance and range.  Also, it's worth mentioning that applying any compound, conformal coating or potting directly to the module WILL void the warranty. If your application requires 100% sealing of the radio module, there is a way to do this very successfully without impacting the module performance. Simply place the module on your PCB. Place a plastic cover over the module (like a hat), make the cover large enough to cover the whole module. Apply glue around the bottom perimeter of the cover where it sits on the PCB. This allows the module to function in free air-space while there is a complete seal around it. This information is only for reference and we recommend you should conduct your own testing with your prototype of your end application to find the best suitable fit for your design.  

Ezurio provides 3D files (STEP) files for most but not all of it's modules.  Based on the nature of the information in the files, in most cases Laird requires a login to access these files as well as layout files and software/firmware downloads.  As such, for most modules, the 3D files are found under the Software Downloads tab of the product page.  The page offers a credentials request link for customers who need credentials.  In most cases, the credentials are provided via return email within about 10 minutes. Please contact support if you have any additional questions or have any issues accessing our downloads.

We only recommend reflowing our modules once as it can damage the module and void the warranty.

Ezurio provides layout files PADS and PADS ASCII formats. The ASCII files will import to Altium (and Protel varients) as well as Cadence (Orcad and Allegro) CAD packages. As far as we know, there is no way to import to Eagle CAD. Please be sure to use the .asc file for PCB and the .txt file for the schematic when importing to Altium. Ezurio uses ORCAD for schematics (Gerbers). 

The recommended cleanser is "hydrocarbon cleaning oil", which can be used to clean the RF shield and PCB. We do not recommend the use of alcohol as it doesn't work as well and could leave residue on the boards.  

You can use this command in sdc_cli: "sdc_cli iface set hostapd wl on"

There are two partitions in the WB45NBT, partition A and B. In partition A, the ubi.mtd is 6 and the kernel boot address is 0x000e0000. In partition B, the ubi.mtd is 7 and kernel boot address is 0x00360000. Here is an example of how to swap from partition B to A: setenv bootargs ?console=ttys0,115200 loglevel=4 rw noinitrd mem=64M rootfstype=ubifs root=ubi0:rootfs ubi.mtd=6? setenv bootcmd ?nand read 0x22000000 0x000e0000 0x00280000; run _mtd; bootm? saveenv reset When you load another partition, it may be loading an older version of the WB software.

Supplicant logging can be turned on using the CLI and the "logging" command. For example, # sdc_cli logging set supplicant error # sdc_cli logging show Note that valid parameters that can be used in place of "error" are none, error, warning, info, debug, msgdump, and excessive.

Initialization scripts that run every time the WB45 boots up are stored in "/etc/init.d". Notice that the scripts here have a naming convention such that they start with "S99" where 99 can be replaced by any number. The scripts are run in ascending order meaning S24script will run before S45script runs. It is recommended that customer scripts are run after all default scripts run so that the module may be fully initialized.

The version information for your WB45 can be accessed by using the CLI. This version information includes the following: CLI, SDK, Hardware Chipset, Driver, Firmware, Supplicant, and Build. # sdc_cli version

The WB45 does not support antenna diversity. It utilizes one antenna port for WiFi and one antenna port Bluetooth.

The WB45 supports the following EAP types: LEAP EAP-FAST PEAP-MSCHAPv1 PEAP-MSCHAPv2 PEAP-GTC EAP-TLS EAP-TTLS PEAP-TLS

Yes, the WB45 supports FIPS encryption. For more information on FIPS see this post,  https://laird-ews-support.desk.com/customer/en/portal/articles/1431831-…-?b_id=1908

FIPS can be enabled on the WB45 with the following commands # sdc_cli global set fips on Note that valid parameters for this command are "0" or "off" and "1" or "on".

By default, the WB45 has ttls-inner-method set to "auto". This mode will auto negotiate which ttls inner method to use. For example, if your network is set to use mschapv2 then the WB45 will use mschapv2 as its inner method when authenticating to that network.

The TTLS inner method or "ttls-inner-method" can be changed in the global settings of the sdc_cli. See the following commands. # sdc_cli global set ttls-inner-method mschapv2 # sdc_cli global show Note that valid parameters for the ttls-inner-method are

The roam delta cannot be adjusted on the WB45. However, the roam trigger and roam period (in milliseconds) can be adjusted.  This can be done with the following commands. # sdc_cli global set roam-trigger 75 # sdc_cli global set roam-period-ms 6000 # sdc_cli global show Note that valid parameters for roam trigger are and valid parameters for roam period are 10

By default the WB45 ships in the WW or World Wide mode. This uses a subset of channels or frequencies that are allowed in all regulatory domains. It also enables 802.11d which will listen to beacons from the surrounding networks to determine what country it is in and therefore which regulatory channel set should be used instead of WW mode. This can be changed using a utility developed by Laird. Please contact Laird support for more details.

The default certificate path of "/etc/ssl" can be changed by using the sdc_cli global settings. # sdc_cli global set certpath /your/file/path/here You can verify this change with # sdc_cli global show

The default certificate path on the WB45 is "/etc/ssl". Note that there is a folder labeled "certs" at that location, but the certs do not go in that directory. By default, they need to be in "/etc/ssl".

The "Static" method on an interface will allow you to statically assign networking addresses such as the IP address, subnet mask, and gateway via the sdc_cli using iface commands or by editing the /etc/network/interfaces file in the Linux file system. The "Manual" method on an interface will result in the interface not being assigned any type of address. The user will need to set the address, subnet mask, and gateway using other tools within the host system.

In the sdc_cli you can change the method of a networking interface by using "iface" commands. # sdc_cli iface set wlan0 dhcp The example command follows the syntax of: iface set method [interface] [dhcp/static/manual]

CCKM is supported with all EAP types Laird supports?LEAP, EAP-FAST, PEAP-MSCHAPv2, PEAP-GTC, PEAP-TLS, EAP-TLS and EAP-TTLS. ACS supports all of the EAP types except EAP-TTLS. However, supporting CCKM is not dependent on using ACS as the RADIUS server. Laird can do CCKM with any RADIUS server since CCKM support is in the wireless infrastructure.

In some cases you may want or need to manually mount some type of USB storage. First, be sure that the module is in USB host mode. For help with this see the " Switching between USB host and device mode " application note. Once you are in USB host mode, if your drive has not automatically mounted you can use the following command to do so: # mount /dev/sda1 /mnt Please note that there is a space between /dev/sda1 and /mnt. This will mount your drive to a folder or location called /mnt. You can navigate there or see the contents using these commands: # cd /mnt # ls /mnt

In the firmware upgrade package, there is a file called "fw.txt". You can add the following lines to transfer the files from the old image to the new upgraded image. For example, to keep the profiles and network setting during the firmware update process, add these three lines in the "fw.txt" file. #transfer-list: /etc/summit/profiles.conf /etc/network/interfaces

EAP-TLS is a tunnel authentication. outer identity: this is the User-Name in the RADIUS packet and visible to all intermediate parties inner identity: this is the actual user identification. It is only visible to the user himself and the Identity Provider The user cert is issued to a user identified by the username, so the username has to be configured so we know which user cert we should be using for the authentication. By default, the username is also used during authentication as the outer identity which gets sent in the identity response packet.

To change the loglevel in run time, you can echo the number to /proc/sys/kernel/printk. However, this setting is in RAM and won't be kept in next boot. # echo 8 > /proc/sys/kernel/printk To keep this setting, you need to set it in bootargs in boot loader configuration. Such as add an extra setting "loglevel=4" as below. bootargs='mem=32M console=ttyS0,115200 ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs loglevel=4 rootflags=bulk_read,chk_data_crc rw'

There are two reasons to send out null packets with p bit enabled. 1. Its RSSI has crossed over the Roam Trigger and the client radio is supposed to start scanning for a new AP. 2. The client radio is running one of our power-save modes (Fast or Max) and is going to sleep for a brief (e.g. 20 ms) period and is telling the AP so it will buffer traffic for it while it sleeps. After a radio has slept for some period of time (defined as the interval between DTIM periods) it is supposed to wake up and indicate to the AP that it is awake by sending a null packet with the P-bit turned off. The radio should only wake if it has traffic to send or it sees from the DTIM in the AP?s beacons that the AP has traffic to send to it.

The WB45 ships, by default, with hostapd enabled. This mode can be turned off in the sdc_cli by using the "iface" command and the appropriate parameters. Once it is turned off, the wlan0 interface must be restarted. Then you can verify that hostapd mode is no longer enabled by using the status command. # sdc_cli iface set hostapd wlan0 off # ifrc wlan0 restart # sdc_cli status The same method can be used to turn hostapd mode on. Just perform the same 3 commands, but replace "off" with "on".

To keep the files during the firmware upgrade in WB45, you will need to add the list followed by "# transfer-list:" in fw.txt in the release package. For example, to keep the certificates that are under /etc/ssl/certs during firmware upgrade, you need to add the following string in fw.txt in the release package. # transfer-list: /etc/ssl/certs

In the WB45 the syslog is initialized by S01logging under /etc/init.d. To change the syslog size, in S01logging you'll see the line "/sbin/syslogd -D -C32 -m0 \", change the -C32 to -C256 or -C512. The number after the -C equals the buffer size in KB. By default, the size is set to 512KB.

Multi-client connections are not currently supported by the WB45NBT. The AP feature was designed to support one client connection for ease of configuration. Contact your Regional Sales Manager (RSM) to discuss your business case if your intended development would require multi-client AP mode.

The following channels require DFS in Korea KCC/KC domain. Channel Frequency MHz 52 5260 56 5280 60 5300 64 5320 100 5500 104 5520 108 5540 112 5560 116 5580 120 5600 124 5620

A list of our radios and supported connector types can be found here: WiFi + Bluetooth Modules

mandatory/optional input for EAP type   EAP credentials Mandatory input Optional input LEAP User name, user password   EAP FAST User name, user password PAC file, FAC password PEAP MSCHAP User name, user password CA cert PEAP GTC User name, user password CA cert EAP TLS User name, user cert CA cert EAP TTLS User name, user password CA cert PEAP TLS User name, user cert CA cert   Note 1: this settings should be read in user perspective but not for actual implementation. For example, when a user does not input PAC file, it will use auto PAC provisioning. If a user inputs it, it will do a manual PAC provisioning. Note 2: user password is not used for TLS but only user cert is used instead.    

With EAP-MS-CHAPv2, the data sent in tunnel will be encapsulated as EAP-MESSAGE AVP (attribute-value pair). In the case of MS-CHAPv2, there is no such extra encapsulation it is just the MS-CHAPv2 message.

The attached document is the list current channels for the KCC domain as of 2015. In document, red means DFS required.

The default mode, REG_WW, will enable 802.11d. The following specific regulatory domains are supported: REG_FCC, REG_ETSI REG_TELEC REG_KCC, REG_CA, REG_FR, REG_GB, REG_AU, REG_NZ, REG_CN. The following regulatory domains are planned to be available in the near future. REG_BR (Brazil) REG_RU (Russia)

Standard: indicates PMK Caching: This means that the 802.1x authentication can be skipped on an access point that a client has already authenticated to once before. Only the 4-way handshake needs to happen. This is useful for a client that needs to reconnect to an access point that it roamed away from previously, due to signal loss etc. However, if a client has not roamed to a particular access point during its current working session, it must then authenticate to that specific access point using 802.1x. PMK Caching is the method defined in the 802.11x (WPA/WPA2) specification. Opportunistic Key Caching: With this method, a client device can skip the 802.1x authentication with an access point after a full authentication,and only needs to perform the 4 way handshake when roaming to access points that are centrally managed by the same WLC in an LWAPP or other controller-based infrastructure. This means that the client doesn't need to authenticate with access points that it wants to roam to, as long as the client has authenticated successfully to at least one of the access points in the same zone as the access point that handled the previous successful authentication. In this case, the PMK identifier has been cached at a central location, like the WLC (or wireless switch.) With OKC, the client must support this method for it to be used, even if the infrastructure has been configured with OKC enabled.

For the WB45N, the server certificate should be located under path ?/etc/ssl?. Use a USB storage drive or wget to upload the file to WB45N and copy this file to ?/etc/ssl? folder. You will need to reboot the system to take effect. For the MSD45N, this certificate can be changed by customers during their integration. By default, it?s located in ?/etc/ssl?.

If the CA cert is expired, will see a message like the following in the log on the WB45N:

Oct 15 13:38:35 summit user.info laird[303]: Event: SDC_E_CONNECTION_STATE status: AUTH_ERROR Oct 15 13:38:35 summit user.info laird[303]: Auth reason: INVALID_CREDENTIALS With an expired user cert, the EAP-TLS or PEAP-TLS authentication will fail.

The message shown above will show up in the log when authentication fails due to using an expired user certificate.

The auto profile feature on the WB45 will cycle through wireless profiles until one connects successfully. Wireless profile are settings and credentials for specific SSIDs or wireless networks. A WB45 may be deployed in multiple areas that have different SSIDs. This is where auto profile may be useful because instead of trying to connect on a specific "active" profile it will cycle through all of the available profiles until one connects. Auto profile can be enabled using the CLI. # sdc_cli global set auto-profile on Note that valid parameters in place of "on" are "0" or "off" and "1" or "on".

The WB45 can support up to 20 wireless profiles at one time.