The SMILE Plug is joint project between Globalscale and Marvell to support Stanford Mobile Inquiry-Based Learning Environment (SMILE). The device features Marvell's latest advances in hardware and chip design to deliver class leading cloud and wireless capabilities. The SmilePlug is designed with the Marvell Armada 370 SOC and Marvell’s new 4x4 wireless chip.
Marvell Avastar 88W8764 4x4 WiFi
External backup battery for hours of reserve power (optional)
2x USB 3.0
2x Gigabit Ethernet
1x Micro SD slot
1GB NAND Flash / 512MB DDR3 RAM
Marvell Armada 370 1.2GHz
This installation will provide a bare Arch Linux ARM installation without the SMILE software.
There is currently no support for a NAND installation. The root filesystem must be on SD or USB.
You must update U-Boot on the device for this installation. If you've updated U-Boot before, you do not need to do it again.
You will need a TFTP server set up to transfer the new U-Boot image. Set these values in U-Boot to reflect your network settings:
Type boot and hit enter, and the system will boot to SD card.
Login as the default user alarm with the password alarm.
The default root password is root.
Default Installation Information
To take advantage of the hardware, the installation by default sets the SMILE Plug up like a wireless access point.
The ethernet port closest to the power connector (eth0) is designated as the WAN port. This is configured by default to try to get an IP address via DHCP.
The ethernet port closest to the edge (eth1) is designated as the LAN port. This should be connected to a switch.
The wireless card (wlan0) is configured as an access point with the SSID "SMILE" and a default WPA passphrase of "smileplug". Configuration of the AP can be done through /etc/hostapd/hostapd.conf.
The eth1 and wlan0 interfaces are bridged together into the interface br0 with the static IP 10.4.0.1. The dnsmasq combined DHCP and DNS server runs on this interface issuing IPs in the range 10.4.0.5-250. Configuration of dnsmasq can be done through /etc/dnsmasq.conf.
There are default iptables rules in place to NAT connections on the AP or LAN port through to the connection on the WAN port.
Extra services installed by the user on the device should be made to listen on all interfaces, or on 10.4.0.1. This will ensure that AP and LAN connected clients can access the service.