On September 21, 2017, the latest Vesta IoT Gateway developer images were released. Many improvements have been included - most importantly, mitigation of the "BlueBorne" vulnerability. We recommend that all development gateways be updated to this new image.
Lithium 3.2.0 Release
- Added Rigado Dev-Kit
- Added hostname to /etc/hosts
- Added zephyr-mode (On/Off scripts)
- Added zephyr-mode will execute on first boot
- Added Git Tools - Submodules
- Upgraded hostapd and wpa_supplicant from 2.5 to 2.6
- Applied Security fix key-replay-cve-multiple.patch to hostapd and wpa_supplicant
- Bugfix: rigtools 2.2.0 - send correct action id after an update
- Bugix: NXP Thread demo fix - remove static MAC address
Lithium 3.1.0 Release
- Added git v2.9.3 to vesta-image-developer
- Updated to zephyr v1.9
- Enabled HCI for both Bluetooth devices on the Vesta-200 and Vesta-300
Lithium 3.0.1 Release
- Added patches to bluez to protect against blueborne attacks.
- Added patches to Linux Kernel to protect against bluebourne attacks.
Lithium 3.0 release
- Added OpenOCD 0.10.0
- Added OpenOCD support for R41Z and BMD-300 modules
- Added Zephyr 1.8 binary for BMD-300 module
- Added nRF52 13.1.0 and softdevice 4.02 binaries for BMD-300 module
- Added bmd300_program.sh script for general programing of BMD-300 using OpenOCD
- Added r41z_program.sh script for general programing of R41Z using OpenOCD
- Added bmd300_program_zephyr.sh script to program BMD-300 with Zephyr binary
- Added bmd300_program_nRF52_PCBLE.sh script to program BMD-300 with PCBLE binaries
- Added paho-mqtt 3.1
- Added IOT Gateway Setup feature to allow setup of WiFi using the Gateway as an access point
- Added NXP Thread Demo 220.127.116.11
- Note: In order to activate and utilize the NXP Thread Demo, you will need a custom serial number and QR code from Rigado directly
- Upgraded to dgua 2.1.1 to report http error response codes > 400
- Upgraded to BlueZ 5.45
Bugfix: Enabled hardware random number generator fixes: Linux stalling for 2 minutes during boot if wlan0 is set to start automatically
- Bugfix: Disabled power management on QCA6234 at startup fixes: Long delays in WiFi transmissions
Outlined here are the steps necessary to update a Vesta gateway using the NXP Manufacturing Tool. This image may also be deployed to Internet-attached devices through our Rigado DeviceOps(TM) management platform.
All documentation for the Rigado Vesta Gateways including Rigado DeviceOps are available at: https://developer.rigado.com.
Installing a Development Build using USB
Listed below are the PC Requirements as found in the
Manufacturing Tool V2 (MFGTool2) Factory Operation Manual.docx in the
mfgtool/Document/V2 folder provided by NXP. Please make sure you can meet or exceed these requirements.
PC Minimum Requirements
CPU: Intel E3400 or higher. Frequency: 2GHz+
OS: Windows XP/Windows 7 version or higher
USB2.0 or USB3.0 root hub is a must, NO USB 1.1 root hub is allowed.
Use of an external USB hub is allowed with the following restrictions:
- The hub must use an independent power supply
- The hub must pass the applicable Product Test Requirements for hubs of the USB-IF Compliance Program. A Belkin USB hub is recommended.
- A utility to unzip "tar" files is necessary, such as 7-zip.
- NOTE: A Virtual Machine may be used. Ensure the following USB VID/PID combinations are configured to automatically connect to the VM:
- Vesta Gateway HID: VID=0x15a2, PID=0x007d
- Vesta Gateway MSD: VID=0x066f, PID=0x37ff
Install the NXP MFG Tool
Follow the steps below to install and customize the NXP MFG Tool to work with the Rigado Gateway:
Download the MFG Tool from NXP’s website. You will need an NXP account for this.
After the download has completed, extract the files from
Double-click on the extracted folder
Extract the files from the file
Double-click on the extracted folder
Your folder structure should look like the following image:
Download the file
rigado-mfgtool-profiles.zip.Save or move it to the folder
rigado-mfgtool-profiles.zipfile to the
Copy Yocto Build Images to the mfgtool Folder
The developer images are pre-compiled. Download the file
mfgtool-builds-li-3.2.0.zip. Extract the contents to the folder
mfgtool/Profiles/Linux/OS Firmware/files. The following image is an example of the
files folder after copying files over from this file.
Use the MFG Tool
Make sure the power supply is not connected to the Rigado Gateway device. If using PoE, unplug the Ethernet cable.
Connect the Rigado Gateway device to your Windows machine using a USB connector.
Hold down the user button while supplying power to the unit. This will put the Rigado Gateway in USB serial down-loader mode and allow the MFG Tool to communicate with the Gateway.
To start the MFG Tool, double-click on the appropriate
vbsfile. For example, for a Vesta-300B or Vesta-300R, open the file
If everything is connected properly you should see
HID-compliant devicein the status box as shown here:
NOTE: If you see
No Device Connectedin the status box, double-check your connections and try again. Be sure you are holding down the user button while supplying power to the Gateway. If using a VM, check the USB auto-connect settings for the proper VID/PID noted above.
Click on the Start button to begin the installation.
As the firmware is being downloaded and installed, various update messages will be displayed along the way.
NOTE: There will be approximately a 20 second pause after the initial transfer. The MFG Tool may show
No Device Connectedyet still show progress. This is normal while the gateway restarts the USB connection as a mass storage device (MSD).
Once the installation is successful, you should see a
Donemessage in the status box.
Click on the Stop button and Exit button to close the tool.
Cycle power to the Rigado Gateway device.
After power is applied, the Rigado Gateway will show an amber LED while booting, then turn green once a DHCP lease has obtained an IP address. You may now proceed with the documentation at https://developer.rigado.com.