Blog - All Comments

RE: Using LTIB to Build Programs for SABRE Lite (i.MX6)

amgalbu — Fri, 21 Nov 2014 06:39:52 GMT

Hi Shaun

the LTIB can be used to build platform for iMX6-board from any vendor? How manufacturer-specific drivers are handled?

RE: Using LTIB to Build Programs for SABRE Lite (i.MX6)

Former Member — Fri, 21 Nov 2014 05:43:50 GMT

I followed the exact way as mentioned above but the build was not successful.

When I executed ./ltib, a error log file was created. Please find the error log below:

Processing: mtd-utils

=======================

Build path taken because: no prebuilt rpm,

Testing network connectivity

No network download connection available

Can't get: mtd-utils-1.5.0.tar.gz at ./ltib line 802.

Died at ./ltib line 1392.

traceback:

main::build_host_rpms:1392

main::host_checks:1447

main:554

Started: Thu Nov 20 22:21:11 2014

Ended: Thu Nov 20 22:21:39 2014

Elapsed: 28 seconds

These packages failed to build:

mtd-utils

Build Failed

----------------------------------

Seeing the above error log, I could see that it is trying to connect to internet but failing. But internet is there for the ubuntu desktop I am using.

Is there anything you can help me with ?

Thanks

Nandhan

RE: Getting Started with SABRE Lite (i.MX6)

Former Member — Tue, 01 Apr 2014 07:30:27 GMT

I think your experience of upgrading u-boot is fairly normal for e14 supplied boards. The version supplied on my boards was so outdated that the Boundary instructions don't work. The Boundary versions of SL ship with newer u-boot than the e14 version, which explains a lot.

The SL is a decent enough board once you get past the e14 issues of useless demo image and outdated firmware.

On the firmware side, there's actually a different way you can boot. Rather than u-boot you can put a minimal loader into the SPI flash which then re-directs the boot process to one of the SD slots. Details here https://wiki.linaro.org/Boards/MX6QSabreLite in the "Boot from SD" section. There are advantages and disadvantages to doing this, you have to pick a single SD slot and load that version of the code into SPI, however once done you won't have to mess with sb_loader when "run upgradeu" fails - u-boot will be on the SD card and is therefore easy to fix.

One of the bigger downsides for me is that you need an SD card, I really quite like having u-boot in SPI as it enables me to load the kernel and rootfs from a sata drive without having to worry about unreliable SD cards.