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...@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.zh...@intel.com
<mailto:jessica.zh...@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-boun...@yoctoproject.org
<mailto:yocto-boun...@yoctoproject.org>
[mailto:yocto-boun...@yoctoproject.org
<mailto:yocto-boun...@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
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
