NameLast modifiedSizeLicense

Parent Directory Parent Directory
text hwpack_linaro-lsk-vexpress_20130926-475_armhf_supported.manifest.txt 12-Jan-2018 10:03 581 open
application/x-tar hwpack_linaro-lsk-vexpress_20130926-475_armhf_supported.tar.gz 26-Feb-2018 17:17 25.8M open
other linaro-image-alip-genericarmv7a-20130925-103.manifest 12-Jan-2018 10:03 31.6K open
application/x-tar linaro-image-alip-genericarmv7a-20130925-103.rootfs.tar.gz 26-Feb-2018 17:17 43.6M open
text lsk-vexpress-openembedded_alip-armv7a-gcc-4.8_20130926-475.html 12-Jan-2018 10:03 3.5K open
other lsk-vexpress-openembedded_alip-armv7a-gcc-4.8_20130926-475.img.gz 26-Feb-2018 17:17 68.3M open
other lsk-vexpress-openembedded_alip-armv7a-gcc-4.8_20130926-475.img.gz.zsync 26-Feb-2018 17:17 19.5M open

Linaro Stable Kernel (LSK) 13.09 Release for Versatile Express (OpenEmbedded)

The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. It is produced to satisfy the requirements of Linaro members. The LSK focuses on quality and stability and is therefore a great basis for member products. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.

Linaro releases monthly binary images for the ARM Versatile Express including support for Cortex-A9, Cortex-A5, TC2 (big.LITTLE) CoreTiles and RTSM.

For support matters related to ARM hardware or firmware images downloaded from ARM sites, please contact ARM support

This release includes Linaro OpenEmbedded for both Versatile Express and Real-Time System Model (RTSM). The images are able to boot A5 (using U-Boot), A9 (ATAGS) and TC2 using UEFI. Sources are also made available so you can build your own images (see the ‘Building from Source’ tab).

About the TC2 Engineering Build

This release is based on the Linux v3.10.12 kernel. As a consequence, almost all of the patches in the ARM Landing Team tree have been rebased and refactored to account for the latest upstream content.

The TC2 CoreTile is the first example of a big.LITTLE system shipped by ARM and serves as a platform for development and test of big.LITTLE software. TC2 contains a tri-core Cortex-A7 cluster and a dual-core Cortex-A15 cluster linked using the CCI–400 coherent interconnect.

The release contains the big.LITTLE MP patchset developed by ARM. This patchset is hosted by Linaro and can be found in the linked git repository. These patches have been developed and rigorously tested in order to enable the ARM Versatile Express V2P-CA15_A7 CoreTile (TC2) to run in full MP mode. This functionality has been optimised for energy and performance bringing it close to the Cortex-A7 (LITTLE) in energy consumption with near Cortex-A15 (big) performance. The patchset also includes optimizations that provide a considerable performance uplift across a wide range of benchmarks. The functionality introduced by this patchset is stable and ready for use on other platforms. This release is the reference point for big.LITTLE MP functionality.

The patches in the big.LITTLE MP patchset are generic and applicable to big.LITTLE systems with minimal porting effort. To ease porting, the patches are also available as an isolated package located here. This package may be used directly by partners interested in porting the big.LITTLE MP scheduler functionality to their custom platform. Please contact ARM support in case of any queries related to this package.

Also provided is optional configurable kernel support for an implementation of ARM’s Power State Co-ordination Interface (PSCI). This support is disabled by default. To use PSCI support you will require secure firmware that is currently available to ARM licensees upon request to ARM. Please contact ARM support to get access to the firmware code.

Scheduler modifications to support big.LITTLE

The following patches make up the big.LITTLE MP patchset.

sched: implement usage tracking
sched: entity load-tracking load_avg_ratio
sched: Task placement for heterogeneous systems based on task load-tracking
sched: Forced task migration on heterogeneous systems
sched: Introduce priority-based task migration filter
ARM: Add HMP scheduling support for ARM architecture
ARM: sched: Use device-tree to provide fast/slow CPU list for HMP
ARM: sched: Setup SCHED_HMP domains
sched: Add ftrace events for entity load-tracking
sched: Add HMP task migration ftrace event
sched: SCHED_HMP multi-domain task migration control
sched: Enable HMP priority filter by default
ARM: sched: Avoid empty ‘slow’ HMP domain
sched: Only down migrate low priority tasks if allowed by affinity mask
sched: fix arch_get_fast_and_slow_cpus to get logical cpumask correctly
sched: Do not ignore grouped tasks during HMP forced migration.
sched: Ignore offline CPUs in HMP migration & load stats
ARM: Change load tracking scale using sysfs
ARM: Experimental Frequency-Invariant Load Scaling Patch
ARM: Fix build breakage when big.LITTLE.conf is not used.
sched: Basic global balancing support for HMP
sched: cfs.nr_running does not contain the intended metric
Revert sched: Enable HMP priority filter by default
HMP: Use unweighted load for hmp migration decisions
HMP: Select least-loaded CPU when performing HMP Migrations
HMP: Avoid multiple calls to hmp_domain_min_load in fast path
HMP: Force new non-kernel tasks onto big CPUs until load stabilises
sched: Restrict nohz balance kicks to stay in the HMP domain
HMP: experimental: Force all rt tasks to start on little domain
HMP: select ‘best’ task for migration rather than ‘current’
sched: HMP fix traversing the rb-tree from the curr pointer
sched: track per-rq ‘last migration time’
HMP: Modify the runqueue stats to add a new child stat
HMP: Explicitly implement all-load-is-max-load policy for HMP targets
sched: HMP change nr_running offload metric
HMP: Implement idle pull for HMP
HMP: Access runqueue task clocks directly.
HMP: Update migration timer when we fork-migrate

Platform Support.

In addition to the big.LITTLE MP work the TC2 platform support includes:

  • TC2: reset CPUs spuriously woken up on cluster power up
  • vexpress: add shim layer for psci backend on TC2
  • vexpress: allow native pm ops backends to probe for psci suppport
  • psci: add cmdline option to enable use of psci
  • psci: add probe function to discover presence of a psci implementation
  • psci: convert psci ‘-EALREADYON’ error code to linux ‘-EAGAIN
  • vexpress: add psci support in TC2 device tree
  • psci: add constants to specify affinity levels
  • TC2: replace hard coded cluster and cpu values with constants
  • TC2: use generic accessors to extract cpu and cluster ids
  • CPUidle & CPUfreq support
  • hwmon driver allowing, amongst other things, TC2’s power, current and energy measurements to be read through standard sysfs interfaces
  • Common clocks implementation
  • Regulator driver
  • Drivers for previously hard-coded configuration interfaces
  • Support self-hosted debugging through idle
  • In addition to the CPU PMUs the perf framework supports the CCI-400 PMUs
  • A patch from Thomas Gliexner which supports a IRQ affinity mask being specified in the command line. This can be used to reduce unnecessary IRQ wakeups on Cortex-A15. For instructions see the irqaffinity entry in Documentation/kernel-parameters.txt
  • arm-multi_pmu_v2 – enables the use of multiple PMU types or sources, for example profiling across both Cortex-A15 and Cortex-A7 clusters and getting results for CCI.

Where To Find More Information

More information on Linaro can be found on our website.

Feedback and Support

Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development.

  • Linaro Development mailing list
  • Linaro IRC channel on at #linaro

  • Landing Team bug reports should be filed in JIRA by clicking on the “Create issue” button on the top menu bar.
    • You will need to login to your JIRA account. If you do not have an account or are having problems, email for help.
  • More general bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to Linaro project.
  • Questions? ask Linaro.
  • Interested in commercial support? inquire at Linaro support

Resolved in this release

  • ARM-47 /mnt/sdcard/.android_secure is missing on 4.3 Android builds

Known Issues

General Issues

  • ARM-16 LP:1097309 – serial console doesn’t received characters on TC2
  • ARM-24 LP:1172350 – Audio playback under Android JellyBean stops sporadically on TC2 with release 13.03
  • ARM-35 Warning in kmalloc_slab when running Android on RTSM
  • ARM-45 cpu_hotplug_latency_with_load/without_load failed to get trace
  • ARM-46 Booting using UEFI with bootmon from VE CD 5.2 fails
  • ARM-49 Vexpress-tc2 linaro 13.05 segfaults when cluster DTS node is removed
  • ARM-50 perf shows zero for cycle and instruction counts on TC2
  • ARM-52 hrtimer issues with TC2 on Linaro 13.06
  • ARM-53 Watchdog timeout booting Android on single core fastmodels

Known Issues due to lack of video acceleration

  • LP: #987155 vexpress: Angrybirds display severely truncated
  • LP: #987172 vexpress: YouTube video playback fails

Known Issues due to lack of software implementation

  • LP: #1042755 TC2: powertop doesn’t show correct frequency stats

Known Issues due to generic Android features

  • ARM-51 Gallery app crashes on start on vexpress Android 4.3

Known Issues due to generic Hardware Pack features

  • LP: #966411 vexpress: ubuntu: Network manager doesn’t manage ethernet connection
  • ARM-23 LP:1129005 – Intermittent failure of LTP shmat01 testcase

Known Issues due to u-boot not being supported by ARMLT

U-Boot is not supported by the ARM Landing Team. Therefore any u-boot bugs are marked as Won’t Fix.

  • LP: #912595 l-m-c fails on vexpress due to a change in u-boot name
  • LP: #880859 U-Boot boot script doesn’t work on Versatile Express

Known Issues due to hardware configuration in LAVA

Hardware configuration in LAVA is not under Landing Team control. Therefore any issues arising due to such hardware configuration are marked as Won’t Fix by the Landing Team.

  • LP: #1009326 e2eaudio test failed on Origen, Snowball & vexpress ubuntu image.

Linaro OpenEmbedded images are made up of two components. The Hardware Pack, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image.

Linaro provides two methods for installing Linaro binary builds:

  1. Using a pre-built image, which you can download
  2. Assembling your own image using provided components

Pre-Installation Steps

Before any installation begins, it is important that you ensure you Versatile Express board has the latest firmware and boot loader installed. Please check the “Firmware Update” tab on this page for the latest updates and installation instructions.

Using pre-built image


  • Ubuntu 12.04 64 bit or newer on your desktop PC (
  • 4GB SD card or larger
  • Latest firmware installed onto the Versatile Express. Please see “Firmware Update” tab
  • This release pre-built image.

Installation Steps

  • Unzip the downloaded pre-built image
  • Insert SD card into your PC and note the assigned '/dev/sdX'
SDCARD=/dev/sdX # sdcard found from dmesg above
zcat vexpress-openembedded_alip-armv7a-gcc-4.8_20130926-475.img.gz | sudo dd bs=64k of=$SDCARD

When the image is created, skip down to the section “Booting the image”.

Note: Windows users may use the Image Writer for Windows.

Building a custom image using pre-built components

Sometimes, you may wish to build your own custom image for a Versatile Express. Perhaps you wish to use a more recent snapshot of the hardware pack or take the latest Android build. Whatever the reason, you will want to use the Linaro Image Tools to create a custom image.

Using components to generate the image will yield the same functionality found in the pre-built image of the same release.


  • Ubuntu 12.04 64 bit or newer on your desktop PC (
  • Download Artifacts from above or use the following command in your terminal
  • Get Linaro image tools. There are multiple ways you can get the latest Linaro Image Tools:

  • Method 1: Install them from the Linaro Image Tools PPA

sudo add-apt-repository ppa:linaro-maintainers/tools
sudo apt-get update
sudo apt-get install linaro-image-tools

  • Method 2: Building from source

  • Insert SD card and note the assigned '/dev/sdX' or '/dev/mmcblk0'
dmesg | less

Look for a line that looks like the following at the end of the log

[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >

Or, if your machine uses ‘/dev/mmcblkX’, you may see a line line this:

[10770.938042] mmcblk0: p1 p2 p3 p4 < p5 p6 >

WARNING: In the next step, make sure you use /dev/“whatever you see above”. You can erase your hard drive with the wrong parameter.

  • Create media
sudo linaro-media-create --mmc /dev/sdX --dev vexpress --hwpack hwpack_linaro-lsk-vexpress_20130926-475_armhf_supported.tar.gz --binary linaro-image-alip-genericarmv7a-20130925-103.rootfs.tar.gz

Booting the image

After the media create tool has finished executing, remove the SD card from your PC and insert it into the Versatile Express board.

Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile MMC card configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device.

OpenEmbedded images are comprised of a Hardware Pack (HWPack) and a root file system. The hardware pack contains the kernel, boot loader and Device Tree blobs (if applicable). There is no need to rebuild the RootFS since it is comprised of a large number of debian packages. Instead, the best approach is to use an image, which you can create as outlined in the “Binary Image Installation” tab then replace the kernel with your compiled one. This is common practice that many engineers deploy when wanting a standard Linux image to use for testing and development purposes.

The following instructions will walk you through how to obtain the kernel source, build it, and add it to a pre-existing image.


  • Ubuntu 12.04 64 bit system. You can download Ubuntu from
  • git and toolchain. You can get those by typing the following command in your terminal
sudo apt-get install build-essential git gcc-arm-linux-gnueabi

Get the source

You can use GIT to obtain the kernel source code for this release:

git clone git://
cd linux-linaro-tracking
git checkout ll_20130918.0

Create a kernel config

Do not use the defconfig for Versatile Express, instead, build a config from the config fragments that Linaro provides:

ARCH=arm scripts/kconfig/ \
linaro/configs/linaro-base.conf \
linaro/configs/distribution.conf \
linaro/configs/big-LITTLE-MP.conf \

Note: the config fragments are part of the git repository and the source tarball.

Build the kernel

To build the kernel uImage, use the following command:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- LOADADDR=0x60008000 uImage

Install your kernel

This section is common for both Android and OpenEmbedded.

  • Create the Device Tree blob if you don’t have one in your Linaro image (note, the A9 Core Tile boots using an ATAGS kernel so there is no need for a device tree blob):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs
  • Insert the SD card containing the Linaro disk image into your PC SD card reader
  • Copy the kernel onto the memory card using
cp arch/arm/boot/uImage /media/boot/
  • Copy the device tree blob
    • For A9 CoreTile: no device tree blob is needed
    • For A5 CoreTile: cp arch/arm/boot/dts/vexpress-v2p-ca5s.dtb /media/boot/v2p-ca5s.dtb
    • For A15 CoreTile (TC1): cp arch/arm/boot/dts/vexpress-v2p-ca15-tc1.dtb /media/boot/v2p-ca15-tc1.dtb
    • For A15_A7 CoreTile (TC2): cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb
  • Eject the memory card from your PC by using the following command
eject /media/boot
  • Insert the memory card into the Versatile Express board and power it on
  • You should boot your image using your own compiled kernel

Ensure that you update your Versatile Express board firmware to the latest version. To update your VE board firmware, please follow the instructions below:

  • Connect and mount your Versatile Express motherboard USB mass storage device to your PC
  • Install the Recovery firmware from the v5.0 VE DVD onto your board.
  • Download ARM’s CPU Migration patch for version 5.0 from
    • Unzip the firmware zip to the root of the motherboard mounted drive
    • Please contact for any issues related this firmware update
  • Unmount the Versatile Express motherboard
  • Reboot the Versatile Express board
  • At the “Cmd> “ prompt, type the following commands:
    Cmd> flash
    Cmd> eraseall
    Cmd> exit
    Cmd> reboot
    • You may need to configure UEFI to boot from the image that you’ve created. See the UEFI page on the Linaro Wiki for more details on configuring UEFI.

You may want to set /media/VEMSD/config.txt AUTORUN to TRUE to be make the CoreTile boot from power on.

For TC2, you should set the DIP swich closest to the black reset button is down so that the Boot Monitor runs the boot script on power on.

Using TC2 as an A7-only or A15-only board

Configure the Firmware

It is possible to configure a TC2 development board as an A7 or A15 only board. To do this, the developer should modify the /SITE1/HBI0249A/board.txt file on the Versatile Express firmware drive, usually mounted at /media/VEMSD.

The relevant register is CFGREG6 on pages 78-81 of the following TRM:

You should add the following setting in board.txt:

SCC: 0x018 0x1FFFFFFF     ; CFGRW6 - Reset register default (both clusters active)
- or -
SCC: 0x018 0x00001FFF     ; CFGRW6 - A15-only config
- or -
SCC: 0x018 0x1FFFF000     ; CFGRW6 - A7-only config

Remember to update TOTALSCCS, eg, if it was 32 and you’ve added one register, it becomes 33:

TOTALSCCS: 33                   ;Total Number of SCC registers

Configure the Device Tree

Once the hardware is booting as an A7 or A15 only board, next you need to remove the unused CPU nodes from the device tree.

In the kernel source tree, edit arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts and remove the unused CPUs from this section:

   cpus {
        #address-cells = <1>;
        #size-cells = <0>;
       cpu2: cpu@2 {
            device_type = "cpu";
            compatible = "arm,cortex-a7";
            reg = <0x100>;
            cluster = <&cluster1>;
            core = <&core2>;
            clock-frequency = <800000000>;
            cci-control-port = <&cci_control2>;
       cpu3: cpu@3 {
            device_type = "cpu";
            compatible = "arm,cortex-a7";
            reg = <0x101>;
            cluster = <&cluster1>;
            core = <&core3>;
            clock-frequency = <800000000>;
            cci-control-port = <&cci_control2>;
       cpu4: cpu@4 {
            device_type = "cpu";
            compatible = "arm,cortex-a7";
            reg = <0x102>;
            cluster = <&cluster1>;
            core = <&core4>;
            clock-frequency = <800000000>;
            cci-control-port = <&cci_control2>;
       cpu0: cpu@0 {
            device_type = "cpu";
            compatible = "arm,cortex-a15";
            reg = <0>;
            cluster = <&cluster0>;
            core = <&core0>;
            clock-frequency = <1000000000>;
            cci-control-port = <&cci_control1>;
       cpu1: cpu@1 {
            device_type = "cpu";
            compatible = "arm,cortex-a15";
            reg = <1>;
            cluster = <&cluster0>;
            core = <&core1>;
            clock-frequency = <1000000000>;
            cci-control-port = <&cci_control1>;

Next, you need to remove the GIC entries that are associated with the removed CPUs, eg:

   gic: interrupt-controller@2c001000 {
        compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
        #interrupt-cells = <3>;
        #address-cells = <0>;
        reg = <0 0x2c001000 0 0x1000>,
              <0 0x2c002000 0 0x1000>,
              <0 0x2c004000 0 0x2000>,
              <0 0x2c006000 0 0x2000>;
        interrupts = <1 9 0xf04>;
       gic-cpuif@0 {
            compatible = "arm,gic-cpuif";
            cpuif-id = <0>;
            cpu = <&cpu0>;
       gic-cpuif@1 {
            compatible = "arm,gic-cpuif";
            cpuif-id = <1>;
            cpu = <&cpu1>;
       gic-cpuif@2 {
            compatible = "arm,gic-cpuif";
            cpuif-id = <2>;
            cpu = <&cpu2>;
       gic-cpuif@3 {
            compatible = "arm,gic-cpuif";
            cpuif-id = <3>;
            cpu = <&cpu3>;
       gic-cpuif@4 {
            compatible = "arm,gic-cpuif";
            cpuif-id = <4>;
            cpu = <&cpu4>;

Finally, you need to re-compile the DTS file and copy it to the SD card used to boot the system, eg:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs
cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb

This release was boot tested on RTSM A15×4 and A15×4-A7×4 models. No rigorous testing was carried out. This build is expected to run on other RTSM models.


  • Install the RTSM model(s) you wish to run. You must have a valid license and the environment set up to run models
  • Install Linaro image tools
  • Install kpartx which you can get by issuing the following command in your terminal
sudo apt-get install kpartx

Linaro OpemEmbedded images are made up of two components. The Hardware Pack, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image.

Install Linaro Image Tools

There are multiple ways you can get the latest Linaro Image Tools:

  • Method 1: Install them from the Linaro Image Tools PPA

sudo add-apt-repository ppa:linaro-maintainers/tools
sudo apt-get update
sudo apt-get install linaro-image-tools

  • Method 2: Building from source


Create a 2GB image file

RTSM will only deal with file systems up to 2GB in size, however the if the pre-built image may be larger. In this case, you can build your own image using the pre-built artifacts as listed below.

Using the following command, you will download the RootFS, the hardware pack.


Now you need to create the image using the following commands.

linaro-media-create --image-file linaro.img --image-size 2000M --dev vexpress --hwpack hwpack_linaro-lsk-vexpress_20130926-475_armhf_supported.tar.gz --binary linaro-image-alip-genericarmv7a-20130925-103.rootfs.tar.gz
sudo kpartx -a linaro.img
mkdir boot
sudo mount /dev/mapper/loop0p1 boot
cp boot/uImage .
cp boot/uInitrd .
cp -ar boot/rtsm rtsm
sudo umount boot
sudo kpartx -d linaro.img

note: unless you use kpartx to delete the loop mappings as above, even if you update linaro.img and re-mount it, it will not refresh and you will end up using the old image.

Run RTSM with UEFI

The instructions for running UEFI on the various models are very similar. The two differences are the UEFI binary and the model used. Follow the model specific instruction below, then proceed to the generic instructions in the section “Run the model with UEFI”.

Run A9×4 model with UEFI


Run A15×1 model with UEFI


Run A15×2 model with UEFI


Run A15×4 model with UEFI


Run the model with UEFI

-C motherboard.flashloader0.fname=$RTSM_UEFI \
-C motherboard.flashloader1.fname=$RTSM_UEFI_VARS \
-C motherboard.flashloader1.fnameWrite=$RTSM_UEFI_VARS \
-C motherboard.mmc.p_mmc_file=$RTSM_MMC \
-C motherboard.pl011_uart0.unbuffered_output=true \
-C motherboard.smsc_91c111.enabled=1 \
-C motherboard.hostbridge.userNetworking=1

Run A15×4 model with the Boot Wrapper

This example shows how to run the Linaro kernel on a quad core A15 RTSM model:

RTSM_CMDLINE="console=ttyAMA0,115200n8 root=/dev/mmcblk0p2 rootwait ro mem=1024M ip=dhcp"
-C motherboard.smsc_91c111.enabled=1 \
-C motherboard.hostbridge.userNetworking=1 \
-C motherboard.mmc.p_mmc_file="$RTSM_MMC" \
-C cluster.cpu0.semihosting-cmd_line="--kernel $RTSM_KERNEL --dtb $RTSM_DTB --initrd $RTSM_INITRD -- $RTSM_CMDLINE"

Run A15×4-A7×4 model with the Boot Wrapper

This example shows how to run the Linaro kernel on a big.LITTLE RTSM model. There is no UEFI binary for the big.LITTLE model, so we only use the boot wrapper for this model.

RTSM_CMDLINE="console=ttyAMA0,115200n8 root=/dev/mmcblk0p2 rootwait ro mem=1024M ip=dhcp"
-a coretile.cluster0.*=$RTSM_BOOTWRAPPER \
-a coretile.cluster1.*=$RTSM_BOOTWRAPPER \
-C motherboard.smsc_91c111.enabled=1 \
-C motherboard.hostbridge.userNetworking=1 \
-C motherboard.mmc.p_mmc_file=$RTSM_MMC \
-C coretile.dualclustersystemconfigurationblock.CFG_ACTIVECLUSTER=0x3 \
-C coretile.cluster0.cpu0.semihosting-enable=1 \
-C coretile.cluster0.cpu0.semihosting-cmd_line="--kernel $RTSM_KERNEL --dtb $RTSM_DTB --initrd $RTSM_INITRD -- $RTSM_CMDLINE"