From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 9D606E008F5; Wed, 5 Nov 2014 06:51: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 41D88E0084D for ; Wed, 5 Nov 2014 06:51:12 -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=Xts5VtKFGS3Z2WxeDojJa0TXNySLlFbvF4dBKYaofJI=; b=YJwtX52ohEObE6d7lo3DtkPrtcBkoGJjblGHvkL6jgYyFG6Zf40zzl8yBcxGT+y8+H1xChl0E6R2YbgJzIH8cPQZu0Y4WfFolt2uJ1FAgQHNc8lU+LU5LWzJml1axE70f9duHIp+Ne+lV38clh/TPkWtnzxsiO8olIsGXEPR6EY=; Received: from modemcable124.64-80-70.mc.videotron.ca ([70.80.64.124]:50192 helo=BRIOGFOURNIER) by ecbiz156.inmotionhosting.com with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1Xm1vN-0007SO-Rq for meta-freescale@yoctoproject.org; Wed, 05 Nov 2014 09:51:11 -0500 From: "Guillaume Fournier" To: References: <000a01cff880$d8b22690$8a1673b0$@brioconcept.com> <20141105012336.63731653@e6520eb.localdomain> In-Reply-To: <20141105012336.63731653@e6520eb.localdomain> Date: Wed, 5 Nov 2014 09:51:08 -0500 Message-ID: <006c01cff907$ef0233e0$cd069ba0$@brioconcept.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQKmmnTva9InJO+t6GG5EnVVZUvx/AJEwulhmpKxaYA= 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 14:51:26 -0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Language: en-ca =C9ric, Since I'm using u-boot.BIN, I believe the seek=3D1 and skip=3D1 are = fine. I have tried this method with a "known-to-work" u-boot.bin and u-boot = boots up fine on the board. So the SD card u-boot.bin write part should work as expected. As suggested, I tried it using the .IMX file using : Sending u-boot.imx write u-boot.imx to sd card u-boot does not boot on the board either using this method. I do not have physical access to the linux box so I need to use my = Windows box to burn the image. This does not seem to be part of the problem for = now since I have proven that I can get a known-to-work image to boot fine on = the board. Guillaume --- Sent: November 4, 2014 7:24 PM Hi Guillaume, Le Tue, 4 Nov 2014 17:44:08 -0500, "Guillaume Fournier" a =E9crit : > file=3D"axion/u-boot.bin">Sending u-boot.bin > bs=3D1k seek=3D1 skip=3D1 conv=3Dfsync">write u-boot.bin to sd = card -> seek & skip is wrong with u-boot.imx you should use with u-boot-fslc : you only need seek=3D1 .../... > 6) Copied u-boot.bin from Linux box ~/axion-dev/u-boot-fslc to Windows box > {INSTALL_FOLDER}\Profiles\MX6DL Linux Update\OS Firmware\axion --> I think you should take u-boot.imx and not u-boot.bin a far simpler way if you have a SD slot on your Linux host should be : dd if=3Du-boot.imx of=3D/dev/mmcblk0 conv=3Dnotrunc seek=3D2 bs=3D512 = replace mmcblk0 by the right device (and take care to not erase your hard drive ;-) Eric