Gateworks AVILA GW2348-4 Install Guide
From wiliGear wiki
This document helps WILI user to install WILI software (WILI-S/WILI-MESH) on AVILA boards from Gateworks ™. Within this document you will be guided through WILI installation, licensing and connection.
Contents |
Installation Requirements
Software requirement:
- WILI-Software (WILI-S or WILI-MESH) for AVILA
Hardware requirements:
- AVILA GW2348-4 Board from Gateworks ™ (http://www.gateworks.com)
- Board details:
- CPU: IXP425BDT or IXP425ABDT (supported since v5.24 software version), 533Mhz
- RAM: 64 MB
- FLASH: 16 MB
Network requirements:
- Internet connection for accessing WILI Remote Configuration Management Server (WILI RCMS)
- TFTP server
- DHCP server enabled on LAN (optional)
Client requirements:
- IEEE 802.11 card for the client
- Laptop or PC (preferably running Microsoft® Windows® XP operating system software)
Upgrade AVILA Board with WILI
After completing the following steps, you will have WILI-S live and running on the dedicated AVILA board. We assume you have running TFTP server and TFTP client on AVILA board. We will use the following IP addresses in the command examples:
- TFTP server uses IP address 192.168.1.254/24
- AVILA device uses IP address 192.168.1.20/24.
1. Download purchased WILI AVILA FW archive from WILIBOX website, Store area. Registration is required to access your store archive.
2. Extract downloaded WILI AVILA FW archive to a temporary folder. You will find files: squashfs.img (image with WILI) and zImage (Linux kernel)
3. Copy extracted WILI AVILA files (squashfs.img and zImage) to TFTP server.
4. Make serial port connection as direct physical connection to the WILI AVILA. Connect
serial console cable from your laptop or desktop PC to AVILA board.
- Set console speed (bits per seconds): 115200
- After successful connection you should see RedBoot console prompt.
| Press Ctrl+C to stop startup script (if enabled). |
5. Configure IP address for local interface and TFTP server:
ip_address -l <192.168.1.20> -h <192.168.1.254>
| Do not forget to modify TFTP server address. We are using 192.168.1.254 as TFTP server address in this example. |
6. Initialize [format] FLASH image system of your AVILA board by command fis init
RedBoot> fis init About to initialize [format] FLASH image system - continue (y/n)? y ***Initialize FLASH Image System ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
7. Load zlmage (Linux kernel) from TFTP and store it to FLASH:
RedBoot> load -r -b 0x01600000 zImage Using default protocol (TFTP) Raw file loaded 0x01600000-0x016c7ff7, assumed entry at 0x01600000 RedBoot> fis create -b 0x01600000 -f 0x50080000 -l 0x00100000 -r 0x01600000 zImage ...Erase from 0x50080000-0x50180000: ....... ...Program from 0x01600000-0x01700000 at 0x50080000: ....... ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
8. Load squashfs.img (image with WILI) from TFTP and store to FLASH:
Redboot> load -r -b 0x00800000 squashfs.img Using default protocol (TFTP) Raw file loaded 0x00800000-0x00acdfff, assumed entry at 0x00800000 RedBoot> fis create -b 0x00800000 -f 0x50180000 -l 0x00500000 ramdisk ...Erase from 0x50180000-0x50680000: ......... ...Program from 0x00800000-0x00d00000 at 0x50180000: ............. ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
9. Create system configuration data sections in FLASH:
RedBoot> fis create -b 0x00000000 -f 0x50680000 -l 0x00080000 -n cfg ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
10. Create filesystem (jffs2) sections in FLASH:
RedBoot> fis create -b 0x00000000 -f 0x50700000 -l 0x008E0000 -n etc ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
11. Configure RedBoot to load kernel:
RedBoot> fconfig Run script at boot: true Boot script: Enter script, terminate with empty line >> fis load zImage >> exec 0x01600000 >> Boot script timeout (100ms resolution): 1 Use BOOTP for network configuration: false Gateway IP address: Local IP address: 192.168.1.20 Local IP address mask: 255.255.255.0 Default server IP address: 192.168.1.254 Console baud rate: 115200 GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Default network device: npe_eth1 Update RedBoot non-volatile configuration - continue (y/n)? y ...Unlock from 0x50fe0000-0x51000000: . ...Erase from 0x50fe0000-0x51000000: . ...Program from 0x03fe0000-0x04000000 at 0x50fe0000: . ...Lock from 0x50fe0000-0x51000000: .
12. Type the reset command to load WILI AVILA on your AVILA board. After successful
installation you will see WILI login prompt.
Connect WILI Based AVILA to Your Network
To prepare your WILI based AVILA for use only the standard connection setup is needed. See the following list to check if you have everything ready for WILI based AVILA:
- Prepared WILI based AVILA (see sections above how to prepare your WILI based AVILA)
- Internet connection
- DHCP server enabled on LAN (optional)
- Administrator computer
- WILI client (e.g. your laptop with wireless connection)
Standard Connection Setup
Connect WILI based AVILA to your network as shown in scheme (see Figure 1 – Network Connection for WILI-based Device). The example of the network with RCMS server presented below shows the optimal range of possibilities provided by WILI. RCMS server is an optional product revealing the full functionality of WILI management but it is not mandatory. Read more about RCMS on www.wilibox.com
Follow the instructions to prepare your WILI based device ready for use:
1. Connect board to the same LAN as Administrator computer. Your local network should have the Internet connection.
2. Make sure the DHCP server is enabled on your network and WILI based AVILA is on the same LAN. WILI based AVILA is DHCP client by default. If there is no DHCP server running on your network, the WILI-S based AVILA will respond to the static IP address 192.168.2.66
3. Prepare WILI client: make sure wireless communication is switched on.
Licensing Your WILI based Device
After having purchased WILI you get a license key. This key need to be uploaded on WILI based device at once. Once you have licensed WILI it unlocks all functionality and can be used for unlimited period of time.
After licensing the device it will be set to a valid licensing status and you will get the full scope of benefits:
- Full functionality of the purchased WILI firmware release
- 1-year free service release updates according to the purchased WILI firmware revision. During this year any of service release firmware revisions can be used for the unlimited period of time.
- 2-weeks support assistance: 10 business days, up to 5 hours, e-mail communication and answer provided within 2 business days.
WILI firmware you have purchased comes with no license included (not valid status). This status provides only a very limited functionality:
- It runs only with a default configuration. Only a single BSSID is allowed; DHCP client runs on WAN interface, DHCP servers run on LAN and Wireless interfaces.
- It is impossible to change the configuration. All features are locked down until a valid license is presented. Any changes made in configuration will be stored in the flash memory of the device. Thus only a default setting will be used after the reboot.
Follow the simple diagram on how to license your WILI device:
Technical Support
If you have any problems, contact Wiligear for assistance at support@wiligear.com


