Filter results by

SDK Generation from Tizen RT Source Code

The SDKs used by the ARTIK IDE are created from Tizen RT source code and made available to the IDE through SDK Update. You can create your own custom SDK configuration (that is, choosing the modules you want included/excluded for build) that can be brought in the same way. There are two approaches you can use.

  • ARTIK IDE method using Tizen RT System Configuration utility – you would use this easy method to create a different version of an existing SDK.

  • Command Line method using – use this approach with source code from a branch of the Tizen RT you cloned from GitHub as shown here. You can also just use it with an SDK already loaded to the ARTIK IDE.

Creating New SDK

You create a new SDK by configuring and building it, then choosing it for a project. Pull up the MQTT Example article for a good companion procedure to try out.

Configure and build the SDK – ARTIK IDE method

Follow these steps.

  1. From the ARTIK IDE top menu, select
    Samsung ARTIK » Tizen RT System Configuration.

  2. From the provided configuration screen, select or un-select the desired features.

  3. Click Build.

Configure and build the SDK – command line method

Prerequisites. You'll first need to install a few dependencies. Use this command.

sudo apt-get install libncurses5-dev

General Usage. Before using this SDK tool, you will typically set up a Linux Development Environment as described in Advanced Concepts and get comfortable using the kconfig customization tool.

Once you are ready, you use the command line to generate the SDK. There are two forms: -s SOURCE -e IDE [options]
    to generate a new SDK -p SDK_PATH [options]
    to add a custom configuration to an existing SDK

SOURCE is the path of the Tizen RT source code
IDE is the path of the ARTIK IDE
SDK_PATH is the path of the existing SDK

and options are:
-b or --nconfig is the new configuration name (default: 'custom')
-t is the toolchain path (needed if not already in PATH)
-d or --description is a descriptive phrase for the configuration
-v or --nsdk is the new SDK name, not used if -p is specified (default: 'custom')
-a or --arch is the architecture of the board (default: A053)
-c or --sconfig is the start configuration (default: 'typical').

Procedure. Follow these steps.

  1. Go to the directory containing the tool.
    cd ~/ARTIK/tools/external-system-config

  2. Run -s SOURCE -e IDE [options]
    to start the program, which will launch the kconfig tool. For example, if you installed your IDE under ARTIK:

     ./ -s ~/ARTIK/SDK/A053/v1.2/source/tinyara -e ~/ARTIK

    If you wanted to additionally specify a description for the user:

     ./ -s ~/ARTIK/SDK/A053/v1.2/source/tinyara -e ~/ARTIK -d "this is a new SDK created by the command line tool"
  3. Make changes to the configuration as described in the Kconfig tools article.

  4. Save your changes to the default .config file as always, then exit.

  5. Wait for the program to build the new SDK.

Creating a new configuration in the existing SDK

To simply bring a new configuration into the existing SDK, the procedure is similar to that above, except that you'll use a different form of the command line: -p SDK_PATH [options]

For example:

./ -p ~/ARTIK/SDK/A053/v1.2 

Selecting Created SDK

Once you have created or updated an SDK, it will be available when starting a new project.

The image below shows an added SDK in the selector. The name defaults to 'custom' unless you changed it using the IDE utility or using the -b option when running

Be sure you restart the ARTIK IDE to see any added SDKs.

Last updated on: