From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 30041E008CA; Wed, 5 Nov 2014 08:22:00 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A032DE00830 for ; Wed, 5 Nov 2014 08:21:44 -0800 (PST) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id B0622F811E3; Wed, 5 Nov 2014 09:21:43 -0700 (MST) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id B693DF811DF; Wed, 5 Nov 2014 09:21:42 -0700 (MST) Message-ID: <545A4E9A.8060106@mlbassoc.com> Date: Wed, 05 Nov 2014 09:21:46 -0700 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: <000a01cff880$d8b22690$8a1673b0$@brioconcept.com> <006601cff906$1a17a170$4e46e450$@brioconcept.com> <008e01cff910$2c00b2f0$840218d0$@brioconcept.com> <00a301cff913$c9430060$5bc90120$@brioconcept.com> In-Reply-To: <00a301cff913$c9430060$5bc90120$@brioconcept.com> Subject: Re: Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2014 16:22:00 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2014-11-05 09:15, Guillaume Fournier wrote: >>>>> The ultimate goal is to have a cross-compiler build environment that works for both u-boot and kernel development. For now, I used Yocto to generate the toolchain (using meta-toolchain as specified in my first post) as described in section 3.4 of the Yocto Project Application Developer's Guide. >>>> >>>> I am failing to see what is missing? I use the toolchain for kernel and u-boot development with no issues. What problems you are facing? >>>> >>>> -- >>>> Otavio Salvador O.S. Systems >>> >>> I know it is a long post but could you read the first email I sent to the mailing list? I think this will sum it up for you. Except for the last bit where I used the mfgtools instead of the cfimager (I changed after Daiane suggestion), everything is still relevant. Thanks for stepping in Otavio. >> >> As I said on the other e-mail you need to use the u-boot.imx file, not the u-boot.bin one. Another change needed for mfgtool xml file is the dd command which needs the removal of 'seek=2' as it has no padding.. > > I'm now using the cfimager instead of the mfgtool as suggested by Daiane. I am using u-boot.imx as follow: > cfimager -f u-boot.imx -raw -offset 1024 -skip 1024 -d d > > If I use an .sdcard file from a Yocto build like this: > cfimager -f core-image-base-imx6dlsabresd.sdcard -raw -d d > > That works. If I'm using, *from the same build*, the u-boot.imx like this: > cfimager -f u-boot.imx -raw -offset 1024 -skip 1024 -d d > > It doesn't! Of course, if I use my custom built u-boot, it doesn't either. I'm starting to believe that cfimager parameter are the culprit. I'd be suspicious of '-offset 1024' - I doubt that you need both. Give it a try - leave out either the 'offset' or 'skip' options -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------