i.MX Processors中的主题 Re: Custom board with IMX6D, building custom U-boot problems

Custom board with IMX6D, building custom U-boot problems

peterhygren — Thu, 23 May 2013 14:13:43 GMT

So we've developed a custom board based loosely on the Sabre Board for Smart Devices.

I've tried booting the default yocto image without success (which I have another thread opened for, but nobody seems to offer any help).

The documentation for doing something like this is a mess at best, but I found the document "i.MX 6Dual/6Quad BSP Porting Guide" which states:

This chapter provides a step-by-step guide that explains how to add i.MX 6 custom board support to U-Boot.

This developer's guide is based on U-Boot version 2009.08 plus LTIB-based package for the i.mx patches. Please refer to the release notes.

Nice, almost exactly what I want to do, except for yocto, but I can live with LTIB, I just need to get a Linux booted right now.

The guide stated:

1. Install LTIB as usual. Make sure you deselect U-Boot from compilation.

I've setup a virtual Ubuntu 9.04 machine according to "Setting_Up_LTIB_Host.pdf"

I've run the install script in "L3.0.35_4.0.0_130424_source" and disabled building U-boot => Build succeded, nice.

The guide now states:

2. Manually unpack U-Boot: ./ltib -m prep -p u-boot

Running that now results in:

peter@ubuntu:~/ltib/ltib$ ./ltib -m prep -p u-boot

Processing: u-boot

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

Build path taken because: build key set, no prebuilt rpm,

Testing network connectivity

OK GPP:

Try u-boot-v2009.08-imx_3.0.35_13.01.00.tar.bz2.md5 from the GPP

http://bitshrine.org/gpp/u-boot-v2009.08-imx_3.0.35_13.01.00.tar.bz2.md5:

06:52:35 ERROR 404: Not Found.

Try u-boot-v2009.08-imx_3.0.35_13.01.00.tar.bz2 from the GPP

http://bitshrine.org/gpp/u-boot-v2009.08-imx_3.0.35_13.01.00.tar.bz2:

06:52:36 ERROR 404: Not Found.

Can't get: u-boot-v2009.08-imx_3.0.35_13.01.00.tar.bz2 at ./ltib line 802.

f_prep() returned an error, exiting

traceback:

main:572

Exiting on error or interrupt

peter@ubuntu:~/ltib/ltib$

Internet connectivity is not an issue, the links don't work, and I can't find those files anywhere else.

Am I on the right path here? What I want to do is build a yocto or ltib based linux with u-boot that will boot on my custom board. I mean the u-boot is 4 years old.

I really need help here, could someone please point me in the right direction?

Re: Custom board with IMX6D, building custom U-boot problems

Yuri — Fri, 24 May 2013 01:48:59 GMT

You wrote : "I've run the install script in "L3.0.35_4.0.0_130424_source" and disabled building U-boot => Build succeded".

Have You built successfully a system (say, minimal configuration) after installation via ltib script?

Re: Custom board with IMX6D, building custom U-boot problems

peterhygren — Fri, 24 May 2013 08:53:50 GMT

You mean just run the ./ltib?

Did it now:

peter@ubuntu:~/ltib/ltib$ ./ltib

Processing platform: Freescale iMX6x Based Boards

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

using config/platform/imx/.config

Processing: fake-provides

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

Processing: kernel-3.0.35

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

Processing: skell

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

Processing: base_libs

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

Processing: busybox

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

Processing: libtermcap

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

Processing: bash

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

Processing: iproute

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

Processing: hotplug

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

Processing: udev

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

Processing: firmware-imx

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

Processing: imx-lib

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

Processing: imx-test

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

Processing: kobs-ng

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

Processing: sysconfig-mx

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

Processing: merge

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

Processing: modeps

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

Started: Fri May 24 01:52:48 2013

Ended: Fri May 24 01:52:49 2013

Elapsed: 1 seconds

Build Succeeded

Re: Custom board with IMX6D, building custom U-boot problems

sathishkumarbal — Thu, 13 Jun 2013 11:16:20 GMT

Modify the ltib/config/platform/imx/u-boot.spec.in like the following

< Release

: imx_3.0.35_13.01.00

---

> Release

: imx_3.0.35_4.0.0

now try again. it should work. for me it worked.