Getting Started

Download

Download CoreCDP 2.3.4 (1298)

CoreCDP 2.3.4 Release Notes

Pre-built Images

Installing the build system

First, extract the build system using tar.
Once extracted, installer scripts are included to easily install the needed prerequisites. The examples below shows installing on a Debian/Ubuntu system.
For prerequisite package information for other distributions, see the Prerequisites page.

# extract the build system
tar xzvf corecdp-2.3.3.tar.gz
cd corecdp-2.3.3
# install any needed packages
sudo ./multitech/contrib/install-deps/install-debian-ubuntu-deps.sh

Ubuntu Notes

/bin/sh must be linked to /bin/bash for the build process to be successful.  Ubuntu defaults to dash, which isn’t compatible with scripts that assume /bin/sh is bash.  This can result in build problems for some software.

To change your default shell to bash, run: sudo dpkg-reconfigure dash and select “No” when asked if dash should be installed as /bin/sh.

Note: Ubuntu releases up to 12.10 are supported (later versions will not work)

Build Procedure

To build the cross compilation toolchain and a sample kernel and filesystem image:

# cd to wherever you extracted the SDK
cd corecdp-2.3.3

# load environment script
source env-oe.sh

# edit conf/local.conf to your needs
#   set MACHINE to your default machine type
#     MACHINE="mtcdp" or MACHINE="mt100eocg"
#   enable/disable the INHERIT += "rm_work" option
#     (to save disk space or keep source code)

# build the image and everything needed to do so
bitbake corecdp-base-image

The corecdp-base-image bitbake recipe builds a kernel and a basic root filesystem which is the recommended starting point for creating your own custom image. See the other CoreCDP sample images located in multitech/recipes/images. To create your own image, see Creating a Custom Image.

The first time the build is started, bitbake will build all necessary tools and dependencies including the cross complier and any native tools that are needed for the build process (these run directly on your build machine).  Subsequent builds will only build what is necessary.

The initial build may take a few hours depending on your hardware. If you have more than 2 cores and lots of RAM, you can increase the BB_NUMBER_THREADS and PARALLEL_MAKE settings in conf/local.conf to speed up build time considerably.

The resulting images will be located in a directory named for the machine type they were built for. The following paths and filenames are for MACHINE=”mtcdp”:
corecdp-2.3.3/build/tmp/deploy/eglibc/images/mtcdp

Kernel image: uImage-mtcdp.bin
Root filesystem: corecdp-base-image-mtcdp.jffs2

Flashing the Device

The device may be flashed either by using the Multi-Tech-provided flashing procedure (upgrade on reboot) or by flashing from U-Boot via TFTP (requires debug serial console).
See NAND Flash Programming for full instructions.

Default Settings

The device should be accessible via SSH with the following defaults:
IP Address: 192.168.2.1
User: root
Password: root

ssh root@192.168.2.1