1. Platforms supported

Below is a table showing the platforms supported. In order to manage slight differences between platforms, a PLATFORM flag has been introduced.

Platform	Composite PLATFORM flag	Maintained	Quick start guide doc
NuMaker-PFM-M2351	`PLATFORM=numaker_pfm_m2351`	v0.1	./numaker_pfm_m2351.md "numaker_pfm_m2351.md"

2. Get and build the solution

Below we will describe the general way of getting the source, building the solution and how to run test on the device. For device specific instructions, see the respective [platform].md file in the docs folder.

2.1 Prerequisites

We believe that you can use any Linux distribution to build mTower, but as maintainers of mTower we are mainly using Ubuntu-based distributions and to be able to build and run mTower there are a few packages that must be installed to start with. Therefore install the following packages regardless of what target you will use in the end.

$ sudo apt-get install git gcc make gperf flex \
                    bison libncurses5-dev texinfo g++ curl pkg-config \ 
                    autoconf libtool libtool-bin libc6:i386 \
                    libc6-dev:i386 gcc-multilib doxygen doxygen-gui

2.2 Building kconfig-frontends in Linux (optional)

Preparing kconfig-frontends for Linux is a fast and simple process, similar (if not identical) to preparation of any software using autotools. Typically the whole process will require you to only download the source tarball, extract it somewhere and run ./configure && make && sudo make install in extracted folder.

2.2.1 Download and extract the source tarball

$ curl -O http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz
$ tar -xf kconfig-frontends-3.12.0.0.tar.xz
$ cd kconfig-frontends-3.12.0.0

2.2.2 Patch

If your system has gperf 3.0.4 or earlier, you may safely skip this chapter.

gperf 3.1 (released on 5th January of 2017) changed the type used as length argument in generated functions from unsigned int to size_t. This will cause your build to fail with following error message:

  CC     libkconfig_parser_la-yconf.lo
In file included from yconf.c:234:0:
hconf.gperf:141:1: error: conflicting types for 'kconf_id_lookup'
hconf.gperf:12:31: note: previous declaration of 'kconf_id_lookup' was here
 static const struct kconf_id *kconf_id_lookup(register const char *str, register unsigned int len);
                               ^~~~~~~~~~~~~~~
make[3]: *** [Makefile:456: libkconfig_parser_la-yconf.lo] Error 1
make[2]: *** [Makefile:350: all] Error 2
make[1]: *** [Makefile:334: all-recursive] Error 1
make: *** [Makefile:385: all-recursive] Error 1

The procedure to fix is below:

$ curl -O https://gist.githubusercontent.com/KamilSzczygiel/d16a5d88075939578f7bd8fadd0907aa/raw/1928495cfb6a6141365d545a23d66203222d28c0/kconfig-frontends.patch
$ patch -p1 -i kconfig-frontends.patch
$ autoreconf -fi

2.2.4 Configure

The recommended set of options to configure kconfig-frontends for use with distortos would be:

$ ./configure --enable-conf --enable-mconf --disable-shared --enable-static

2.2.5 Compile and install

$ make
$ sudo make install
# sudo strip /usr/local/bin/kconfig-*
cd <mTower_PATH>

Full description How to install kconfig-frontends

2.3 Get the source code

$ git clone https://github.com/Samsung/mTower.git

Choose the PLATFORM corresponding to the platform you intend to use. For example, if you intend to use NuMaker-PFM-M2351, then PLATFORM should be numaker_pfm_m2351. After that, generate context using default configuration options.

$ cd mTower/

$ make PLATFORM=numaker_pfm_m2351 create_context

2.4 Get the toolchains

In mTower different toolchains are used for different targets (depends on architecture 32-bit solutions). In any case start by downloading the toolchains by:

$ make toolchain

2.5 Build the solution

We've configured default .config and Make.defs for each platforms, so that configuration will always automatically to the correct device specific make, that means that you simply start the build by running:

$ make

2.6 Flash the device

This is device specific.

2.7 Boot up the device

This is device specific.