June 18, 2013

LTIB 4.0.0 images

We just uploaded a couple of images of the 4.0.0. release of kernel and LTIB from Freescale that include our latest kernel.

There are two images:
  • ltib4-with-x-20130618.tar.gz – This image was built with the FSL gnome release package configuration, which includes X-Windows, gstreamer-acceleration, and GPU acceleration.
  • ltib4-no-x-20130618.tar.gz – This image was built with gstreamer-acceleration and GPU acceleration, but without X-Windows.
The precise LTIB configuration is included in each image in the file ltib-4.0.0-config.tar.gz.

Each of the images can be extracted to a single-partition SD card formatted as ext2/3/4 like so (assuming that your SD card shows up as /dev/sdc):
~/$ echo ',,83,*' | sudo sfdisk /dev/sdc
~/$ sudo mkfs.ext3 -L ltib /dev/sdc1
~/$ udisks --mount /dev/sdc1
~/$ sudo tar zxvf ltib4-with-x-20130618.tar.gz -C /media/ltib/
~/$ sync && sudo umount /media/ltib
Each of these was built using the mx6qsabrelite configuration in LTIB, but the kernels were replaced and boot scripts added by overlaying the build output with this tarball, which is a recent build from our boundary-imx_3.0.35_4.0.0 kernel branch.

To test the gstreamer acceleration in each image, we used the gplay command-line player and placed a video fw.flv into the /root directory.
root@boundary:~/$ gplay fw.flv
To test the GPU acceleration, we exercised a number of the Vivante tutorials:
root@boundary:/opt/viv_samples/vdk/$ ./tutorial3_es20 -f 1000
Both images are configured with a single user: root (password “Boundary”), and are configured for DHCP on the ethernet port and to automatically start an SSH server.

Wi-Fi is configured in the kernel, and the firmware files for the TiWi device are present in the filesystems, so you can perform a first-pass test like so:
root@boundary:~/$ ifconfig wlan0 up
root@boundary:~/$ iwlist wlan0 scan
iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: E0:91:F5:CA:DE:FE
                    Frequency:2.437 GHz (Channel 6)
                    Quality=45/70  Signal level=-65 dBm
                    Encryption key:on
There are a bunch of new features in this release, including support for the Wayland X replacement, but we haven’t tested those. Our intent is to provide working images to test the kernel.

Comments 65

    1. Post

      Hi Fikret,

      LTIB doesn’t support apt-get. That’s a Debian/Ubuntu tool.

      I’m also surprised that sudo was even installed. LTIB typically starts everything as root.

      1. Fikret

        Hi Eric,

        I have achieved to install packages by connecting from the serial port. If I type sudo apt-get install … from the serial port terminal, the commands work. I have installed the necessary packages and now it works good.


  1. Post
  2. Mark

    So, the image (http://boundarydevices.com/eula?file=ltib4-no-x-20130618.tar.gz) runs well with the tests I have that can run on it. Building it so the other tests and the app we have will run is another story. The gstreamer pipelines and gplay do well, but some of the samples I have fail. The example above (./tutorial3_es20 -f 1000) seg faults, and clinfo does the following:

    >>>>>>>> ./clinfo Starting…

    Available platforms: 1

    Platform ID: 0
    CL_PLATFORM_NAME: Vivante OpenCL Platform
    CL_PLATFORM_VENDOR: Vivante Corporation

    !!! Error # -30 at line 203 , in file main.cpp !!!

    !!! Press to quit…

    !!! Exiting…

    As I start the process of rebuilding, are these symptoms of something obvious I’m missing?

    1. Post

      Hi Mark,

      I don’t have a machine and image handy to test this out.

      Is module galcore loaded? In some of our images, it was necessary to load it by hand:

      ~/$ modprobe galcore

      I don’t recall off-hand whether this was one of those.

      1. Mark

        Hey Eric, it loads automatically with the image I used. On my builds, I’ve had to modprobe it in rc.local and, at one point, built it into the kernel.

  3. yyang2000

    Hello Ericn,

    I am new and start working on the project with NITROGEN6W board.

    I’ve created the Ubuntu Linux machine and downloaded L3.0.35_4.0.0_130424_source.tar.gz from FreeScale website. The LTIB installation and configureation were successfully.

    I built the image and booted on Netroden demo board. I found there is no wireless module detected, which it sould be the LS Research Wifi module. Then I tried to configure kernel using command “make ARCH=arm CROSS_COMPILE=arm-fsl-linux-gnueabi- menuconfig” and to enable the TI WL12xx. Unfortunately I could not enable the TI WL12xx driver, because it is not there.

    From community, I found one post mentioned about supporting the Wifi device driver that you need to get a linux kernel source code released from Boundary instead from FreeScale. Then I git clone the boundary-imx_3.0.35_4.0.0 kernel source code.

    I configured the kernel and enabled TI WL12xx, but it is failed to compile with the error listing below.
    drivers/mfd/ezx-pcap.c: In function ‘pcap_isr_work’:
    drivers/mfd/ezx-pcap.c:205:2: error: implicit declaration of function ‘irq_to_gpio’ [-Werror=implicit-function-declaration]

    I am wondering if you can provide me some sort of helps. Thanks,

    Bill Ynag

    1. Post

      Hi Bill,

      I’m guessing that you didn’t start with the nitrogen6x_defconfig in the boundary-imx_3.0.35_4.0.0 kernel.

      The module ezx-pcap.c isn’t included in that kernel by default, and it isn’t one of ours…

  4. Mark

    Hey Eric,

    Started from scratch:

    – Fresh ltib install from https://community.freescale.com/docs/DOC-94809, and used the config files from http://boundarydevices.com/eula?file=ltib4-with-x-20130618.tar.gz (thanks for putting those in there)

    – kernel checked out from http://boundarydevices.com/i-mx6-kernel-l3-0-35_4-0-0/ and .config taken from a runing version of the filesystem above.

    – u-boot and scripts also taken from the filesystem above.

    The problems I had before are gone, however running gplay fw.flv will play the audio but not video. Any of the gstreamer pipelines I had exit with:

    WARNING: erroneous pipeline: could not link videotestsrc0 to mfw_gst_v4lsink_info_t0

    Oddly enough, if I start with the filesystem image, and just replace the kernel and modules, gplay works fine, but my pipelines still fail the same way.

    Should the method I’ve described work, or have I tripped up on something simple?

    1. Mark

      After some digging, I must not be building this correctly. gst-inspect mfw_v4lsink shows:

      Pad Templates:
      SINK template: ‘sink’
      Availability: Always

      while every other image I have (including older ones I’ve built) fill this out with the various formats.

      Pulled the codecs along with the main ltib tar ball, and put the contents in /var/tmp/pkgs/ on the build system. Pretty sure this is how I’ve been doing it for earlier builds on both the nitrogen and sabre boards. What am I missing?

    2. jiada

      Hi Mark

      I ran
      “gst-launch videotestsrc ! ‘video/x-raw-yuv,format=(fourcc)YV12’ ! mfw_v4lsink axis-left=10 axis-top=10 disp-width=400 disp-height=400 disp-type=lvds device=/dev/video1 –gst-debug=mfw_v4lsink:9 –gst-debug=videotestsrc:9”
      on my SabreLite board, also failed with
      “WARNING: erroneous pipeline: could not link videotestsrc0 to mfw_gst_v4lsink_info_t0”

      have you had this issue fixed for you?

      1. Mark

        Hi jiada,

        If I remember correctly, ltib wasn’t building all of gstreamer as expected. I needed to drop into a ltib shell and build by hand. My notes for this are on another computer, but the information came from the freescale board.

  5. odbwilson

    Hi all,

    I wanna develop a FULL HD video and image display solution with gsteamer on i.mx6 board (image: ltib4-with-x-20130618.tar.gz). Just wondering if I develop an application on Linux box (Nvidia ION2 desktop) with gsteamer SDK, can that be used in i.mx6 board?

    Or I need to install the same SDK (http://docs.gstreamer.com/display/GstSDK/Installing+on+Linux) on i.mx6 and compile?

    I am not quite familiar with the development kit on i.mx6?
    Or can you suggest a better way to do this?


    1. Post
  6. yyang2000

    Hi Ericn,

    Is Boundary’s ltib4-no-x-20130618.tar.gz LTIB image similar to Freescale L3.0.35_4.0.0-130424_source.tar.gz?

    I saw L3.0.35_4.0.0-130424_source.tar.gz is Linux BSP source code. What is ltib4-no-x-20130618.tar.gz?

    My current LTIB was installed by L3.0.35_4.0.0-130424 from Freescale. Do I have to replace it with ltib4-no-x-20130618.tar.gz for Nitrogen6X supporting TiWi?


  7. yyang2000

    Hi Ericn,

    Does Boundary has Liniux BSP source code that is similiar to Freescale’s L3.0.35_4.0.0-130424.tar.gz?

  8. dmeados@rosenaviation.com

    Hi –
    I used the “ltib4-with-x-20130618.tar.gz” image and followed the instructions listed above (and below…) to update an SD card which I then inserted into a Nitrogen6W board (no serial number but dated 3/22/2012). The board has a WL1271 TiWi-R2 module installed.

    ~/$ echo ‘,,83,*’ | sudo sfdisk /dev/sdc
    ~/$ sudo mkfs.ext3 -L ltib /dev/sdc1
    ~/$ udisks –mount /dev/sdc1
    ~/$ sudo tar zxvf ltib4-with-x-20130618.tar.gz -C /media/ltib/
    ~/$ sync && sudo umount /media/ltib

    The board booted up to a “root@freescale /$” prompt. This was slightly unexpected in that the web page depicts a “root@boundary:~/$” prompt (….?….).

    Entering the command “ifconfig wlan0 up” returned “ifconfig: SIOCGIFFLAGS: No such device”.

    So, I find myself wondering if the tar file I downloaded using the link above really contains the expected bits, whether there’s a board or module issue, or whether some configuration option was missed.

    Any insights would be appreciated…

    1. Post

      Hi David,

      First, the easy one: there’s a setting in LTIB for the host name, and I usually set things to boundary. If you see freescale, that means I missed a step and got the default.

      I thought WiFi was working in these images, but apparently missed that. You can likely get things working by copying in the firmware from this tar-ball onto the image. I’ll test this when I get to the office this morning and upload an updated image.

      1. Post

        The ltib-with-x image does have TiWi drivers and firmware installed.

        Out of the box, I could run this from the shell:

        root@freescale ~$ ifconfig wlan0 up
        root@freescale ~$ iwlist wlan0 scan
        ... list of WLAN access points here
        1. Post

          Same goes for the ltib-no-x tar-ball: ifconfig wlan0 up; iwlist wlan0 scan shows proper output.

          ~/Downloads$ tar ztvf ltib4-no-x-20130618.tar.gz | grep ti-connect
          drwxr-xr-x root/root         0 1969-12-31 17:25 lib/firmware/ti-connectivity/
          -rwxr-xr-x root/root    271064 1969-12-31 17:25 lib/firmware/ti-connectivity/wl128x-fw-multirole-plt.bin
          1. dmeados@rosenaviation.com

            Hi Eric –
            Okay, thank you for verifying that information.

            My configuration is using a version of uBoot programmed into the SPI_NOR flash. My understanding from a coworker is that this image is or should be the same image as the one bundled in the tar file (run upgradeu was used).

            One more thing I noticed is that DHCP is not enabled on my system. Do you know if the uBoot configuration from the SD card would be transferred to the uBoot image in the SPI NOR by the “run upgradeu” utility in uBoot?

            Based on what I’m seeing, I’m still uncertain as to whether my system is really configured the same as yours and as expected or whether there’s simply an issue with the TiWi module.

            Can you think of any other configuration options or settings that I may be missing?

            Any insight you can offer would be greatly appreciated.


      2. yyang2000

        Hi Eric,

        I reconfigured and built a LTIB BSP image. I got wl12xx_sdio probed, but WiFi still don’t see wl1271 module. Below is the output.

        I downloaded the ti-connectivity pack from your post link. untar and copy them to my target.

        root@freescale ~$ modprobe wl12xx_sdio
        root@freescale ~$ ifconfig wlan0 up
        ifconfig: SIOCGIFFLAGS: No such device

        1. Post
    2. Post

      Hi David,

      Is the trouble you’re having on one of your custom boards?

      Do you have the Timesys image we shipped with one of ours?

  9. yyang2000


    I have no problem with Boundary’s LTIB 4.0.0 image to ifconfig wlan0 up on the Nithogen6x board.

    My problem is that I built my LTIB image that did not load/detect wl1271 module although the wl12xx.ko was built. Below is what I did.

    1) Downloaded Freescale’s L3.0.35_4.0.0-130424_source code and installed LTIB on my ubuntu linux machine.
    2) Using ./ltib -c to configure/built a BSP image. The linux kernel, linux-3.0.35, is located under /ltib/rpm/BUILD/. The BSP image was successfully generated and including the u-boot loader, uImage and rootfs. After then I used a script file, flash_linux.sh, to flash it onto an SD card. Note the flash_linux.sh was from an Adeneo Embedded trainng class.
    3) After SD card booted on Nitrogen6x board, it did not load or detect wl1271 module. My co-worker mentioned “you have to use Boundary’s kernel and enable wl12xx”. So I git clone boundary-imx-3.0.35_4.0.0 kernel from github to my desktop.
    4) I configured and built the kernel uisng;
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- menumake // to enable wl12xx
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage -j4 // build kernel
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- module -j4 // build drivers as modules
    and followed your instructions to install the built modules into rootfs/lib/modules/kernelversion, which is 3.0.35-ge7a19ff.
    5) I copied uImage to SD card using “dd if=arch/arm/boot/uImage of=/dev/sdb bs=1k seek=1024
    6) I copied /rootfs/lib/modules/* to /media/myrootfs/lib/modules/
    7) Insert the SD into Nithogen6x to boot. After booted, I used “modprobe wl12xx_sdio” to probe the wl12xx module, but it showed not such driver. I used “dmesg |tail” to search wl1271 module, but got nothing.

    I have a question why the new image did not use the new kernelversion 3.0.35-ge7a19ff instead a previous kernel version 3.0.35-2508-g5450ff. I used “uname -a” to see which kernel version used. But it showed the previous kernel version 3.0.35-2508-g5450ff, not new one. That is my suspecious. I also did remove previous kernel version 3.0.35-2508-g5450ff from /lib/modules/. After removal, I booted system again, but it still showed old kernel version. Since the wl12xx was enabled and built as a module, wl12xx.ko, in new kernel version, the image should use the new kernel version. Obviously it did not. I am wondering if you can help me out about this issue.

    Bill Yang

  10. yyang2000

    Hi Ericn,

    Can you point to me what is meaning of the returning message when I issued “modprobe wl12xx_sdio”?

    root@freescale ~$ modprobe wl12xx_sdio
    modprobe: module wl12xx_sdio not found in modules.dep

    I’ve checked /lib/modules/3.0.35-2508-g54750ff-ge7a19ff/kernel/drivers/net/wireless/wl12xx/. There are 3 modules, wl12xx.ko, wl12xx_sdio.ko and wl12xx_sdio_test.ko. Why the system still could not probe the wl12xx module?

  11. Post

    This means that the kernel (/boot/uImage) doesn’t match the files in /lib/modules.

    What’s your kernel version (found in /proc/version)?

    If you’re using our image directly, it should match (3.0.35-2508-g54750ff).

    1. yyang2000

      The version is 3.0.35-2508-g54750ff-ge7a19ff as below output.

      Linux version 3.0.35-2508-g54750ff-ge7a19ff (byang@byang-EP45T-UD3P) (gcc version 4.6.
      2 20110630 (prerelease) (Freescale MAD — Linaro 2011.07 — Built at 2011/08/10 09:20)
      ) #3 SMP PREEMPT Wed Jul 10 12:17:31 MDT 2013

    2. yyang2000

      Hi Eric,

      Does Boundary provide or have a LTIB toolchain, boundary-L3.0.35_4.0.0_source.tar.gz like Freescale’s L3.0.35_4.0.0_source.tar.gz?

      I would like to install the Boundary’s LTIB toolchain on my second linux machine to perform the bulding BSP image. and find out the WiFi module, since your ltib4-no-x-20130618 BSP image just works fine for TiWi module.

  12. yyang2000

    The Build errors when I built BSP image with boundary-imx-3.0.35_4.0.0 kernel. If any one can help me

    creating libhttp.la
    (cd .libs && rm -f libhttp.la && ln -s ../libhttp.la libhttp.la)
    make[2]: Leaving directory `/home/byang/ltib/rpm/BUILD/gnome-vfs-2.24.1/modules’
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/byang/ltib/rpm/BUILD/gnome-vfs-2.24.1′
    make: *** [all] Error 2
    error: Bad exit status from /home/byang/ltib/tmp/rpm-tmp.46322 (%build)

    RPM build errors:
    Bad exit status from /home/byang/ltib/tmp/rpm-tmp.46322 (%build)
    Build time for gnome-vfs: 39 seconds

    Failed building gnome-vfs

    f_buildrpms() returned an error, exiting

  13. yyang2000


    Can any one help me to fix the WiFi issue as error below? I am testing on Boundary Device Nitrogen6x board that has a LS Research WiFi module. I tried to turn up the WiFi module. The kernel I used is linux-3.0.35_4.0.0. I am stuck here for couple of days could not go through.

    root@freescale ~$ modprobe wl12xx_sdio
    root@freescale ~$ ifconfig wlan0 up
    ifconfig: SIOCGIFFLAGS: No such device

  14. yyang2000

    Hi Eric,

    I built an image in LTIB with kernel 3.0.35_4.0.0 from freescale.

    I configured and enabled ti12xx in kernel configuration. It built and generated an image.
    I verified the image for /lib/firmware/ti-connectivity, /lib/modules/, and uImage. Everything seams OK. below is listing of those folder.

    byang@byang-EP45T-UD3P:~/ltib/rootfs/lib$ ls modules/3.0.35-2508-g54750ff-ge7a19ff/kernel/drivers/net/wireless/wl12xx/
    wl12xx.ko wl12xx_sdio.ko wl12xx_sdio_test.ko wl12xx_spi.ko
    byang@byang-EP45T-UD3P:~/ltib/rootfs/lib$ ls firmware/ti-connectivity/
    wl1271-fw-2.bin wl1271-fw.bin wl127x-fw-3.bin wl127x-nvs.bin
    wl1271-fw-ap.bin wl1271-nvs.bin wl127x-fw-plt-3.bin wl12xx-nvs.bin

    I flashed the image to an SD card, and booted on Nitrogen6x. It can modprobe ti12xx_sdio, but cannot ifconfig wlan0 up.

  15. yyang2000

    Hi Eric,

    I followed your instructions to build a kernel and modules as below steps.

    1) make nitrogen6x_defconfig
    2) make uImage modules
    3) dd if=arch/arm/boot/uImage of=/dev/sdb bs=1k seek=1024
    4) make INSTALL_MOD_PATH=~/tmp modules_install
    5) find ~/tmp/lib/modules/ -type l -exec rm -f {} ;
    6) cp -ravf ~/tmp/lib/modules/* /media/myrootfs/lib/modules/
    7) boot the SD card on board.

    After booted, I still did not get wlan0 up. below is the output.

    root@freescale ~$ ifconfig wlan0
    ifconfig: wlan0: error fetching interface information: Device not found
    root@freescale ~$ zcat /proc/config.gz |grep MACH
    # CONFIG_MACH_MX6SL_ARM2 is not set
    # CONFIG_MACH_MX6SL_EVK is not set
    root@freescale ~$ zcat /proc/config.gz |grep WL12
    # CONFIG_WL1251 is not set
    # CONFIG_MFD_WL1273_CORE is not set

    1. Post

      Hi Bill,

      Where did you get step 3 from? I suspect it’s from some Freescale document.

      For our boards, we don’t use a kernel in unformatted space, and you may have
      trashed your SD card in the process of doing this.

      What you want is a simple copy:

      ~/linux-imx6$ sudo cp -fv arch/arm/boot/uImage /media/myrootfs/boot/
      ~/linux-imx6$ sync && sudo umount /media/*

      This explains why you’re not getting CONFIG_MACH_NITROGEN6X=y in
      your kernel configuration at run time (you’re still running whatever is
      in /boot/uImage.

  16. yyang2000

    Hi Eric,

    Let’s deal with the kernelversion, since I’ve already done on uImage and Ti-connectivity.
    The kernel version installed on /tmp/lib/modules is 3.0.35-gc38a245. It has been copied over to /media/myrootfs/lib/modules/. There are some others kernel versions already existed on /media/myroott/lib/modules. you can see below list.

    root@freescale ~$ ll /lib/modules/
    drwxr-xr-x 3 root root 4096 Jul 1 2013 3.0.35-2508-g54750ff
    drwxr-xr-x 3 root root 4096 Jul 11 2013 3.0.35-2508-g54750ff-ge7a19ff
    drwxrwxr-x 3 messageb messageb 4096 Jul 11 2013 3.0.35-gc38a245
    drwxr-xr-x 3 root root 4096 Jul 9 2013 3.0.35-ge7a19ff

    But I looked at /proc/version as below.

    Linux version 3.0.35-2508-g54750ff-ge7a19ff (byang@byang-EP45T-UD3P) (gcc versi
    on 4.6.2 20110630 (prerelease) (Freescale MAD — Linaro 2011.07 — Built at 201
    1/08/10 09:20) ) #12 SMP PREEMPT Thu Jul 11 09:16:37 MDT 2013

    It is not new kernel /lib/modules/3.0.35-gc38a245 that I just built. Does it cause problem?

    1. Post

      Hi Bill,

      I think you didn’t copy arch/arm/boot/uImage into /media/myrootfs/boot,
      which is why you’re still running the old kernel (which doesn’t have Nitrogen6x support).

      You can see what version information is in a kernel file using strings:

      ~/linux-imx6$ strings arch/arm/boot/uImage | grep Linux
      ~/linux-imx6$ strings /media/myrootfs/boot/uImage | grep Linux

      When you use modprobe, a part of the kernel version will be used
      to find the right directory in /lib/modules.

      You can use uname to see which part:

      root@freescale: ~/$ uname -r
  17. artyeffem

    Building the nitrogen6x config from buildroot works when I use the buildroot/uClibc toolchain, but not when I use a cortexA9-glibc crosstool-ng toolchain. I can generate working U-boot and kernel from the cortexA9 toolchain, even NFS mounting the uClibc rootfs, but kernel fails to find init when trying to mount the glibc rootfs. I would prefer the glibc rootfs to be compatible with existing applications. Any tips?

    1. Post

      A couple of points:

      • The C library in your toolchain doesn’t matter when building the kernel.
      • Failing to find init is a pretty typical failure when moving things around. The kernel normally looks in /sbin/init in normal and NFS root filesystems, and /init for RAM disks.

      I suggest that you take this in two steps. First, use our latest kernel image (link in this post) and verify your filesystem.

      When that’s up and working, you can focus on recompiling the kernel using various tool chains. Note that we recently added some patches for gcc versions > 4.8.

      1. artyeffem

        I’m still unable to see the gstreamer plugins in my buildroot system. At first I thought this was caused by the Linaro tools, which are hardfloat, but I have the same results using a softfloat toolchain. Should I even be using the buildroot system for the nitrogen6x board?

  18. artyeffem

    I’ve had better success with the Linaro toolchain, which has full glibc support. Currently trying to figure out why the gst-inspect only returns the two staticelements, no plugins. The rootfs has a set of the base plugins under /usr/lib/gstreamer-0.10.

  19. Mark


    Continuing http://boundarydevices.com/configuring-i-mx6-machines-different-screens-nitrogen6x-sabre-lite/#comment-46599 since this looks more like the topic at hand.

    I knew about the -dirty flag (and that uname -a just pulls from /proc/version), but not about the git id. Thanks for that. Until this morning, I’ve been having problems with 4.0.0. I suspect from jumping between kernels and filesystems (and even freescale boards) for the past few months. Starting pretty much from scratch, I’ve managed to boot the no-x tarball above with a localy built kernel and modules. Still can’t seem to get a ltib build which will work with anything but 1.1.1. But, this should be good for the immediate future.

  20. Bill Yang


    When I booted from LTIB 4.0.0 on nitrogen6x board. It was asked for a password. I wonder how to reset the password. Second, how to change “boundary” prompt instead using my prompt?


  21. Bill Yang

    Does any one knows how to reset prompt “boundary” on terminal when it is booted? Also how to reset the password that BoundaryDevice has pre-set to “Boundary”. I need to change them. Please help.

    1. Post
      1. yyang2000


        RE: Change boundary prompt to my system name.

        There is no /etc/hostname. I’ve executed a command “hostname myname”. It replaced boundary with myname. However, after the system reboot, the prompt still backs to boundary. Also I notice, after it booted, the prompt is “boundary login:” and once loged in, it is “root@boundary ~$”.

        We need to change the prompt with myname login: and root@myname. Does it change in kernel or in rootfs?

      2. yyang2000

        Hi Eric,

        There is no /etc/hostname to allow us to change and put our company name on prompt. I think this should be changed into linux image, which I have to rebuild the ltib image as your posted. Can you please provide a detail how to rebuild ltib4-no-x-20130618 image.


        1. Post
          1. yyang2000


            Thanks. I got prompt fixed.

            I have another quesiton regarding WPA implemention. I got wpa_supplicant running and can ping other IPs on the network. However, there is message always pop up.

            cfg80211: Calling CRDA to update world regulatory domain
            wl1271: Association completed.

            I searched google and someone suggests to use “iw reg set US” to resolve. However, there is no iw packet. as well there is no apt-get install iw. I wonder if you have a idea about the issue.

    2. Post
  22. jkrupp

    Platform unrelated question, but this would really help me – Can you point me to any information on the Vivante samples? Code, tools used, or anything? Thanks!

    1. Post
  23. Bill Yang


    It seems Boundary’s LTIB BSP (ltib4-no-x-20130618.tar.gz) and IMX6 kernel (boundary-imx_3.0.35_4.0.0) don’t have the latest version of wl1271 driver.

    Since I configured and implement WPA_Supplicant on TIWI through wlan, the wl1271 CRDA issue pop up always and the wireless connections also were down and up.

    cfg80211: Calling CRDA to update world regulatory domain
    cfg80211: Calling CRDA to update world regulatory domain
    cfg80211: Calling CRDA to update world regulatory domain

    I have googled a while and found a post from TI E2E forum that talked about the same issue as I have. It suggested to update the wl1271 driver version as descript below.

    wl1271 CRDA problem on TI814x
    “It appears that you are using a fairly old driver version (R4_SP2_03_00). Can you please try again with our new driver (R5.SP5.01)? Build instruction can be found here: http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Build_Instructions

    I am wondering if Boundary has bewared the wl1271 driver version issue and if you has any comment and suggstion to solve this problem?
    Bill Yang

  24. prerit.jain

    I tried second image (ltib4-no-x-20130618.tar.gz). I copied it into SD card and boot the board. It got loaded. Now I am trying to access this board using “ssh boundary@” , then it is asking password for access. Can anybody tell me the password for ssh access to the board?


    1. Post
    2. Post
  25. Bill Yang

    Hi Eric,

    I wonder if you have any idea how to set up an AP (Access Point) on Nitrogen6x board with LIT4 BSP?

    I tried to set an AP on nitrogen6x. But it returned failure message “Could not set channel for kernel driver”. Below is my procedures. I’ve digged this issue for several days, but could not get resolving.

    root@boundary ~$ modprobe wl12xx_sdio
    root@boundary ~$ ifconfig -a
    can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-0
              NOARP  MTU:16  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:10
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    eth0      Link encap:Ethernet  HWaddr 00:19:B8:00:FB:E4
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    lo        Link encap:Local Loopback
              inet addr:  Mask:
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    wlan0     Link encap:Ethernet  HWaddr DE:AD:BE:EF:00:00
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    root@boundary ~$ hostapd -B /etc/hostapd.conf
    Configuration file: /etc/hostapd.conf
    wl1271: firmware booted (Rev
    Could not set channel for kernel driver
    wlan0: Unable to setup interface.
    wl1271: down

    The hostapd.conf file is listing below.

  26. Bill Yang

    Hi Eric,

    Since the ltib4 linux image does not support APT (apt-get), what is the substitution of the apt-get command? e.g. if I want to use apt-get update, what I should do it?

  27. yyang2000

    Hi Eric,

    We used ltib4-no-x version image and deployed on a Nitrogen6W board connected with a touchscreen, DB_SABER_Lite_Display. However, when I executed the command, ts_calibrate, it stops and pop up error message said “could not support the device”. I wonder if you have an idea with this error or comments? Thanks,

    root@boundary ~$ ts_calibrate
    xres = 1024, yres = 600
    error: could not support the device

    1. Post
    1. Post

Leave a Reply