From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4E16CE008CE; Wed, 5 Nov 2014 08:16:02 -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 0E7CAE00830 for ; Wed, 5 Nov 2014 08:15:58 -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:Cc:To:From; bh=AB3qNyBW4ssDyLanGEeD2gtGSm3z8TEsb41fvdjvmV0=; b=QmwEji8/U+5Dch+3D679pbdAkzJbAKbo6RXmIYHVniIY+yvmnWcqvXC3QX45viAd0SoXRlx0XqfynvFXUOC54KHUOZQ4kUAvBpiIJVPcPgKzgbnev4GTOmZZT/ksVK+L65z17orh/ikO00E6AyL15kUQuuI604+2buk/5S8mmwE=; Received: from modemcable124.64-80-70.mc.videotron.ca ([70.80.64.124]:50427 helo=BRIOGFOURNIER) by ecbiz156.inmotionhosting.com with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1Xm3FU-0007Aq-BP; Wed, 05 Nov 2014 11:15:56 -0500 From: "Guillaume Fournier" To: "'Otavio Salvador'" References: <000a01cff880$d8b22690$8a1673b0$@brioconcept.com> <006601cff906$1a17a170$4e46e450$@brioconcept.com> <008e01cff910$2c00b2f0$840218d0$@brioconcept.com> In-Reply-To: Date: Wed, 5 Nov 2014 11:15:58 -0500 Message-ID: <00a301cff913$c9430060$5bc90120$@brioconcept.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQKmmnTva9InJO+t6GG5EnVVZUvx/AJgL0tAAYIHMioBbJHTeQGBwdDkAoTHbK2aWkVU4A== 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 Cc: meta-freescale@yoctoproject.org 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:16:02 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-ca >>>> 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=3D2' 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. Guillaume Fournier