From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 5EFF7E0082F; Tue, 4 Nov 2014 15:31:12 -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 X-Greylist: delayed 2807 seconds by postgrey-1.32 at yocto-www; Tue, 04 Nov 2014 15:31:01 PST Received: from ecbiz156.inmotionhosting.com (ecbiz156.inmotionhosting.com [23.235.201.8]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 911E6E0079E for ; Tue, 4 Nov 2014 15:31:01 -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:To:From; bh=u1pXi7CSY1/8bd46MIl+7Tf7XPmlrSqE04yHksYKSN8=; b=fxMW9sB0TsvxyvpASlvIACI1Ezwy+N8np7JMoMrSZDuLsTEn691wyleyYGayBdCQseF9h5K6e/juAymKftBFrAdSfA1lzHn4NaTHPY/YEb78WjUWOeGq2kFW+R+zMq2vRhtzii9GHaHuW1Mip1+drTGlVSy4b9F2d8X1EpV92ko=; Received: from modemcable124.64-80-70.mc.videotron.ca ([70.80.64.124]:49734 helo=BRIOGFOURNIER) by ecbiz156.inmotionhosting.com with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XlmpZ-0002c0-9G for meta-freescale@yoctoproject.org; Tue, 04 Nov 2014 17:44:12 -0500 From: "Guillaume Fournier" To: Date: Tue, 4 Nov 2014 17:44:08 -0500 Message-ID: <000a01cff880$d8b22690$8a1673b0$@brioconcept.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: Ac/4gFBTA9XnL+7dRGGcKnAohQaILQ== 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: 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: Tue, 04 Nov 2014 23:31:12 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Language: en-ca Hello, I am new to Yocto and I am having a hard time getting a basic environment setup. I have read a lot of documentation but I'm still stock so I'd like to seek your help. Problem: I can't get u-boot to start on my evaluation board. No output whatsoever on the UART. Board used: i.MX6 Series SABRE for Smart Devices (MCIMX6DL-SDP) Here are the steps I followed to get to the point where I am: *********************************************************************** BSP setup on a Ubuntu 12.04.5 LTS *********************************************************************** 1) Made sure following required packages were installed $ sudo apt-get install gawk wget git-core diffstat unzip texinfo build-essential chrpath libsdl1.2-dev xterm curl 2) Created a working directory $ mkdir ~/axion-dev 3) CD to that directory 4) Installed the REPO tool $ mkdir ~/axion-dev/bin $ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/axion-dev/bin/repo $ chmod a+x ~/axion-dev/bin/repo 5) Downloaded BSP source code $ PATH=${PATH}:~/axion-dev/bin $ mkdir ~/axion-dev/fsl-community-bsp $ cd ~/axion-dev/fsl-community-bsp $ git config --global user.email "gfournier@brioconcept.com" $ git config --global user.name "Guillaume Fournier" $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b daisy $ repo sync $ repo start axion --all *********************************************************************** Built and installed cross development toolchain *********************************************************************** 1) Setup the build environment (this changes the current working directory) $ source ./setup-environment build Accepted the EULA 2) Choose "imx6dlsabresd" as the machine. 3) Modified ~/axion-dev/fsl-community-bsp/build/conf/local.conf to change the MACHINE parameter with the name of the selected machine. For instance: MACHINE ??= 'imx6dlsabresd' 4) Launched the build $ bitbake meta-toolchain 5) Grabbed a coffee and waited... 6) Launched ~/axion-dev/fsl-community-bsp/build/tmp/deploy/sdk/poky-eglibc-x86_64-meta-t oolchain-cortexa9hf-vfp-neon-toolchain-1.6.1.sh When asked where to install, I choose ~/axion-dev/toolchain *********************************************************************** Got and built u-boot *********************************************************************** 1) Got Freescale u-boot $ cd ~/axion-dev $ git clone https://github.com/Freescale/u-boot-fslc.git 2) Ran toolchain environment script. This sets all relevant environment variables for cross-compilation $ ~/axion-dev/toolchain/environment-setup-cortexa9hf-vfp-neon-poky-linux-gnuea bi 3) Built u-boot $ cd ~/axion-dev/u-boot-fslc $ make LDFLAGS="" CC="$CC" mrproper $ make LDFLAGS="" CC="$CC" mx6dlsabresd_config $ make LDFLAGS="" CC="$CC" The reason behind the [LDFLAGS="" CC="$CC"] is this: u-boot top level Makefile contains: PLATFORM_LIBGCC := -L $(shell dirname `$(CC) $(CFLAGS) -print-libgcc-file-name`) -lgcc The above call gets resolved to "-L ." Doing ${CC} -print-libgcc-file-name shows the proper value. The reason for this is that U-Boot does not pickup $CC from our environment (which is including the --sysroot option). Without this option -print-libgcc-file-name resolve to a simple file name without a path. And thus dirname resolve it further to "." So the fix is to do: make LDFLAGS="" CC="$CC" This passes the ${CC} environment variable to the Makefile which in turns resolve the PLATFORM_LIBGCC correctly As read here: https://lists.yoctoproject.org/pipermail/yocto/2013-October/016385.html *********************************************************************** Flashed an SD card with u-boot *********************************************************************** 1) Downloaded Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER.gz from Freescale onto a Windows machine Also called IMX_6DL_6S_MFG_TOOL: Tool and documentation for downloading OS images to the i.MX 6DualLite and i.MX6Solo. Size (K): 73917 Format: gz Rev #: L3.0.35_4.1.0 Modified: 9/5/2013 http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREPL AT&fpsp=1&tab=Design_Tools_Tab 2) Uncompressed it 3) Modified {INSTALL_FOLDER}\cfg.ini so it looks like this: [profiles] chip = MX6DL Linux Update [platform] board = SabreSD [LIST] name = AXION-i.MX6DL-SABRESD-SD 4) Modified {INSTALL_FOLDER}\Profiles\MX6DL Linux Update\OS Firmware\ucl2.xml to add this list entry: Loading U-boot Loading Kernel. Loading Initramfs. Jumping to OS image. Sending partition shell Partitioning... Partitioning... Sending u-boot.bin write u-boot.bin to sd card Sending kernel uImage write kernel image to sd card Formatting rootfs partition Sending and writing rootfs Finishing rootfs write Unmounting rootfs partition Done 5) Created a directory under {INSTALL_FOLDER}\Profiles\MX6DL Linux Update\OS Firmware\ named "axion" 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 7) Connected eval board to the Windows box using USB cable (on USB OTG connector) 8) Set all DIP switches on the eval board to OFF (SW6) 9) Powered the board 10)Ran MfgTool2.exe and hit Start 11)Once done, unpowered the board 12)Flip SW6 to '01000010' 13)Connected eval board to the Windows box using USB cable (USB TO UART connector) 14)Launched a terminal (I used PuTTY) on the virtual com port created (115200 N81) 15)Powered the board I would expect u-boot to come up here and it doesn't. I don't have anything output on the serial port. I have tried with supplied i.MX6DL-SABRESD-SD profile in IMX_6DL_6S_MFG_TOOL and it works fine, I get the expected u-boot printouts. What am I doing wrong ? Guillaume Fournier Hardware Designer Brioconcept Consulting Inc.