Globalscale Technologies 003-MBX001 MIRABOX User Manual

Download:
Mirror Download [FCC.gov]
Document ID	1922614
Application ID	9oPVruSuxZByka1cLxLnmA==
Document Description	User manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	53.02kB (662750 bits)
Date Submitted	2013-03-21 00:00:00
Date Available	2013-03-21 00:00:00
Creation Date	2013-03-06 10:40:41
Producing Software	Acrobat Distiller 9.0.0 (Windows)
Document Lastmod	2013-03-07 15:12:18
Document Title	Microsoft Word - Mirabox User Guide_US_v1-Sep-20-2012-Tony_pm 20.40_.docx
Document Creator	PScript5.dll Version 5.2.2
Document Author:	dell

MiraBoxUser Guide –page1 / 27
MiraBox User Guide
-Sep18, 2012
Contents
A. Package contents .............................................................................................................................................. 2
B. MiraBox appearance and connecting ports................................................................................................... 4
C. LED indication .................................................................................................................................................... 6
D. System console and debugging ...................................................................................................................... 7
1.
Driver and tool installation..................................................................................................................................... 7
2.
Go into debugging console. ................................................................................................................................ 10
3.
WiFi AP mode testing......................................................................................................................................... 11
4.
WIFI Client mode testing .................................................................................................................................... 13
5.
Gigabit ethernet ports......................................................................................................................................... 16
6.
USB 3.0 port ..................................................................................................................................................... 17
7.
Multi-IO port ...................................................................................................................................................... 18
8.
Reset................................................................................................................................................................ 26
9.
Download sites .................................................................................................................................................. 27
10.
FCC STATEMENT......................................................................................................................................... 27
11.
RF warning statement: ................................................................................................................................... 27
MiraBoxUser Guide –page2 / 27
A. Package contents
1． Standard package contents
MiraBoxstandard content List
Remark
MiraBox
1 unit
Mirabox main unit
AC-DC Power Adapter
1 pc
Input 90-240VAC / output 5V,3A DC
Ethernet Cable
1 pc
Cat 5e
USB3.0 Cable
1 pc
Mini-USB Cable
1 pc
Quick reference card
1 pc
Warranty card
1 pc
For debug console use
MiraBoxUser Guide –page3 / 27
2. Optional package contents
MiraBoxOptional Content List
Multi I/O Cable
1 pc
Connect from MiraBox to JTAG/GPIO box
GPIO Cable
1 pc
For GPIO port connection
MiraBox JTAG/GPIO box
1 pc
External JTAG/GPIO box for debugging
MiraBoxUser Guide –page4 / 27
B. MiraBox appearance and connecting ports
MiraBoxUser Guide –page5 / 27
Mirabox ports description
Connection port
Description
Remark
Power Port
DC 5V/3A port
RJ45 #1
Gigabit Ethernet port1
RJ45 #2
Gigabit Ethernet port2
USB 3.0 port#1
USB 3.0 high speed host
USB 3.0 port#2
USB 3.0 high speed host
Mini USB console port
Debug console
Connect to PC USB port
Multi-I/O port
JTAG and GPIO port
Connect to external JTAG/GPIO box for system
development.
Micro SD slot
External Micro-SD slot
Reset button hole
System reset button
Reset through GPIO
MiraBoxUser Guide –page6 / 27
C. LED indication
LED indication table
LED
Color/ Pattern
Description
Power on LED
Solid green
Upon power on, this LED lights up
WiFi AP
Blinking blue
Indicate WiFi AP mode is activated as default after boot up
Off
WiFi AP mode is not activated
Blinking green
WiFi client mode is activated
Off
WiFi client mode is not activated
WiFi client
MiraBoxUser Guide –page7 / 27
D. System console and debugging
1. Driver and tool installation.
(1) Prepare one Windows PC
(2) Download the serial communication tool “putty.exe”.
(3) Downloadthe driver “2KXPVDock.exe”forProlific-USB-to-Serial-Comm-Portat our Website.
http://www.globalscaletechnologies.com/t-downloads.aspx
(4) Install driver on your PC (only for the first time)
(4-1) Connect Mirabox to your Windows PC
Connect Mini USB cable here.The other end
connects to computer’s USB port.
(4-2) The first time when you connect Mirabox to the Windows computer you will be asked to install the driver
MiraBoxUser Guide –page8 / 27
(4-3) Run file “2KXPVDock.exe”and the driver will be installed to the PATH C:\cabs\2KXPVDock”.
Click “Next” to complete t
(5) Find out the com port of your debugger on your windows PC.
(5-1) Right click [My Computer]  [Properties]  [Hardware]  [Device Manager]
MiraBoxUser Guide –page9 / 27
(5-2) Find out your com port as below (here is com3 for example)
(6) Run “putty.exe”and configure as below on yourWindows PC.
The “Serial line” should be
configured the same as the
COM port in Device Manager
Give it a name and save for
easy execution next time
Click
open
MiraBoxUser Guide –page10 / 27
2. Go into debugging console.
(1) Power on the MiraBoxand you will see messages on screen as below
(2) You can press any key to stop auto-boot when you see the bootdelay timer is counting down.
After entering the uboot prompt, you can also change the uboot environment variables such
asbootdelaytime, Ipaddr,serverip and so on.
(3) If no key was pressed to interrupt the uboot, it will continue running to the login screen where urges you to
input the login name and password, here is the default login information.
Login :root
Password: nosoup4u
MiraBoxUser Guide –page11 / 27
(4) Now you are the root user and have the full control of the mirabox
3. WiFi AP mode testing
MiraBoxServer has a built-in WiFi module which is in compliance with 802.11 b/g/n standard. The WiFican work
as client or AP modebut only one at a time. The default mode is AP modeevery time when it powers on, and the
indication light D6 is blinking blue.
Here are steps for testing:
(1) Enter command and you will see message for uap0 device.
#ifconfig
(2) Prepare one computer installed with Wi-Fi Lan card, here we use computer with Windows XP operating system
for example.
(3) Go to “Network Connections”as shown below..
1. Select “Local Area connection 4”
MiraBoxUser Guide –page12 / 27
2. Select “View Available Wireless Networks”
3. Choose name with “mira-uAP-6344”, here digits”6344” is the last
four digits of MAC address for the MiraBoxWiFi
Then click “Connect”.
4. Successfully connected.
MiraBoxUser Guide –page13 / 27
4. WIFI Client mode testing
(1) Switchto WiFiclient mode by giving command as following.
# wlan.sh
When done successfully, the LED(D7) is blinking green and mlan0 is activated.
(2) To check mlan0 with ifconfig command
# ifconfig
MiraBoxUser Guide –page14 / 27
(3) Scan for WiFi AP near-by
# iwlist mlan0 scan
MiraBoxUser Guide –page15 / 27
(4) Connect to WiFi AP
# iwconfig mlan0 essid
# dhclient mlan0
# ifconfig mlan0
#ping 192.168.1.1
The below screenshot is a example for how to connect a mlan device. If you can see IP address (for example:
192.168.1.102) means you have already connected and got an IP.
(5) Switch back to WiFi AP mode
There are two useful script files:
Client_ap.sh – switch from wifi client mode to wifi AP mode
Wlan.sh – switch from wifi AP mode to wifi client mode
MiraBoxUser Guide –page16 / 27
5. Gigabit ethernet ports
(1) Connect the two Gigabit Ethernet ports to Gigabit switch by Network cables. Normally it will get an IP address
assigned by DHCP.
Enter command as below to check:
#ifconfig
(2) Testing the speed of Gigabit Ethernet ports
#ethtool eth0
Normally you will see the information as below:
MiraBoxUser Guide –page17 / 27
6. USB 3.0 port
(1) Plug in the usb3.0 hard disk or flash disk to the USB port then you can see some driver messages as below
of this device
(2) View the usb3.0 hard disk
#fdisk-l
you will see below messages of the usb3.0 devicewhich is usually shown as /dev/sdb*、/dev/sdc*.
(3) Testing the access speed of the usb3.0 ports
#hdparm-t /dev/sdc1
MiraBoxUser Guide –page18 / 27
7. Multi-IO port
Connect the MIRABOX JTAG/GPIO box to the Multi-IO port via Multi-IO cable.
Multi‐I/O port
Multi‐I/O Cable
MiraBox JTAG/GPIO box
(1) JTAG interface
Please connect the debugger to the 20‐pin JTAG slot as shown below, here we use the Marvell
BlackStone debugger and XDB(Marvell eXtreme Debugger 5.1) software on Windows PC for
example.
MiraBoxUser Guide –page19 / 27
Debugger connection
Marvell
BlackStone
debugger
MiraBox JTAG
GPIO
Run XDB on Windows PC
MiraBoxUser Guide –page20 / 27
(2) GPIO interface and control
(2-1) There is a demo program to show the GPIO LEDs by entering command as below:
#ledtest1
This will light up the LEDs for 3 seconds then light off.
（2-2）Control the LED by yourself
The other side is GPIO port 0
GPIO port 4
GPIO port 3
GPIO port 2
GPIO port 1
MiraBoxUser Guide –page21 / 27
a. preparation
1. Prepare a host pc with linux (as:fedora 14) installed, and download the cross tool chain
“arm-marvell-linux-gnueabi-vfp.tar.bz2” from our
websitehttp://www.plugcomputer.org/downloads/d2plug/ or
http://www.globalscaletechnologies.com or
2. Install and configure the tool chain
Copy “arm-marvell-linux-gnueabi-vfp.tar.bz2” to directory /opt
#cd /opt
#tar -jxfarm-marvell-linux-gnueabi-vfp.tar.bz2
#ls
#vim /root/.bashrc
Add “export PATH=$PATH:/opt/arm-marvell-linux-gnueabi-vfp/bin” to last line as below, then save and exit.
Enable the PATH
#source /root/.bash_profile
MiraBoxUser Guide –page22 / 27
b. compile the program
Here has an example “i2c_led.c” for you to debugging
/*i2c_led.c*GTI‐‐Globalscaletechnologies.,INC**/
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#define I2C_RETRIES 0x0701
#define I2C_TIMEOUT 0x0702
#define I2C_RDWR 0x0707
#define I2C_M_RD 0x0001
#define I2C_M_NOSTART
0x4000
/* if I2C_FUNC_PROTOCOL_MANGLING */
#define I2C_M_REV_DIR_ADDR 0x2000
/* if I2C_FUNC_PROTOCOL_MANGLING */
#define I2C_M_IGNORE_NAK 0x1000
/* if I2C_FUNC_PROTOCOL_MANGLING */
#define I2C_M_NO_RD_ACK
#define I2C_M_RECV_LEN
0x0800
/* if I2C_FUNC_PROTOCOL_MANGLING */
0x0400
/* length will be first received byte */
/*********define struct i2c_rdwr_ioctl_data and struct i2c_msg，they must be consistent to kernel*******/
struct i2c_msg
unsigned short addr;
unsigned short flags;
#define I2C_M_TEN 0x0010
unsigned short len;
unsigned char *buf;
};
struct i2c_rdwr_ioctl_data
struct i2c_msg *msgs;
intnmsgs;/* the nmsgs decide the num of start signal*/
};
/***********the main program***********/
int main()
intfd,ret;
MiraBoxUser Guide –page23 / 27
struct i2c_rdwr_ioctl_data e2prom_data;
fd=open("/dev/i2c‐0",O_RDWR);/*
/dev/i2c‐0 is registered to the system */
if(fd<0)
perror("open error");
e2prom_data.nmsgs=2;
e2prom_data.msgs=(struct i2c_msg*)malloc(e2prom_data.nmsgs*sizeof(struct i2c_msg));
if(!e2prom_data.msgs)
perror("malloc error");
exit(1);
ioctl(fd,I2C_TIMEOUT,1);/*timeout */
ioctl(fd,I2C_RETRIES,2);/*retries times*/
/***write data to e2prom**/
e2prom_data.nmsgs=1;
(e2prom_data.msgs[0]).len=2;
(e2prom_data.msgs[0]).addr=0x25;//e2prom device address
(e2prom_data.msgs[0]).flags=0; //write
(e2prom_data.msgs[0]).buf=(unsigned char*)malloc(2);
/***********
control the GPIO OP‐0 **************************************/
(e2prom_data.msgs[0]).buf[0]=0x18;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0x0;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error2");
/***********
control the GPIO OP‐1 **************************************/
(e2prom_data.msgs[0]).buf[0]=0x19;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0x0;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error2");
MiraBoxUser Guide –page24 / 27
/*********** control the GPIO OP‐2 **************************************/
//turn on LED
(e2prom_data.msgs[0]).buf[0]=0x1a;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0x0;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error3");
//turn off LED
sleep(1);
//delay 1 second
(e2prom_data.msgs[0]).buf[0]=0x1a;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0xFF;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error3");
/*********** control the GPIO OP‐3 **************************************/
//turn on LED
sleep(1);
(e2prom_data.msgs[0]).buf[0]=0x1b;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0x0;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error4");
//turn off LED
sleep(1);
(e2prom_data.msgs[0]).buf[0]=0x1b;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0xFF;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error4");
MiraBoxUser Guide –page25 / 27
/*********** control the GPIO OP‐4 **************************************/
//turn on LED
sleep(1);
(e2prom_data.msgs[0]).buf[0]=0x1c;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0x0;//the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error5");
//turn off LED
sleep(1);
(e2prom_data.msgs[0]).buf[0]=0x1c;// e2prom write address
(e2prom_data.msgs[0]).buf[1]=0xFF;// the data to write
ret=ioctl(fd,I2C_RDWR,(unsigned long)&e2prom_data);
if(ret<0)
perror("ioctl error5");
printf("testing ok\n");
close(fd);
return 0;
Copy this program to file “i2c_led.c” and save to “/home” directory or other else, and compile it use
cross-compile tool just have been installed.
#cd /home
#arm-marvell-linux-gnueabi-gcc -o led i2c_led.c
Then copy the executable file “led” to Mirabox and run it. You can see the LED is controlled by youself.
MiraBoxUser Guide –page26 / 27
8. Reset
6、GPIO reset button hole.
(1) GPIO reset button
The reset button is connected to one GPIO which means controlled by software.
When you press down this button by using a sharp pin, it arouses attention of CPU then CPU asserts the master
reset low signal to start the system reset session.
Below is the reboot screen after reset
Note: Since this reset function is controlled by software so it will not be handled during boot-up session.
(2) More push button functions
System developer can program this button to have more functions by different press-then-release delay time.
MiraBoxUser Guide –page27 / 27
9.
Download sites
To download the files for MiraBox server, please visit:
http://www.globalscaletechnologies.com/t-downloads.aspx
Other useful resource links are:
http://www.plugcomputer.org/
http://plugcomputer.org/plugwiki/index.php/GuruPlug
10. FCC STATEMENT
1. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference.
(2) This device must accept any interference received, including interference that may cause undesired
operation.
2. Changes or modifications not expressly approved by the party responsible for compliance could void the user's
authority to operate the equipment.
NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to
Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in
a residential installation.
This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance
with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that
interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or
television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to
correct the interference by one or more of the following measures:
--- Reorient or relocate the receiving antenna.
--- Increase the separation between the equipment and receiver.
--- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
--- Consult the dealer or an experienced radio/TV technician for help.
11. RF warning statement:
This equipment complies with FCC radiation exposure limits setforth for an uncontrolled
environment. This equipment should be installed and operated with minimum distance 20cm
between theradiator & your body

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : Yes
Author                          : dell
Create Date                     : 2013:03:06 10:40:41+08:00
Modify Date                     : 2013:03:07 15:12:18+08:00
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:08:04
Creator Tool                    : PScript5.dll Version 5.2.2
Metadata Date                   : 2013:03:07 15:12:18+08:00
Format                          : application/pdf
Title                           : Microsoft Word - Mirabox User Guide_US_v1-Sep-20-2012-Tony_pm 20.40_.docx
Creator                         : dell
Producer                        : Acrobat Distiller 9.0.0 (Windows)
Document ID                     : uuid:b6d6ee48-f7ef-4412-9e51-55549bc7de37
Instance ID                     : uuid:aba080ad-766b-489e-a33b-90b7bbe3b54a
Page Count                      : 27

EXIF Metadata provided by EXIF.tools