From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4069BE008DB; Mon, 10 Nov 2014 20:06:55 -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,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [134.170.140.77 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] X-Greylist: delayed 850 seconds by postgrey-1.32 at yocto-www; Mon, 10 Nov 2014 20:06:51 PST Received: from APAC01-HK1-obe.outbound.protection.outlook.com (mail-hk1on0077.outbound.protection.outlook.com [134.170.140.77]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D0BC6E008B4 for ; Mon, 10 Nov 2014 20:06:51 -0800 (PST) Received: from [192.168.5.3] (220.233.218.62) by HKNPR02MB180.apcprd02.prod.outlook.com (10.141.19.26) with Microsoft SMTP Server (TLS) id 15.1.16.15; Tue, 11 Nov 2014 03:52:37 +0000 Message-ID: <546187FF.5060803@beamcommunications.com> Date: Tue, 11 Nov 2014 14:52:31 +1100 From: Craig McQueen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: X-Originating-IP: [220.233.218.62] X-ClientProxiedBy: HKNPR02CA002.apcprd02.prod.outlook.com (10.255.138.147) To HKNPR02MB180.apcprd02.prod.outlook.com (10.141.19.26) X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:HKNPR02MB180; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:HKNPR02MB180; X-Forefront-PRVS: 0392679D18 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(979002)(6009001)(6049001)(164054003)(189002)(199003)(87976001)(99396003)(97736003)(92566001)(92726001)(120916001)(83506001)(46102003)(40100003)(59896002)(33656002)(80316001)(19580395003)(101416001)(117156001)(102836001)(4396001)(62966003)(450100001)(77096003)(77156002)(64126003)(42186005)(31966008)(110136001)(99136001)(50986999)(95666004)(107886001)(229853001)(2351001)(107046002)(50466002)(105586002)(36756003)(106356001)(23676002)(86362001)(122386002)(87266999)(54356999)(64706001)(65956001)(20776003)(66066001)(47776003)(65806001)(21056001)(65816999)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:HKNPR02MB180; H:[192.168.5.3]; FPR:; MLV:ovrnspm; PTR:InfoNoRecords; MX:1; A:1; LANG:en; X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:HKNPR02MB180; X-OriginatorOrg: beamcommunications.com Subject: Rebuilding kernel doesn't rebuild sdcard image 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, 11 Nov 2014 04:06:55 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit I'm trying out Yocto to build core-image-minimal for imx28evk. I was able to build with the linux-imx kernel provider (which builds a 2.6.35 kernel), and then switch to linux-fslc kernel provider (3.14.19 kernel). That seemed fine. But now I am trying to switch back to linux-imx kernel provider, to check some things with the 2.6.35 kernel. But when I write the sdcard image then boot, I find the sdcard image still contains the 3.14.19 kernel. I tried: bitbake -c cleansstate linux-fslc bitbake -c cleansstate linux-imx bitbake core-image-minimal But still the sdcard image contains the 3.14.19 kernel. I had a closer look at what's in the build/tmp/deploy/images/imx28evk directory. Here is the latest .sdcard file, and the latest uImage file: -rw-r--r-- 1 craigm craigm 83886080 Nov 10 16:25 core-image-minimal-imx28evk-20141110052334.rootfs.sdcard -rw-r--r-- 2 craigm craigm 2612944 Nov 10 17:13 uImage--2.6.35.3-r45-imx28evk-20141110060936.bin I check the uImage file: file uImage--2.6.35.3-r45-imx28evk-20141110060936.bin uImage--2.6.35.3-r45-imx28evk-20141110060936.bin: u-boot legacy uImage, Linux-2.6.35.3-maintain+yocto+gb, Linux/ARM, OS Kernel Image (Not compressed), 2612880 bytes, Mon Nov 10 17:12:44 2014, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC: 0x35886962, Data CRC: 0x37FEB8CE So the uImage has been built fine. But it looks as though the core-image-minimal-imx28evk-xxxx.rootfs.sdcard has not been subsequently rebuilt. Perhaps the .sdcard file is only rebuilt if the root file system changes, but not if the kernel only changes. To confirm this, I mount the SD card and check its contents, and I see the uImage still contains a 3.14.19 kernel: file /media/craigm/Boot\ imx28e/uImage /media/craigm/Boot imx28e/uImage: u-boot legacy uImage, Linux-3.14.19-fslc+g00e4721, Linux/ARM, OS Kernel Image (Not compressed), 3586912 bytes, Mon Nov 10 12:10:21 2014, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC: 0x9CFC9D94, Data CRC: 0x7C476150 After this, I tried to force an SD card image rebuild, by rebuilding an arbitrary package: bitbake -c cleansstate nano bitbake core-image-minimal It rebuilt nano, but didn't rebuild _any_ of the images in build/tmp/deploy/images/imx28evk. So it looks as though the problem is bigger than I originally thought. I'm fairly new to Yocto, so I'm not sure what is going on here. Is it possible to update the recipe that builds the .sdcard file and other images, to ensure it will run after any kernel or root filesystem change? Meanwhile as a work-around, what is the command to manually re-run this step? Thanks, Craig McQueen