...
Freescale makes their i.MX series official bsp build scripts available via the following GIT repository:
Info | ||
---|---|---|
| ||
git://git.freescale.com/imx/meta-fsl-bsp-release |
Info | ||
---|---|---|
| ||
git://git.yoctoproject freescale.org com/meta- imx/fsl-arm-yocto-bsp.git |
It is this repository that actually pulls in the fsl-bsp-release project to perform the Linux BSP builds for Freescale's i.MX6 ARM Cortext-A9 chips.
Generating SSH Keys
We recommend you use SSH keys to establish a secure connection between your computer and Embedian Gitlab server. The steps below will walk you through generating an SSH key and then adding the public key to our Gitlab account.
Step 1. Check for SSH keys
First, we need to check for existing ssh keys on your computer. Open up Git Bash and run:
Code Block | ||||
---|---|---|---|---|
| ||||
$ cd ~/.ssh $ ls # Lists the files in your .ssh directory |
Check the directory listing to see if you have a file named either id_rsa.pub
or id_dsa.pub
. If you don't have either of those files go to step 2. Otherwise, you already have an existing keypair, and you can skip to step 3.
Step 2. Generate a new SSH key
To generate a new SSH key, enter the code below. We want the default settings so when asked to enter a file in which to save the key, just press enter.
Code Block | ||||
---|---|---|---|---|
| ||||
$ ssh-keygen -t rsa -C "your_email@example.com" # Creates a new ssh key, using the provided email as a label # Generating public/private rsa key pair. # Enter file in which to save the key (/c/Users/you/.ssh/id_rsa): [Press enter] $ ssh-add id_rsa |
Now you need to enter a passphrase.
Code Block | ||||
---|---|---|---|---|
| ||||
Enter passphrase (empty for no passphrase): [Type a passphrase] Enter same passphrase again: [Type passphrase again] |
Which should give you something like this:
Code Block | ||||
---|---|---|---|---|
| ||||
Your identification has been saved in /c/Users/you/.ssh/id_rsa. Your public key has been saved in /c/Users/you/.ssh/id_rsa.pub. The key fingerprint is: 01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db your_email@example.com |
Step 3. Add your SSH key to Embedian Gitlab Server
Copy the key to your clipboard.
Code Block | ||||
---|---|---|---|---|
| ||||
$ cat ~/.ssh/id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAABDAQABAAABAQDQUEnh8uGpfxaZVU6+uE4bsDrs/tEE5/BPW7jMAxak 6qgOh6nUrQGBWS+VxMM2un3KzwvLRJSj8G4TnTK2CSmlBvR+X8ZeXNTyAdaDxULs/StVhH+QRtFEGy4o iMIzvIlTyORY89jzhIsgZzwr01nqoSeWWASd+59JWtFjVy0nwVNVtbek7NfuIGGAPaijO5Wnshr2uChB Pk8ScGjQ3z4VqNXP6CWhCXTqIk7EQl7yX2GKd6FgEFrzae+5Jf63Xm8g6abbE3ytCrMT/jYy5OOj2XSg 6jlxSFnKcONAcfMTWkTXeG/OgeGeG5kZdtqryRtOlGmOeuQe1dd3I+Zz3JyT your_email@example.c om |
Go to Embedian Git Server. At Profile Setting --> SSH Keys --> Add SSH Key
Paste your public key and press "Add Key" and your are done.
Overview of the meta-emb-smarc Yocto Layer
The supplied meta-emb-smarc Yocto compliant layer has the following organization:
Info | ||
---|---|---|
| ||
|
Notes on meta-emb-smarc layer content
conf/machine/*
This folder contains the machine definitions for the imx6solosmarc|imx6u1gsmarc|imx6q1gsmarc|imx6q2gsmarc platform and backup repository in Embedian. These select the associated kernel, kernel config, u-boot, u-boot config, and tar.gz image settings.
recipes-bsp/u-boot/*
This folder contains recipes used to build DAS U-boot for imx6solosmarc|imx6u1gsmarc|imx6q1gsmarc|imx6q2gsmarc platform.
recipes-connectivity/ifplugdlftp/*
This folder adds ifplugd daemon to detect Ethernet cable re-connection lftp ftp client for imx6solosmarc|imx6u1gsmarc|imx6q1gsmarc|imx6q2gsmarc platform.
recipes-fsl/images/*
These recipes are used to create the final target images for the devices. When you run Bitbake one of these recipes would be specified. For example, to build the root file system for the imx6q1gsmarc platform:
Info | ||
---|---|---|
| ||
MACHINE=imx6q1gsmarc bitbake -k imx6q1gsmarc-fsl-image-qt5 |
recipes-core/init-ifupdown*
This recipe is used to amend device network interfaces
recipes-core/init-sysvinit*
This recipe is used to amend device console interfaces
recipes-devtools/nodejs/*
These recipes build the Node.js Javascript server execution environment.
recipes-kernel/linux/*
Contains the recipes needed to build the imx6solosmarc|imx6u1gsmarc|imx6q1gsmarc|imx6q2gsmarc Linux kernels.
recipes-support/boost/*
Adds Boost to the images. Boost provides various C++ libraries that encourage cross-platform development.
recipes-support/ntp/*
Network time protocol support.
Setting Up the Tools and Build Environment
To build the latest Freescale i.MX6 fsl-bsp-release, you first need an Unbuntu Linux 12.04LTS or Ubuntu 14.04LTS installation. Since bitbake does not accept building images using root privileges, please do not login as a root user when performing the instructions in this section.
Once you have Ubuntu 12.04 LTS or Ubuntu 14.04LTS running, install the additional required support packages using the following console command:
Info | ||
---|---|---|
| ||
|
If you are using a 64-bit Linux, then you'd also need to install 32-bit support libraries, needed by the pre-built Linaro toolchain and other binary tools.
Info | ||
---|---|---|
| ||
$ sudo dpkg --add-architecture i386 |
Note |
---|
If you saw error like the following after running "sudo dpkg --add-architecture i386"
make sure the only file present in /etc/dpkg/dpkg.cfg.d/ is "multiarch"
if output is
execute the following commands as it is else replace "multiarch" with the name of file present in that directory.
The above command will add i386 architecture. |
You’ll also need to change the default shell to bash from Ubuntu’s default dash shell (select the <No> option):
Info | ||
---|---|---|
| ||
|
To get the BSP you need to have 'repo' installed and use it as:
Install the 'repo' utility:
Info | ||
---|---|---|
| ||
|
Info | ||
---|---|---|
| ||
|
Info | ||
---|---|---|
| ||
$ wget ftp://ftp.embedian.com/public/dev/minfs/emb smarc-fsl fimx6-bsp-release/emb- fsl-smarcfimx6-fido-setup-release.shemb- fsl-smarfimx6-fido-setup-release.shcd cd sourcesemb- fsl-smarcfimx6-fido-setup-release.sh -b imx6q1g-build-qt5fb -efb fb |
Note | ||
---|---|---|
| ||
The last line of the above script $ MACHINE= <machine name> source emb-setup-release.sh <build directory> -e <fb/x11/dfb>
The default console debug port is SER3. In this document, we will use imx6q1gsmarc as the example of machine name. Users need to change different machine name if you have different SMARC card variants. |
To build Embedian/Freescale Yocto BSP, use the following commands:
Info | ||
---|---|---|
| ||
|
Note | ||
---|---|---|
| ||
imx6q1gsmarc-fsl-image-gui provides a gui image without QT5. imx6q1gsmarc-fsl-image-qt5 provides a Qt5 image for X11 and FB backends. If your machine name is imx6u1gsmarc and your gui image is without QT5 ,the following command gives you as an example. The first build takes time. |
Once it done, you can find all required images under ~/smarc-fsl-bsp-release/<build directory>/tmp/deploy/images/<machine name>/
You may want to build programs that aren’t installed into a root file system so you can make them available via a feed site (described below.) To do this you can build the package directly and then build the package named package-index to add the new package to the feed site.
The following example builds the minicom program and makes it available on the feed site:
Info | ||
---|---|---|
| ||
|
~/smarc-fsl-bsp-release/<build directory>/tmp/deploy
.deploy/images/<machine name>/*
This folder contains the binary images for the root file system and the Embedian SMARC-FiMX6 specific version of the u-boot, zImage and device tree file. Specifically the images are:
deploy/images/<machine name>/u-boot.binimx
This u-boot bootloader binary for SMARC-FiMX6
deploy/images/<machine name>/zImage
The kernel zImage for SMARC-FiMX6.
deploy/images/<machine name>/zImage-imx6q-smarcfimx6.dtb
The device tree binary file for SMARC-FiMX6 Dual and Quad core.
deploy/images/<machine name>/zImage-imx6dl-smarcfimx6.dtb
The device tree binary file for SMARC-FiMX6 Solo and Dual Lite core.
deploy/images/<machine name>/imx6u1gsmarc-fsl-image-gui-imx6u1gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual Lite core platforms without QT5.
deploy/images/<machine name>/imx6u1gsmarc-fsl-image-qt5-imx6u1gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual Lite core platforms with QT5.
deploy/images/<machine name>/imx6q1gsmarc-fsl-image-gui-imx6q1gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual and Quad core platforms without QT5.
deploy/images/<machine name>/imx6q1gsmarc-fsl-image-qt5-imx6q1gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual and Quad core platforms with QT5.
deploy/images/<machine name>/imx6solosmarc-fsl-image-gui-imx6solosmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Solo core platforms without QT5.
deploy/images/<machine name>/imx6solosmarc-fsl-image-qt5-imx6solosmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Solo core platforms with QT5.
deploy/images/<machine name>/imx6q2gsmarc-fsl-image-gui-imx6q2gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual and Quad core platforms and 2GB DDR3 without QT5.
deploy/images/<machine name>/imx6q2gsmarc-fsl-image-qt5-imx6q2gsmarc.*
Embedian root file system images for software development on Embedian’s SMARC-FiMX6 Dual and Quad core platforms and 2GB DDR3 with QT5.
deploy/rpm/*
This folder contains all the packages used to construct the root file system images. They are in rpm format (similar format to Fedora packages) and can be dynamically installed on the target platform via a properly constructed feed file. Here is an example of the feed file (named imx6q1g_qt5fb_update.repo) that is used internally at Embedian to install upgrades onto a imx6q1gsmarc QT5 platform directly on framebuffer without reflashing the file system:
Info | ||
---|---|---|
| ||
[all] |
deploy/licenses/*
Setup SD Card
For these instruction, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.
Info | ||
---|---|---|
| ||
$ export DISK=/dev/mmcblk0 |
Erase SD card:
Info | ||
---|---|---|
| ||
$ |
Create Partition Layout:
With util-linux v2.26, sfdisk was rewritten and is now based on libfdisk.
Info | ||||
---|---|---|---|---|
| ||||
$ sudo sfdisk --version sfdisk from util-linux 2.27.1 |
Create Partitions:
Info | ||
---|---|---|
| ||
$ sudo sfdisk ${DISK} <<-__EOF__ |
Info | ||
---|---|---|
| ||
$ sudo sfdisk --in-order --Linux --unit M ${DISK} <<-__EOF__ |
Format Partitions:
Info | ||
---|---|---|
| ||
for : DISK=/dev/mmcblk0 $ sudo mkfs.vfat -F 16 ${DISK}p1 -n boot $ sudo mkfs.ext4 ${DISK}p2 -L rootfs for : DISK=/dev/sdX $ sudo mkfs.vfat -F 16 ${DISK} 1 -n boot $ sudo mkfs.ext4 ${DISK} 2 -L rootfs |
Mount Partitions:
On some systems, these partitions may be auto-mounted...
Info | ||
---|---|---|
| ||
$ sudo mkdir -p /media/boot/ $ sudo mkdir -p /media/rootfs/ for : DISK=/dev/mmcblk0 $ sudo mount ${DISK}p1 /media/boot/ $ sudo mount ${DISK}p2 /media/rootfs/ for : DISK=/dev/sdX $ sudo mount ${DISK} 1 /media/boot/ $ sudo mount ${DISK} 2 /media/rootfs/ |
Install Bootloader
CopyIf SPI NOR Flash is not empty
The u-boot.
bin to the boot partitionimx is pre-installed in SPI NOR flash at factory default. SMARC-FiMX6 is designed to always boot up from SPI NOR flash and to load zImage, device tree blob and root file systems based on the setting of BOOT_SEL. If users need to fuse their own u-boot or perform u-boot upgrade. This section will instruct you how to do that.
Copy u-boot.imx to the boot partition.
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v u-boot.binimx /media/boot/u-boot.imx |
Fuse u-boot.imx to the SPI NOR flash.
Stop at U-Boot command prompt (Press any key when booting up). Copy and Paste the following script under u-boot command prompt.
Info | ||||
---|---|---|---|---|
| ||||
U-Boot# mmc rescan; mmc dev; load mmc 0:1 0x10800000 u-boot.imx; sf probe; sleep 2; sf erase 0 0xc0000; sf write 0x10800000 0x400 80000 |
If SPI NOR Flash is empty
In some cases, when SPI NOR flash is erased or the u-boot is under development, we need a way to boot from SD card first. Users need to shunt cross the TEST# pin to ground. In this way, SMARC-FiMX6 will always boot up from SD card.
Copy u-boot.imx to the boot partition
Info | ||||
---|---|---|---|---|
| ||||
$ sudo dd if=u-boot.imx of=${DISK} bs=512 seek=2 |
Note |
---|
|
uEnv.txt based bootscript
Create "uEnv.txt" boot script: ($ vim uEnv.txt)
Info | ||||
---|---|---|---|---|
| ||||
#####HDMI###### 400M"24 M 24M vmalloc=400M" console=ttymxc4,115200 |
Copy uEnv.txt to the boot partition:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v ~/uEnv.txt /media/boot/ |
Install Kernel zImage
Copy zImage to the boot partition:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v zImage /media/boot |
Install Kernel Device Tree Binary
Info | ||||
---|---|---|---|---|
| ||||
$ sudo mkdir -p /media/boot/dtbs $ sudo cp -v zImage-imx6q-smarcfimx6.dtb /media/boot/dtbs/imx6q-smarcfimx6.dtb $ sudo cp -v zImage-imx6dl-smarcfimx6.dtb /media/boot/dtbs/imx6dl-smarcfimx6.dtb |
Note | ||
---|---|---|
| ||
For WVGA (800x480) LVDS panel: For XGA (1024x768) LVDS panel: For WXGA (1366x768) LVDS panel: For 1080p (1920x1080) LVDS panel: |
Install Root File System
Copy Root File System:
Yocto Built Rootfs:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo tar xvfz <filename.tar.gz> -C /media/rootfs |
Note | ||
---|---|---|
| ||
|
Remove SD card:
Info | ||
---|---|---|
| ||
$ sync $ sudo umount /media/boot $ sudo umount /media/rootfs |
Feed Packages
The following procedure can be used on a Embedian SMARC-FiMX6 device to download and utilize the feed file show above to install the tcpdump Ethernet packet analyzer program:
Info | ||
---|---|---|
| ||
$ smart channel -y --add http://www.embedian.com/smarcfimx6-feed/imx6q1g_qt5fb_update.repo $ smart update $ smart install tcpdump |
Writing Bitbake Recipes
In order to package your application and include it in the root filesystem image, you must write a BitBake recipe for it.
When starting from scratch, it is easiest to learn by example from existing recipes.
Example HelloWorld recipe using autotools
For software that uses autotools (./configure; make; make install), writing recipes can be very simple:
DESCRIPTION = "Hello World Recipe using autotools" HOMEPAGE = "http://www.embedian.com/" SECTION = "console/utils" PRIORITY = "optional" LICENSE = "GPL" PR = "r0" SRC_URI = "git://git@git.embedian.com/developer/helloworld-autotools.git;protocol=ssh;tag=v1.0" S = "${WORKDIR}/git" inherit autotools |
SRC_URI
specifies the location to download the source from. It can take the form of any standard URL using http://, ftp://, etc. It can also fetch from SCM systems, such as git in the example above.
PR
is the package revision variable. Any time a recipe is updated that should require the package to be rebuilt, this variable should be incremented.
inherit autotools
brings in support for the package to be built using autotools, and thus no other instructions on how to compile and install the software are needed unless something needs to be customized.
S
is the source directory variable. This specifies where the source code will exist after it is fetched from SRC_URI and unpacked. The default value is ${WORKDIR}/${PN}-${PV}
, where PN
is the package name and PV
is the package version. Both PN
and PV
are set by default using the filename of the recipe, where the filename has the format PN_PV.bb
.
Example HelloWorld recipe using a single source file
This example shows a simple case of building a helloworld.c file directly using the default compiler (gcc). Since it isn’t using autotools or make, we have to tell BitBake how to build it explicitly.
DESCRIPTION = "HelloWorld" SECTION = "examples" LICENSE = "GPL" SRC_URI = "file://helloworld.c" S = "${WORKDIR}" do_compile() { ${CC} ${CFLAGS} ${LDFLAGS} helloworld.c -o helloworld } do_install() { install -d ${D}${bindir} install -m 0755 helloworld ${D}${bindir} } |
In this case, SRC_URI
specifies a file that must exist locally with the recipe. Since there is no code to download and unpack, we set S
to WORKDIR
since that is where helloworld.c will be copied to before it is built.
WORKDIR
is located at ${OETREE}/<build directory>/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/<package name and version>
for most packages. If the package is machine-specific (rather than generic for the cortexa9hf architecture), it may be located in the imx6q1gsmarc-poky-linux-gnueabi subdirectory depending on your hardware (this applies to kernel packages, images, etc).
do_compile
defines how to compile the source. In this case, we just call gcc directly. If it isn’t defined, do_compile
runs make
in the source directory by default.
do_install
defines how to install the application. This example runs install
to create a bin directory where the application will be copied to and then copies the application there with permissions set to 755.
D
is the destination directory where the application is installed to before it is packaged.
${bindir}
is the directory where most binary applications are installed, typically /usr/bin
.
For a more in-depth explanation of BitBake recipes, syntax, and variables, see the Recipe Chapter of the OpenEmbedded User Manual.
Setup eMMC
Setting up eMMC usually is the last step at development stage after the development work is done at your SD card or NFS environments. From software point of view, eMMC is nothing but a non-removable SD card on board. For SMARC-FiMX6, the SD card is always emulated as /dev/mmcblk1 and on-module eMMC is always emulated as /dev/mmcblk3. Setting up eMMC now is nothing but changing the device descriptor.
This section gives a step-by-step procedure to setup eMMC flash. Users can write a shell script your own at production to simplify the steps.
First, we need to backup the final firmware from your SD card or NFS.
Prepare for eMMC binaries from SD card (or NFS):
Insert SD card into your Linux PC. For these instructions, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.
For these instruction, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.
Info | ||
---|---|---|
| ||
$ export DISK=/dev/mmcblk0 |
Mount Partitions:
On some systems, these partitions may be auto-mounted...
Info | ||
---|---|---|
| ||
$ sudo mkdir -p /media/boot/ $ sudo mkdir -p /media/rootfs/ for : DISK=/dev/mmcblk0 $ sudo mount ${DISK}p1 /media/boot/ $ sudo mount ${DISK}p2 /media/rootfs/ for : DISK=/dev/sdX $ sudo mount ${DISK} 1 /media/boot/ $ sudo mount ${DISK} 2 /media/rootfs/ |
Changing Device descriptor from U-Boot:
There is only one line needed to be changed from original u-boot.
At include/configs/smarcfimx6.h, find
#define CONFIG_SYS_MMC_ENV_DEV
Change from "0" to "2" and make again.
(Users can also modify Yocto meta layer at sources/meta-emb-smarc/u-boot/u-boot-smarcfimx6_2014.04-smarcfimx6.bb, commit out the original SRCREV and SRCBRANCH and replace by the following.
# eMMC Boot Up
#SRCREV = "1fde73522a9617f04c5eb16b508dd70f193139bb"
#SRCBRANCH = "smarc-emmc-imx_v2014.04_3.14.28_1.0.0_ga"
)
The new u-boot.bin will be the one for eMMC use.
Copy u-boot.bin to rootfs partition:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v u-boot.bin /media/rootfs/home/root |
Copy zImage to rootfs partition:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v zImage /media/rootfs/home/root |
Copy uEnv.txt to rootfs partition:
Copy and paste the following contents to /media/rootfs/home/root ($ sudo vim /media/rootfs/home/root/uEnv.txt)
Info | ||
---|---|---|
| ||
#####HDMI###### 400M"24 M 24M vmalloc=400M" console=ttymxc4,115200 |
Copy device tree blob to rootfs partition:
Info | ||||
---|---|---|---|---|
| ||||
$ sudo cp -v zImage-mx6q-smarcfimx6.dtb /media/rootfs/home/root/imx6q-smarcfimx6.dtbdtb dtb |
Note | ||
---|---|---|
| ||
For WVGA (800x480) LVDS panel: For XGA (1024x768) LVDS panel: For WXGA (1366x768) LVDS panel: For 1080p (1920x1080) LVDS panel: |
Copy real rootfs to rootfs partition:
Info | ||
---|---|---|
| ||
$ pushd /media/rootfs $ sudo tar cvfz ~/smarcfimx6-emmc-rootfs.tar.gz . $ sudo mv ~/smarcfimx6-emmc-rootfs.tar.gz /media/rootfs/home/root $ popd |
Remove SD card:
Info | ||
---|---|---|
| ||
$ sync $ sudo umount /media/boot $ sudo umount /media/rootfs |
Copy Binaries to eMMC from SD card:
Insert this SD card into your SMARC-FiMX6 device.
Now it will be almost the same as you did when setup your SD card, but the eMMC device descriptor is /dev/mmcblk3 now.
Info | ||
---|---|---|
| ||
$ export DISK=/dev/mmcblk3 |
Erase SD card:
Info | ||
---|---|---|
| ||
$ |
Create Partition Layout:
Info | ||
---|---|---|
| ||
$ sudo sfdisk --in-order --Linux --unit M ${DISK} <<-__EOF__ 1 , 48 , 0x83 ,* ,,,- __EOF__ |
Format Partitions:
Info | ||
---|---|---|
| ||
$ sudo mkfs.vfat -F 16 ${DISK}p1 -n boot $ sudo mkfs.ext4 ${DISK}p2 -L rootfs |
Mount Partitions:
Info | ||
---|---|---|
| ||
$ sudo mkdir -p /media/boot/ $ sudo mkdir -p /media/rootfs/ $ sudo mount ${DISK}p1 /media/boot/ $ sudo mount ${DISK}p2 /media/rootfs/ |
Install binaries for partition 1
Copy u-boot.bin/ uEnv.txt/zImage/*.dtb to the boot partition
Info | ||
---|---|---|
| ||
$ sudo cp -v u-boot.bin zImage uEnv.txt /media/boot/ |
Install Kernel Device Tree Binary
Info | ||
---|---|---|
| ||
$ sudo mkdir -p /media/boot/dtbs $ sudo cp -v imx6q-smarcfimx6.dtb imx6dl-smarcfimx6.dtb /media/boot/dtbs |
Install Root File System
Info | ||
---|---|---|
| ||
$ sudo tar -zxvf smarcfimx6-emmc-rootfs.tar.gz -C /media/rootfs |
Unmount eMMC:
Info | ||
---|---|---|
| ||
$ sync $ sudo umount /media/boot $ sudo umount /media/rootfs |
Switch your Boot Select to eMMC and you will be able to boot up from eMMC now.
version 1.0a, 3/23/2015
Last updated 20152016-0604-1112