are separate -sdk image targets necessary Was: Build external module against Yocto kernel

are separate -sdk image targets necessary Was: Build external module against Yocto kernel

[Trevor Woerner]

On Tue, Jan 15, 2013 at 2:16 PM, Zhang, Jessica <jessica.zhang@intel.com> wrote:
> According to bug 1614, the kernel dev packages should be
> included in sdk images. Please generate your toolchain using
> "bitbake core-image-sato-sdk -c populate_sdk" which will
> make the toolchain target sysroot matching your image's
> sysroot (this is a new feature of 1.3) as long as your image
> is a sdk image.

I am a bit confused by the above email. To me it appears as if Jessica
is saying: "add '-c populate_sdk' to the build of an -sdk image".

But if we look at this email from Mark Hatle:
http://www.mail-archive.com/yocto@yoctoproject.org/msg10636.html

I get the impression that Mark is saying: "now that '-c populate_sdk'
is available, there no longer is any need for separate -sdk images".

Am I confusing two different things with each other?

Re: are separate -sdk image targets necessary Was: Build external module against Yocto kernel

[Burton, Ross]

On 23 January 2013 16:51, Trevor Woerner <twoerner@gmail.com> wrote:
> On Tue, Jan 15, 2013 at 2:16 PM, Zhang, Jessica <jessica.zhang@intel.com> wrote:
>> According to bug 1614, the kernel dev packages should be
>> included in sdk images. Please generate your toolchain using
>> "bitbake core-image-sato-sdk -c populate_sdk" which will
>> make the toolchain target sysroot matching your image's
>> sysroot (this is a new feature of 1.3) as long as your image
>> is a sdk image.
>
> I am a bit confused by the above email. To me it appears as if Jessica
> is saying: "add '-c populate_sdk' to the build of an -sdk image".
>
> But if we look at this email from Mark Hatle:
> http://www.mail-archive.com/yocto@yoctoproject.org/msg10636.html
>
> I get the impression that Mark is saying: "now that '-c populate_sdk'
> is available, there no longer is any need for separate -sdk images".
>
> Am I confusing two different things with each other?

My understanding was that populate_sdk will take the package set from
an image, add compilers and all development packages, and produce a
SDK.  So all you need is your production image, and then you can
generate a SDK from that.

Ross

Re: are separate -sdk image targets necessary Was: Build external module against Yocto kernel

[Zhang, Jessica]

Hi Trevor,

-c populate_sdk will generate a SDK that matches the target image, while an -sdk image allows people to use it to boot up device and do development work on target as you can see in the requirements of bug 1614. The other usage of an -sdk image is to extract its rootfs and use it as your cross development sysroot, if you want to use your toolchain against different sysroot(s).

Thanks,
Jessica

-----Original Message-----
From: Trevor Woerner [mailto:twoerner@gmail.com]
Sent: Wednesday, January 23, 2013 8:51 AM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: are separate -sdk image targets necessary Was: [yocto] Build external module against Yocto kernel

On Tue, Jan 15, 2013 at 2:16 PM, Zhang, Jessica <jessica.zhang@intel.com> wrote:
> According to bug 1614, the kernel dev packages should be included in
> sdk images. Please generate your toolchain using "bitbake
> core-image-sato-sdk -c populate_sdk" which will make the toolchain
> target sysroot matching your image's sysroot (this is a new feature of
> 1.3) as long as your image is a sdk image.

I am a bit confused by the above email. To me it appears as if Jessica is saying: "add '-c populate_sdk' to the build of an -sdk image".

But if we look at this email from Mark Hatle:
http://www.mail-archive.com/yocto@yoctoproject.org/msg10636.html

I get the impression that Mark is saying: "now that '-c populate_sdk'
is available, there no longer is any need for separate -sdk images".

Am I confusing two different things with each other?

Re: are separate -sdk image targets necessary Was: Build external module against Yocto kernel

[Mark Hatle]

On 1/23/13 10:56 AM, Burton, Ross wrote:
> On 23 January 2013 16:51, Trevor Woerner <twoerner@gmail.com> wrote:
>> On Tue, Jan 15, 2013 at 2:16 PM, Zhang, Jessica <jessica.zhang@intel.com> wrote:
>>> According to bug 1614, the kernel dev packages should be
>>> included in sdk images. Please generate your toolchain using
>>> "bitbake core-image-sato-sdk -c populate_sdk" which will
>>> make the toolchain target sysroot matching your image's
>>> sysroot (this is a new feature of 1.3) as long as your image
>>> is a sdk image.
>>
>> I am a bit confused by the above email. To me it appears as if Jessica
>> is saying: "add '-c populate_sdk' to the build of an -sdk image".
>>
>> But if we look at this email from Mark Hatle:
>> http://www.mail-archive.com/yocto@yoctoproject.org/msg10636.html
>>
>> I get the impression that Mark is saying: "now that '-c populate_sdk'
>> is available, there no longer is any need for separate -sdk images".
>>
>> Am I confusing two different things with each other?
>
> My understanding was that populate_sdk will take the package set from
> an image, add compilers and all development packages, and produce a
> SDK.  So all you need is your production image, and then you can
> generate a SDK from that.

That is correct.  Just like everything else in OE, there are multiple ways to do 
things.

When it comes to the SDK there are two main ways, an SDK specific recipe, such 
as meta-toolchain, or use an existing image and produce an SDK for that image. 
The former is better for targeted SDKs that you want to allow something to 
produce software with a known set of limitations/capabilities.  The later is 
useful when your SDK has to match the image -exactly-.

The kernel components/headers is a separate issue.  The SDKs are currently 
configured to be focused on application development tasks.  Jessica and I were 
talking this morning, and it may be possible to enable kernel module compilation 
as well -- but this isn't the existing use-case.

--Mark

> Ross
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: install and use "bitbake -c populate_sdk"

[Eddy Lai GMail]

Hi,

I have build and boot the image from USB flash disk with the .hddimg 
created by "bitbake -k core-image-basic"
have added ssh server inside and make sure the ethernet works well,
then use "bitbake -c populate_sdk core-image-basic" to create the 
"poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory,
my plan is to install the sdk into the target system and compile my 
kernel module there, but now the problem is:
1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df" 
command from target said there's 85MB available only,
     but the sdk .sh installer image is about 300MB, how can I "extend" 
the target system to use the rest USB disk space? ( it's FAT file system)
     or how to modify configuration to force build the .hddimg create 
~"8GB" file system?
2. after that SDK installed into my target system, can I copy (scp) my 
own kernel module driver source code into the target system then
     make/compile and try insmod/debug the .ko there?
     or should I install the sdk on host system, then copy only the 
compiled .ko into target system for test/debugging?

Eddy

Re: install and use "bitbake -c populate_sdk"

[Trevor Woerner]

On Thu, Jan 24, 2013 at 8:48 AM, Eddy Lai GMail <eddy.lai.tw@gmail.com> wrote:
> how can I "extend" the
> target system to use the rest USB disk space? ( it's FAT file system)
>     or how to modify configuration to force build the .hddimg create ~"8GB"


By default a certain amount of overhead is applied to the final image.
So the scripts figure out the size of your image and add a certain
overhead.

In your conf/local.conf you can specify "IMAGE_ROOTFS_SIZE" which you
can set to the size, in kB, you want your image to have. But if you
image (plus overhead) would have been larger than this size, then
you'll get the larger + overhead size you would have received had you
not specified IMAGE_ROOTFS_SIZE.

You can adjust the overhead by playing with the IMAGE_OVERHEAD_FACTOR variable.

These calculations are performed by code from meta/classes/image_types.bbclass

Re: install and use "bitbake -c populate_sdk"

[Burton, Ross]

On 24 January 2013 17:12, Trevor Woerner <twoerner@gmail.com> wrote:
>> how can I "extend" the
>> target system to use the rest USB disk space? ( it's FAT file system)
>>     or how to modify configuration to force build the .hddimg create ~"8GB"
>
> By default a certain amount of overhead is applied to the final image.
> So the scripts figure out the size of your image and add a certain
> overhead.
>
> In your conf/local.conf you can specify "IMAGE_ROOTFS_SIZE" which you
> can set to the size, in kB, you want your image to have. But if you
> image (plus overhead) would have been larger than this size, then
> you'll get the larger + overhead size you would have received had you
> not specified IMAGE_ROOTFS_SIZE.

Or just set IMAGE_ROOTFS_EXTRA_SPACE, in kb.  I always add half a gig
to my images.

Ross

Re: install and use "bitbake -c populate_sdk"

[Zhang, Jessica]

Hi Eddy,

The SDK is meant to be used on development host for cross development instead of target.  Sounds like you need an sdk image which contains the development tools and needed development library and kernel sources.  Please refer to  core-image-sato-sdk for how to customize your image to allow your do development work on target.

Thanks,
Jessica

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Eddy Lai GMail
Sent: Thursday, January 24, 2013 5:49 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] install and use "bitbake -c populate_sdk"

Hi,

I have build and boot the image from USB flash disk with the .hddimg created by "bitbake -k core-image-basic"
have added ssh server inside and make sure the ethernet works well, then use "bitbake -c populate_sdk core-image-basic" to create the "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to install the sdk into the target system and compile my kernel module there, but now the problem is:
1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df"
command from target said there's 85MB available only,
     but the sdk .sh installer image is about 300MB, how can I "extend"
the target system to use the rest USB disk space? ( it's FAT file system)
     or how to modify configuration to force build the .hddimg create ~"8GB" file system?
2. after that SDK installed into my target system, can I copy (scp) my own kernel module driver source code into the target system then
     make/compile and try insmod/debug the .ko there?
     or should I install the sdk on host system, then copy only the compiled .ko into target system for test/debugging?

Eddy
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: install and use "bitbake -c populate_sdk"

[Lai Eddy]

[-- Attachment #1: Type: text/plain, Size: 3168 bytes --]

Thanks Jessica,

why I tried to use "-c populate-sdk" is because that I can find
"core-image-sato-sdk"  but no "core-image-basic-sdk" available, and my
hardware is a samll jasperforest x86_64 target with 2 serial port and 1
ethernet port only, no display interface.
I'm trying to find if any of following configuration suitable for my kernel
module driver develop/debug:
1. with the x86_64 toolchain sdk installed on my x86_64 host , build my
kernel module driver, then scp ".ko" binary to target for insmod/debugging,
but the problem I have now is the "make" always pointing to /usr/src/3.2.x
kernel source path (my host OS's kernel version), but not the linux-yocto
target kernel (3.4.x) source/header path (and I don't know where's the
proper 3.4.x target kernel header/source files, is it inside tmp/work/...? )
2.build and run the "core-image-basic" on my target, and install the sdk
created with "bitbake core-image-basic -c populate-sdk", but there's no
"/usr/src/.." , "/lib/modules/3.4.x-yocto-stand/build" exist

trying to build the "core-image-sato-sdk to see if that help for target
develop now...

Eddy

2013/1/31 Zhang, Jessica <jessica.zhang@intel.com>

> Hi Eddy,
>
> The SDK is meant to be used on development host for cross development
> instead of target.  Sounds like you need an sdk image which contains the
> development tools and needed development library and kernel sources.
>  Please refer to  core-image-sato-sdk for how to customize your image to
> allow your do development work on target.
>
> Thanks,
> Jessica
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:
> yocto-bounces@yoctoproject.org] On Behalf Of Eddy Lai GMail
> Sent: Thursday, January 24, 2013 5:49 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] install and use "bitbake -c populate_sdk"
>
> Hi,
>
> I have build and boot the image from USB flash disk with the .hddimg
> created by "bitbake -k core-image-basic"
> have added ssh server inside and make sure the ethernet works well, then
> use "bitbake -c populate_sdk core-image-basic" to create the
> "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to install
> the sdk into the target system and compile my kernel module there, but now
> the problem is:
> 1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df"
> command from target said there's 85MB available only,
>      but the sdk .sh installer image is about 300MB, how can I "extend"
> the target system to use the rest USB disk space? ( it's FAT file system)
>      or how to modify configuration to force build the .hddimg create
> ~"8GB" file system?
> 2. after that SDK installed into my target system, can I copy (scp) my own
> kernel module driver source code into the target system then
>      make/compile and try insmod/debug the .ko there?
>      or should I install the sdk on host system, then copy only the
> compiled .ko into target system for test/debugging?
>
> Eddy
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 4043 bytes --]

Re: install and use "bitbake -c populate_sdk"

[Zhang, Jessica]

[-- Attachment #1: Type: text/plain, Size: 3699 bytes --]

Hi Eddy,



I don't think build core-image-sato-sdk is the right approach.  Have you looked into following the example of hello-mod under meta-skeleton, to use bitbake to build your kernel module?



-          Jessica

From: Lai Eddy [mailto:eddy.lai.tw@gmail.com]
Sent: Wednesday, January 30, 2013 7:54 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] install and use "bitbake -c populate_sdk"



Thanks Jessica,



why I tried to use "-c populate-sdk" is because that I can find "core-image-sato-sdk"  but no "core-image-basic-sdk" available, and my hardware is a samll jasperforest x86_64 target with 2 serial port and 1 ethernet port only, no display interface.

I'm trying to find if any of following configuration suitable for my kernel module driver develop/debug:

1. with the x86_64 toolchain sdk installed on my x86_64 host , build my kernel module driver, then scp ".ko" binary to target for insmod/debugging, but the problem I have now is the "make" always pointing to /usr/src/3.2.x kernel source path (my host OS's kernel version), but not the linux-yocto target kernel (3.4.x) source/header path (and I don't know where's the proper 3.4.x target kernel header/source files, is it inside tmp/work/...? )

2.build and run the "core-image-basic" on my target, and install the sdk created with "bitbake core-image-basic -c populate-sdk", but there's no "/usr/src/.." , "/lib/modules/3.4.x-yocto-stand/build" exist



trying to build the "core-image-sato-sdk to see if that help for target develop now...



Eddy



2013/1/31 Zhang, Jessica <jessica.zhang@intel.com<mailto:jessica.zhang@intel.com>>

Hi Eddy,

The SDK is meant to be used on development host for cross development instead of target.  Sounds like you need an sdk image which contains the development tools and needed development library and kernel sources.  Please refer to  core-image-sato-sdk for how to customize your image to allow your do development work on target.

Thanks,
Jessica


-----Original Message-----
From: yocto-bounces@yoctoproject.org<mailto:yocto-bounces@yoctoproject.org> [mailto:yocto-bounces@yoctoproject.org<mailto:yocto-bounces@yoctoproject.org>] On Behalf Of Eddy Lai GMail
Sent: Thursday, January 24, 2013 5:49 AM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: Re: [yocto] install and use "bitbake -c populate_sdk"

Hi,

I have build and boot the image from USB flash disk with the .hddimg created by "bitbake -k core-image-basic"
have added ssh server inside and make sure the ethernet works well, then use "bitbake -c populate_sdk core-image-basic" to create the "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to install the sdk into the target system and compile my kernel module there, but now the problem is:
1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df"
command from target said there's 85MB available only,
     but the sdk .sh installer image is about 300MB, how can I "extend"
the target system to use the rest USB disk space? ( it's FAT file system)
     or how to modify configuration to force build the .hddimg create ~"8GB" file system?
2. after that SDK installed into my target system, can I copy (scp) my own kernel module driver source code into the target system then
     make/compile and try insmod/debug the .ko there?
     or should I install the sdk on host system, then copy only the compiled .ko into target system for test/debugging?

Eddy

_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto




[-- Attachment #2: Type: text/html, Size: 12209 bytes --]

Re: install and use "bitbake -c populate_sdk"

[Eddy Lai GMail]

[-- Attachment #1: Type: text/plain, Size: 4391 bytes --]

I have tried to copy entire 
"poky/meta-skeleton/recipes-kernel/hello-mod" folder
into my target  (poky/meta-intel/meta-jasperforest/recipes-kernel) and 
then add this line

MACHINE_EXTRA_RRECOMMENDS += "kernel-module-hello-mod"

to conf/local.conf,
but can't see hello-ko in the target binary image (core-image-basic) 
after boot USB from the target hardware,
anything else missed ? (yocto 1.3 + jasperforest BSP on x86_64 target)

Eddy
-----------------------------------
>
> Hi Eddy,
>
> I don't think build core-image-sato-sdk is the right approach.  Have 
> you looked into following the example of hello-mod under 
> meta-skeleton, to use bitbake to build your kernel module?
>
> -Jessica
>
> *From:*Lai Eddy [mailto:eddy.lai.tw@gmail.com]
> *Sent:* Wednesday, January 30, 2013 7:54 PM
> *To:* Zhang, Jessica
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] install and use "bitbake -c populate_sdk"
>
> Thanks Jessica,
>
> why I tried to use "-c populate-sdk" is because that I can find 
> "core-image-sato-sdk"  but no "core-image-basic-sdk" available, and my 
> hardware is a samll jasperforest x86_64 target with 2 serial port and 
> 1 ethernet port only, no display interface.
>
> I'm trying to find if any of following configuration suitable for my 
> kernel module driver develop/debug:
>
> 1. with the x86_64 toolchain sdk installed on my x86_64 host , build 
> my kernel module driver, then scp ".ko" binary to target for 
> insmod/debugging, but the problem I have now is the "make" always 
> pointing to /usr/src/3.2.x kernel source path (my host OS's kernel 
> version), but not the linux-yocto target kernel (3.4.x) source/header 
> path (and I don't know where's the proper 3.4.x target kernel 
> header/source files, is it inside tmp/work/...? )
>
> 2.build and run the "core-image-basic" on my target, and install the 
> sdk created with "bitbake core-image-basic -c populate-sdk", but 
> there's no "/usr/src/.." , "/lib/modules/3.4.x-yocto-stand/build" exist
>
> trying to build the "core-image-sato-sdk to see if that help for 
> target develop now...
>
> Eddy
>
> 2013/1/31 Zhang, Jessica <jessica.zhang@intel.com 
> <mailto:jessica.zhang@intel.com>>
>
> Hi Eddy,
>
> The SDK is meant to be used on development host for cross development 
> instead of target.  Sounds like you need an sdk image which contains 
> the development tools and needed development library and kernel 
> sources.  Please refer to  core-image-sato-sdk for how to customize 
> your image to allow your do development work on target.
>
> Thanks,
> Jessica
>
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org 
> <mailto:yocto-bounces@yoctoproject.org> 
> [mailto:yocto-bounces@yoctoproject.org 
> <mailto:yocto-bounces@yoctoproject.org>] On Behalf Of Eddy Lai GMail
> Sent: Thursday, January 24, 2013 5:49 AM
> To: yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> Subject: Re: [yocto] install and use "bitbake -c populate_sdk"
>
> Hi,
>
> I have build and boot the image from USB flash disk with the .hddimg 
> created by "bitbake -k core-image-basic"
> have added ssh server inside and make sure the ethernet works well, 
> then use "bitbake -c populate_sdk core-image-basic" to create the 
> "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to 
> install the sdk into the target system and compile my kernel module 
> there, but now the problem is:
> 1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df"
> command from target said there's 85MB available only,
>      but the sdk .sh installer image is about 300MB, how can I "extend"
> the target system to use the rest USB disk space? ( it's FAT file system)
>      or how to modify configuration to force build the .hddimg create 
> ~"8GB" file system?
> 2. after that SDK installed into my target system, can I copy (scp) my 
> own kernel module driver source code into the target system then
>      make/compile and try insmod/debug the .ko there?
>      or should I install the sdk on host system, then copy only the 
> compiled .ko into target system for test/debugging?
>
> Eddy
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto
>


[-- Attachment #2: Type: text/html, Size: 15419 bytes --]