[yocto] uboot.bin and rootfs but not uImage

Rudolf Streif rstreif at linuxfoundation.org
Sat Mar 2 11:29:10 PST 2013


You are missing .config because you called your defconfig
skidata-carrier_defconfig.
Just rename skidata-carrier_defconfig do defconfig in

SRC_URI = "git://${KSRC};protocol=file;branch=${KBRANCH};name=kernel \
           file://defconfig \
          "

Alternatively you could do

do_fetch_append () {
   mv ${S}/skidata-carrier_defconfig ${S}/defconfig
}

:rjs


On Sat, Mar 2, 2013 at 7:37 AM, Satya Swaroop DAMARLA <swaroop at weisser.at>wrote:

> Hi Bruce and Hi Rudy,
>
> You are right and it works until it failes at the do_configure.
> Suggestions please. Here is the file for linux-skidata.bb
>
> DESCRIPTION = "Skidata Linux Kernel"
> SECTION = "kernel"
> LICENSE = "GPLv2"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
> PV = "3.2"
>
> inherit kernel
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:${THISDIR}/${PN}/patches:"
>
> # GIT repository location
> KSRC ?= "/home/damarla/linux-nvidia.git"
>
> # Branch to check out
> KBRANCH ?= "remotes/origin/tamonten/l4t"
>
> # Revision tag or AUTOREV
> SRCREV ?= "${AUTOREV}"
>
> SRC_URI = "git://${KSRC};protocol=file;branch=${KBRANCH};name=kernel \
>            file://skidata-carrier_defconfig \
>            "
>
> COMPATIBLE_MACHINE = "skidata-carrier"
>
> S = "${WORKDIR}/linux-nvidia-skidata"
>
> The following is the error. I just need some suggestions. and other thing
> is there are several device tree compilers. Please tell me the variable and
> where to place it for the specific dts file to be used..
>
> ERROR: Function failed: do_configure (see
> /home/damarla/yocto/poky/buildSkidata/tmp/work/skidata_carrier-poky-linux-gnueabi/linux-skidata/3.2-r0/temp/log.do_configure.29911
> for further information)
> ERROR: Logfile of failure stored in:
> /home/damarla/yocto/poky/buildSkidata/tmp/work/skidata_carrier-poky-linux-gnueabi/linux-skidata/3.2-r0/temp/log.do_configure.29911
> Log data follows:
> | DEBUG: Executing python function sysroot_cleansstate
> | DEBUG: Python function sysroot_cleansstate finished
> | DEBUG: Executing shell function do_configure
> | NOTE: make oldconfig
> | make: *** No rule to make target `oldconfig'.  Stop.
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_configure (see
> /home/damarla/yocto/poky/buildSkidata/tmp/work/skidata_carrier-poky-linux-gnueabi/linux-skidata/3.2-r0/temp/log.do_configure.29911
> for further information)
> ERROR: Task 766 (/home/damarla/yocto/poky/meta/recipes-kernel/linux/
> linux-skidata.bb, do_configure) failed with exit code '1'
>
>
> Thanks a million
>
>
>
> On Fri, Mar 1, 2013 at 2:49 PM, Bruce Ashfield <
> bruce.ashfield at windriver.com> wrote:
>
>> On 13-03-01 03:53 AM, Satya Swaroop Damarla wrote:
>>
>>> Hi Rudy,
>>>
>>> Thank you for the basic file... I have a question here... The git
>>> directory is already saved on my work pc. What is the necessity to
>>> download it again? The reason behind my asking this question is, it is
>>> secured and so password is required. So, in order to avoid confusion I
>>> already downloaded it to a directory called
>>> "/home/damarla/linux-skidata.**git". So can I just write
>>>
>>> SRC_URI = "dir://home/damarla/linux-**skidata.git"
>>>
>>> I think in the above way I can just simply remove the KSRC and KBRANCH
>>> variables from the linux-skidata.bb <http://linux-skidata.bb> file. The
>>>
>>> revision tag is also not required in this cases as we are using the
>>> kernel provided by the company itself, I mean for the first basic build.
>>>
>>
>> The example code that was posted, already does this. KSRC points to
>> a git repository on your local machine:
>>
>>
>>    KSRC ?= "<path to>/linux-skidata.git"
>>
>> And the protocol is set to "file" in the SRC_URI
>>
>>
>>    SRC_URI = "git://${KSRC};protocol=file;**branch=${KBRANCH};name=kernel
>> \
>>        file://defconfig"
>>
>> There's nothing more that you need to do.
>>
>>
>>
>>> One more thing is the skidata-carrier_defconfig is already in the
>>> directory git I mentioned above at
>>> "/home/damarla/linux-skidata.**git/arch/arm/configs/skidata-**
>>> carrier_defconfig"
>>> ... When compiling the kernel how can we tell the build system to build
>>> the kernel using that specific defconfig file?
>>>
>>
>> Putting the defconfig on the SRC_URI is all that you have to do.
>>
>> This information is also covered in the quickstart and development
>> guides .. have you had a look at them ? If you have a look, you'll
>> see that more options are available with linux-yocto based recipes
>> (custom or the ones part of oe-core), which will allow you some more
>> flexibility in handling modifications to the kernel.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>>
>>
>>> Thanks Rudy in advance,
>>> Satya
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Feb 28, 2013 at 9:31 PM, Rudolf Streif
>>> <rstreif at linuxfoundation.org <mailto:rstreif@**linuxfoundation.org<rstreif at linuxfoundation.org>>>
>>> wrote:
>>>
>>>     Hi Satya,
>>>
>>>     You will first need a kernel recipe, let's call it linux-skidata.bb
>>>     <http://linux-skidata.bb>. It can look like this:
>>>
>>>
>>>     DESCRIPTION = "Skidata Linux Kernel"
>>>     SECTION = "kernel"
>>>     LICENSE = "GPLv2"
>>>
>>>     LIC_FILES_CHKSUM = "file://COPYING;md5=**
>>> d7810fab7487fb0aad327b76f1be7c**d7"
>>>
>>>     PV = "3.2"
>>>
>>>     inherit kernel
>>>
>>>     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:${THISDIR}/$**
>>> {PN}/patches:"
>>>
>>>     # GIT repository location
>>>     KSRC ?= "<path to>/linux-skidata.git"
>>>
>>>     # Branch to check out
>>>     KBRANCH ?= "<branch>"
>>>
>>>     # Revision tag or AUTOREV
>>>     SRCREV ?= "${AUTOREV}"
>>>
>>>     SRC_URI = "git://${KSRC};protocol=file;**branch=${KBRANCH};name=kernel
>>> \
>>>        file://defconfig \
>>>         "
>>>
>>>     S = "${WORKDIR}/git"
>>>
>>>
>>>     You will need to provide a defconfig file next to your recipe
>>>     containing the kernel configuration settings. Your kernel GIT repo
>>>     may contain a .config that is good for your hardware. In that case
>>>     you do not need a defconfig but is still a good practice and will
>>>     allow you to easily change the settings.
>>>
>>>     Then you need to adjust your machine configuration file:
>>>
>>>     PREFERRED_PROVIDER_virtual/**kernel ?= "linux-skidata"
>>>     PREFERRED_VERSION_skidata ?= "3.2%"
>>>
>>>
>>>     That should do it.
>>>
>>>     :rjs
>>>
>>>
>>>     On Thu, Feb 28, 2013 at 11:21 AM, Satya Swaroop Damarla
>>>     <swaroop.damarla at gmail.com <mailto:swaroop.damarla at gmail.**com<swaroop.damarla at gmail.com>>>
>>> wrote:
>>>
>>>         Yes I got an error message when I was building the kernel...
>>>           Actuallly I have a kernel git given by the company.... I
>>>         downloaded it and is in my work pc.. How can I tell the build
>>>         system to use that kernel?
>>>
>>>
>>>         On Thu, Feb 28, 2013 at 8:17 PM, Rudolf Streif
>>>         <rstreif at linuxfoundation.org
>>>         <mailto:rstreif@**linuxfoundation.org<rstreif at linuxfoundation.org>>>
>>> wrote:
>>>
>>>             Satya,
>>>
>>>             your machine configuration file looks ok as far as I can
>>>             tell. Did you get an error message when building the kernel?
>>>             Did you try to build just the kernel e.g. bitbake
>>> linux-yocto?
>>>
>>>             :rjs
>>>
>>>
>>>             On Mon, Feb 25, 2013 at 11:31 PM, Satya Swaroop Damarla
>>>             <swaroop.damarla at gmail.com
>>>             <mailto:swaroop.damarla at gmail.**com<swaroop.damarla at gmail.com>>>
>>> wrote:
>>>
>>>                 Hello Guys... I think uImage is important but it is not
>>>                 being generated by the yocto project. It only generated
>>>                 the rootfs and uboot.bin. Is there any variable that has
>>>                 to be introduced in the machine.conf (in my case it is
>>>                 skidata-tamonten.conf)....
>>>
>>>                 Here is the configuration file
>>>
>>>                 #@TYPE: Machine
>>>                 #@NAME: skidata-tamonten machine
>>>                 #@DESCRIPTION: Machine configuration for the Tamonten
>>> board
>>>
>>>                 PREFERRED_PROVIDER_virtual/**xserver ?= "xserver-xorg"
>>>
>>>                 IMAGE_FEATURES += "package-management"
>>>                 EXTRA_IMAGEDEPENDS += " u-boot"
>>>
>>>                 # Uncomment the following line to enable the hard
>>>                 floating point abi. Note that
>>>                 # this breaks some binary libraries and 3D (neither of
>>>                 which ship with
>>>                 # meta-yocto). For maximum compatibility, leave this
>>>                 disabled.
>>>                 DEFAULTTUNE ?= "cortexa9t"
>>>                 include conf/machine/include/tune-**cortexa9.inc
>>>
>>>                 IMAGE_FSTYPES += "tar.bz2 ext2"
>>>
>>>                 SERIAL_CONSOLE = "115200 ttyS0"
>>>
>>>                 PREFERRED_PROVIDER_virtual/**kernel ?= "linux-yocto"
>>>                 PREFERRED_VERSION_linux-yocto ?= "3.2%"
>>>
>>>                 KERNEL_IMAGETYPE = " uImage"
>>>
>>>                 PREFERRED_VERSION_u-boot ?= "v2013.01.01%"
>>>
>>>                 UBOOT_MACHINE = "tec_config"
>>>                 UBOOT_ENTRYPOINT = "0x17000000"
>>>                 UBOOT_LOADADDRESS = "0x17000000"
>>>
>>>                 MACHINE_FEATURES = "usbgadget usbhost vfat screen
>>>                 touchscreen keyboard"
>>>
>>>
>>>                 Greets,
>>>                 Satya
>>>
>>>                 ______________________________**_________________
>>>                 yocto mailing list
>>>                 yocto at yoctoproject.org <mailto:yocto at yoctoproject.org**>
>>>                 https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>
>>>
>>>
>>>
>>>             --
>>>             --
>>>             *Rudolf J. Streif*
>>>
>>>             Director of Embedded Solutions
>>>             The Linux Foundation
>>>
>>>             rudolf.streif at linux.com <mailto:rudolf.streif at linux.**com<rudolf.streif at linux.com>
>>> >
>>>             Phone: +1.619.631.5383 <tel:%2B1.619.631.5383>
>>>
>>>             Skype: rudolfstreif
>>>             PGP: RSA 2048/2048 D6E7D28B
>>>
>>>             Linux Foundation Events Schedule: events.linuxfoundation.org
>>>             <http://events.**linuxfoundation.org/<http://events.linuxfoundation.org/>
>>> >
>>>
>>>             Linux Foundation Training Schedule:
>>>             training.linuxfoundation.org
>>>             <http://training.**linuxfoundation.org/<http://training.linuxfoundation.org/>
>>> >
>>>
>>>
>>>
>>>
>>>
>>>     --
>>>     --
>>>     *Rudolf J. Streif*
>>>
>>>     Director of Embedded Solutions
>>>     The Linux Foundation
>>>
>>>     rudolf.streif at linux.com <mailto:rudolf.streif at linux.**com<rudolf.streif at linux.com>
>>> >
>>>     Phone: +1.619.631.5383 <tel:%2B1.619.631.5383>
>>>
>>>     Skype: rudolfstreif
>>>     PGP: RSA 2048/2048 D6E7D28B
>>>
>>>     Linux Foundation Events Schedule: events.linuxfoundation.org
>>>     <http://events.**linuxfoundation.org/<http://events.linuxfoundation.org/>
>>> >
>>>
>>>     Linux Foundation Training Schedule: training.linuxfoundation.org
>>>     <http://training.**linuxfoundation.org/<http://training.linuxfoundation.org/>
>>> >
>>>
>>>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> yocto mailing list
>>> yocto at yoctoproject.org
>>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>
>>>
>>
>


-- 
-- 
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation

rudolf.streif at linux.com
Phone: +1.619.631.5383
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B

Linux Foundation Events Schedule:  events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130302/4f17894a/attachment.html>


More information about the yocto mailing list