From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 0FFBAE008CF; Wed, 5 Nov 2014 08:41:26 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU 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] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from ecbiz156.inmotionhosting.com (ecbiz156.inmotionhosting.com [23.235.201.8]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 523C6E008C9 for ; Wed, 5 Nov 2014 08:41:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brioconcept.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=7OZQWqeeAVrN3Sq98RIFywC/QR/WLgFZI2KbhGEffCI=; b=o2Xf2NsKLL/9CrQBuR0CZUTvmPgNBvm8PMunmMzZrMFaxGPNHhfhWLuzfp466m+xKjw5qVM6XrdCWg5umnORR2Xal/o1cRjuLJZn94kwjGZi+0+jDI8YRv4P1wCUwYBB5TmrofYWL8a2ksmM4vokVN7+V8dRSRsg5DmufrF4kCU=; Received: from modemcable124.64-80-70.mc.videotron.ca ([70.80.64.124]:50747 helo=BRIOGFOURNIER) by ecbiz156.inmotionhosting.com with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1Xm3e2-000C3P-T4; Wed, 05 Nov 2014 11:41:19 -0500 From: "Guillaume Fournier" To: "'Gary Thomas'" , References: <000a01cff880$d8b22690$8a1673b0$@brioconcept.com> <006601cff906$1a17a170$4e46e450$@brioconcept.com> <008e01cff910$2c00b2f0$840218d0$@brioconcept.com> <00a301cff913$c9430060$5bc90120$@brioconcept.com> <545A4E9A.8060106@mlbassoc.com> In-Reply-To: <545A4E9A.8060106@mlbassoc.com> Date: Wed, 5 Nov 2014 11:41:21 -0500 Message-ID: <00c201cff917$54ccb6a0$fe6623e0$@brioconcept.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQKmmnTva9InJO+t6GG5EnVVZUvx/AJgL0tAAYIHMioBbJHTeQGBwdDkAoTHbK0CfQaevQF4+6DLmjqd8vA= X-OutGoing-Spam-Status: No, score=-2.9 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ecbiz156.inmotionhosting.com X-AntiAbuse: Original Domain - yoctoproject.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brioconcept.com X-Get-Message-Sender-Via: ecbiz156.inmotionhosting.com: authenticated_id: gfournier@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:41:26 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Language: en-ca >> 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 Ok, there was a problem with the -skip option. Removing it altogether solves the problem for the u-boot.imx coming from a Yocto build: cfimager -f u-boot-from-Yocto-build.imx -raw -offset 1024 -d d However, the u-boot.imx coming from u-boot-fslc cross-compiled with a Yocto installed toolchain doesn't. Back to square one...