[yocto] [PATCH] libmailtools: Add HOMEPAGE info into recipe file.

2017-09-13 Thread Huang Qiyu
Signed-off-by: Huang Qiyu 
---
 meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb 
b/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
index 7afcb05..5a9ef84 100644
--- a/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
+++ b/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
@@ -1,4 +1,5 @@
 DESCRIPTION = "MailTools is a set of Perl modules related to mail applications"
+HOMEPAGE = "http://search.cpan.org/dist/MailTools/;
 SECTION = "libs"
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
-- 
2.7.4



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Eclipse Target Communication Framework prevents shutdown

2017-09-13 Thread Tim Orling
You are probably on an older Yocto Project release and missing this commit:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b467a22729bea886d7bde976c9606ac8e4589cde

Also, Mars support will be dropped soon, so please consider moving to Neon.

> On Sep 13, 2017, at 12:16 PM, Paul D. DeRocco  wrote:
> 
> I'm using TCF on a Raspberry Pi and on an Intel Atom, for remote target
> debugging with Eclipse Mars. It works fine, except for one thing: if I
> have to reboot the target, it puts up a message that says that "A stop job
> is running for Target Communication Framework", and it takes a minute and
> a half to time out. How do I get TCF to respond to the usual kill signal
> on shutdown, or have a more reasonable timeout like five seconds?
> 
> -- 
> 
> Ciao,   Paul D. DeRocco
> Paulmailto:pdero...@ix.netcom.com
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Fwd: Best practices when for script recipes.

2017-09-13 Thread Khem Raj
On Wed, Sep 13, 2017 at 1:06 PM, Einar Vading  wrote:
> Hi,
>
> I was just wondering if there is some best practice advice on how to
> handle adding a single script from a recipe.
>
> If I have one or a few shell scripts with their own recipe. Do I make
> a git and use the git from the recipe or do I just add the scripts to
> a files directory and install from there?
>
> Are there any pros and cons to either?
>

Generally, it depends. if OE is all you intend to support then you might
choose to keep it with the metadata or a separate repo. Keeping in seprate
repo makes a cleaner history as well as defines component ownership if
that matters.

If you drill down to automation or mechanics then there are no added benefits.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

2017-09-13 Thread Mark Hatle
On 9/12/17 9:19 PM, Mark Hatle wrote:
> On 9/12/17 9:06 PM, wenzong fan wrote:
>> On 09/12/2017 06:59 PM, Chanho Park wrote:
>>> Hi,
>>>
>>> I can't apply this patch on top of the master branch. Which revision did 
>>> you make the patches?
>>
>> Oops, that's my fault. I did a "sed -i -e 's/Subject: [/Subject: 
>> [meta-selinux][/g' 00*" to add prefix for mail subjects, that also 
>> changed the removed patch files in libsemanage.
>>
>> I'll send v2.
>>
>> Thanks
>> Wenzong
> 
> I don't see the original set of patches in my archives.  When you rebase, 
> please
> rebase on top of mgh/master-next.

My mailer finally loaded the original set.  I saw the same problems, but was
able to get them merged.

I have updated 'mgh/master-next'.  Please verify the contents include all of
your changes.

I tried to build a system and boot it, but it didn't work.  I'm guessing I
forgot something simple, but I can't make master-next into master without
knowing I can boot..  Any clue would be useful.  Thanks!


My configuration is:

bblayers.conf:

oe-core (master) & meta-selinux (mgh/master-next)


local.conf:

IMAGE_FEATURES_append = " debug-tweaks ssh-server-openssh"

DISTRO_FEATURES_append = " opengl x11 wayland acl xattr pam selinux"

PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-mls"
PREFERRED_VERSION_refpolicy-mls = "2.20170204"


I ran QEMU using:


runqemu qemux86 core-image-selinux ext4 nographic



Trying to login I get:

qemux86 login: root
[   23.960609] kauditd_printk_skb: 13 callbacks suppressed
Cannot execute /bin/sh: Permission denied
[   23.973922] audit: type=1400 audit(1505347190.805:29): avc:  denied  {
execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0
[   23.975463] audit: type=1400 audit(1505347190.813:30): avc:  denied  {
execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0



> --Mark
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Fwd: Best practices when for script recipes.

2017-09-13 Thread Einar Vading
Hi,

I was just wondering if there is some best practice advice on how to
handle adding a single script from a recipe.

If I have one or a few shell scripts with their own recipe. Do I make
a git and use the git from the recipe or do I just add the scripts to
a files directory and install from there?

Are there any pros and cons to either?

Best regards,
Einar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Keeping same IP address under DHCP

2017-09-13 Thread Paul D. DeRocco
Whenever I build a new version of my target system, the DHCP server in my
router thinks it's a new machine, and assigns it a new IP address. This
means that I have to edit the connection settings in Eclipse remote
debugging. What is changing in my system that makes that happen, and is
there any way, short of assigning a static IP address, to make the router
continue to recognize it as the same machine?

-- 

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Eclipse Target Communication Framework prevents shutdown

2017-09-13 Thread Paul D. DeRocco
I'm using TCF on a Raspberry Pi and on an Intel Atom, for remote target
debugging with Eclipse Mars. It works fine, except for one thing: if I
have to reboot the target, it puts up a message that says that "A stop job
is running for Target Communication Framework", and it takes a minute and
a half to time out. How do I get TCF to respond to the usual kill signal
on shutdown, or have a more reasonable timeout like five seconds?

-- 

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-13 Thread Khem Raj
On Wed, Sep 13, 2017 at 12:27 AM, Ayoub Zaki  wrote:

> I ran into the same problem:
>
> ENABLE_UART = "1" is not enough you should also add INSTALL_append= "
> rpi-config" to your local.conf and Serial port will be enabled.
>

​this should be automatically pulled in if you built a sdcard image.​



>
> On 12.09.2017 14:09, yahia farghaly wrote:
>
> I have bitbaked rpi-hwup-image for raspberry pi 3 on sd card and connected
> the serial ports to *usb to ttl device* . i have set the minicom to
> port: /dev/ttyUSB0
> baud rate: 115200
> the image is booting fine and i can see the prompt on the screen but
> cannot see in my serial console using minicom.
> *is serial enabled by default for this image ? *
> i also tried ENABLE_UART = "1" in local.conf but doesn't help.
>
> how to enable it ? and what the serial device name with respect to
> raspberry pi
>
> thanks,
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>
>
>
> --
>
> Ayoub Zaki
> Embedded Systems Consultant
>
> Vaihinger Str. 2/1
> 71634 Ludwigsburg
>
> e-mail: ayoub.z...@embexus.com
> Tel: +49176-62901545 <+49%20176%2062901545>https://embexus.com
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] pyro openembedded gpsd update-rc.d problems with read-only-rootfs

2017-09-13 Thread Dan Walkes
On Mon, Sep 11, 2017 at 5:01 AM, Burton, Ross  wrote:
> On 10 September 2017 at 21:35, Dan Walkes 
> wrote:
>>
>> It looks like because the update-rc.d step fails this setup gets moved
>> into a gpsd post install script, which won’t work because I’m
>> configured to use a read only root filesystem.  So I need to find a
>> way to keep the update-rc.d step from failing.
>
>
> The recipe shouldn't invoke update-alternatives directly, but use the
> update-alternatives class instead.
>

Thanks for the suggestion Ross.

I didn't mention it before but I had already attempted to make this
change after I initially noticed the problem.  See this commit:
https://github.com/Trellis-Logic/meta-openembedded/commit/ddf008dbdae602dbe722f1fcb231f5549e75a586

I didn't see any difference when I updated to use update-alternatives
instead of invoking directly.

Since the error message was related to update-rc.d I've also attempted
to use the multi-update form of update-rc.d in the above commit.  I
thought that might be required when multiple packages were built from
the same .bb file.  However, don't see a difference in the result with
these changes either.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed

2017-09-13 Thread yahia farghaly
i just did IMAGE_INSTALL_append = " speech-tools festival"

error log details:

Build Configuration:
> BB_VERSION= "1.34.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "raspberrypi3"
> DISTRO= "poky"
> DISTRO_VERSION= "2.3.2"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
> cortexa7"
> TARGET_FPU= "hard"
> meta
> meta-poky
> meta-yocto-bsp= "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"
> meta-oe
> meta-python
> meta-multimedia
> meta-networking   = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
> meta-raspberrypi  = "pyro:c981f01a2cdb3299eb57920cffbb5dfd4248209a"
> meta-ros  = "master:3ff83184bd16a9ef13660dd5df08687a6c17a458"
> meta-mylayer  = "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"
> Initialising tasks: 100%
> ||
> Time: 0:00:07
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: festival-2.3-r0 do_compile: oe_runmake failed
> ERROR: festival-2.3-r0 do_compile: Function failed: do_compile (log file
> is located at
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.49956)
> ERROR: Logfile of failure stored in:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.49956
> Log data follows:
> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32',
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
> | DEBUG: Executing shell function do_compile
> | NOTE: make
> | ERROR: oe_runmake failed
> | config/config:43:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/config:
> No such file or directory
> | config/common_make_rules:67:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/common_make_rules.mak:
> No such file or directory
> | Makefile:84:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/top_level.mak:
> No such file or directory
> | Makefile:85:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak:
> No such file or directory
> | make: *** No rule to make target
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak'.
> Stop.
> | ERROR: Function failed: do_compile (log file is located at
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.49956)
> ERROR: Task
> (/yocto/poky/meta-ros/recipes-extended/festival/festival_2.3.bb:do_compile)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2392 tasks of which 2390 didn't need to be
> rerun and 1 failed.
> Summary: 1 task failed:
>   /yocto/poky/meta-ros/recipes-extended/festival/festival_2.3.bb:
> do_compile
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code



‌

On 13 September 2017 at 08:42, yahia farghaly 
wrote:

> i want to install festival on the target image,
> it gives me this error *"ERROR: festival-2.3-r0 do_compile: oe_runmake
> failed"*
> i have added the meta-oe to bblayer also .
>
> how to solve this error ?
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>



-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

2017-09-13 Thread Philip Balister
On 09/13/2017 08:40 AM, Ruslan Bilovol wrote:
> On Thu, Aug 24, 2017 at 9:37 PM, Philip Balister  wrote:
>> Once again we will have a developer meeting in Prague the Sunday before
>> ELCE.
>>
>> Please go to https://www.openembedded.org/wiki/OEDEM_2017 and add
>> yourself if you are attending and ideas for topics.
>>
>> Although it is called a developer meeting, we invite members of the
>> larger community to attend. The core developers are always interested in
>> hearing how OpenEmbedded is used, and what we can do to make it better
>> for building the embedded devices of the future.
> 
> Is it free to attend, anything else required except of
> self-registration on wiki?

Self registration on the wiki is fine. See you in October.

Philip

> 
> Thanks,
> Ruslan
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer

2017-09-13 Thread yahia farghaly
thanks for the note.

‌

On 13 September 2017 at 16:53, Martin Jansa  wrote:

> You're missing incompatible branches, use the same branch for all 3 and it
> will work.
>
> On Wed, Sep 13, 2017 at 4:48 PM, yahia farghaly 
> wrote:
>
>> Minutes ago, i pulled the recent commits for poky,meta-oe, meta-raspberry
>> pi
>> and when i build this comes. there are actually another errors but as i
>> started taking one by one error. this was the first.
>>
>> *ERROR: No recipes available for:*
>> *
>> /yocto/poky/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.12%.bbappend*
>>
>>
>> --
>> Yahia Farghaly
>> Graduated from Faculty of Engineering - Electronics and Communications
>> Department at Cairo University.
>> Linkedin  - GitHub
>> 
>>
>>
>>
>> ‌
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer

2017-09-13 Thread Martin Jansa
You're missing incompatible branches, use the same branch for all 3 and it
will work.

On Wed, Sep 13, 2017 at 4:48 PM, yahia farghaly 
wrote:

> Minutes ago, i pulled the recent commits for poky,meta-oe, meta-raspberry
> pi
> and when i build this comes. there are actually another errors but as i
> started taking one by one error. this was the first.
>
> *ERROR: No recipes available for:*
> *
> /yocto/poky/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.12%.bbappend*
>
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer

2017-09-13 Thread yahia farghaly
Minutes ago, i pulled the recent commits for poky,meta-oe, meta-raspberry
pi
and when i build this comes. there are actually another errors but as i
started taking one by one error. this was the first.

*ERROR: No recipes available for:*
*
/yocto/poky/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.12%.bbappend*


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub




‌
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [bitbake] Failed to launch bitbake image -u -g depexp on a Debian 9 host system ?

2017-09-13 Thread Leonardo Sandoval
"Burton, Ross"  writes:

> On 12 September 2017 at 08:56, Karim ATIKI 
> wrote:
>
>
> FATAL: Unable to import extension module "depexp" from bb.ui.
> Valid extension modules: knotty, ncurses or taskexp
>
>
> depexp was renamed to taskexp.

and the -u parameter is the one expecting a user interface, -g is just
for producing the dot files, so flip the parameters. Just tried on
debian 9 and worked as expected.


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


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread yahia farghaly
For technical knowledge, why is it failing from the first place ?

from my observation, It seems to try to execute gnome-terminal by default,
so i installed it but it failed to open it. even when i tried with ssh -X ,
it opened gnome-terminal but print the same failure messages within it.


‌

On 13 September 2017 at 14:05, Alex Lennon 
wrote:

>
>
> On 13/09/2017 13:00, yahia farghaly wrote:
>
> Nice Aaron, it worked as charm.  Thank you !
>
> Alex, i will try your way. but you can test qemu without vnc by specifying 
> *serial
> nographic* of runqemu options
> ‌
>
>
> Yes. I generally have a need for graphical output for testing though :)
>
> You can actually use the in-built qemu VNC server if you change the
> options too...
>
> ref: https://wiki.archlinux.org/index.php/QEMU#vnc
>
> Cheers!
>
> Alex
>



-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Question about populate_sdk

2017-09-13 Thread Olaf Mandel
Hello,

Am 13.09.2017 um 13:43 schrieb Anders Darander:
-Snipp-
> See Yocto #11724, at https://bugzilla.yoctoproject.org/show_bug.cgi?id=11724
-Snipp-
> Ah, a small test example? Perfect!
> Could you add it the bug above? It would likely make it easier to debug.
> 
Done.

Cheers,
Olaf
-- 
Olaf Mandel




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Alex Lennon



On 13/09/2017 13:00, yahia farghaly wrote:

Nice Aaron, it worked as charm.  Thank you !

Alex, i will try your way. but you can test qemu without vnc by 
specifying /serial nographic/ of runqemu options

‌


Yes. I generally have a need for graphical output for testing though :)

You can actually use the in-built qemu VNC server if you change the 
options too...


ref: https://wiki.archlinux.org/index.php/QEMU#vnc

Cheers!

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Alex Lennon



On 13/09/2017 13:00, yahia farghaly wrote:

Nice Aaron, it worked as charm.  Thank you !

Alex, i will try your way. but you can test qemu without vnc by 
specifying /serial nographic/ of runqemu options

‌


Yes. I'm generally have a need for graphical output for testing though :)

You can actually use the in-built qemu VNC server if you change the 
options too...


ref: https://wiki.archlinux.org/index.php/QEMU#vnc

Cheers!

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread yahia farghaly
Nice Aaron, it worked as charm.  Thank you !

Alex, i will try your way. but you can test qemu without vnc by
specifying *serial
nographic* of runqemu options
‌

On 13 September 2017 at 13:51, Alex Lennon 
wrote:

> Hi Yahia,
>
> On 13/09/2017 12:24, Aaron Schwartz wrote:
>
>> Tmux [0] also works well for this, and I've never tried it with Screen (a
>> similar utility) so here's instructions using Tmux:
>>
>> You need to install Tmux on the server you are using SSH to connect to,
>> then as soon as you SSH into the server run `$ tmux`.  Then when you run `$
>> bitbake -c menuconfig ...` it will automatically open a second pane on the
>> bottom half of your screen where you can edit your kernel config.  That
>> pane will close automatically when you exit the menuconfig application.
>>
>> I hope that helps!
>> Aaron
>>
>>
>>
>>
> I mostly remote into my server via SSH too. And I use the screen method to
> run menuconfig and devshell and so forth. Works well.
>
> As Yusuke says you can install screen on the server (if it is Ubuntu or
> similar) if you need to with
>
> $ sudo apt install screen
>
> You might need to tell the bitbake tooling to use the screen utility which
> you can do with something like
>
> $ export  OE_TERMINAL=screen
>
> I see there are some notes here
>
> https://books.google.co.uk/books?id=yNi6BwAAQBAJ=PA35
> =PA35=yocto+OE_TERMINAL+screen=bl=HYab5gQgCg&
> sig=-qLFfrNLtglXCKwagcbU2Uqg1WM=en=X=0ahUKEwie667d
> iqLWAhUkLcAKHfXDBZwQ6AEIQzAD#v=onepage=yocto%20OE_
> TERMINAL%20screen=false
>
> ...
>
> I hadn't heard of tmux. Thanks Aaron - I will have a look into that...
>
> ...
>
> Sometimes I need a graphical environment. For example when I want to run
> up a Yocto Poky build for testing on a QEmu emulated machine easily.
>
> For this I have VNC Server installed on the build box. I then run this up
> and it creates a new desktop. Your default desktop is usually :0 and in my
> case VNC then creates a :1 desktop
>
> This usually ends up on build box local port 5901 as I recall (if not it
> will be a similar number, you can check with netstat -anp)
>
> You can then port forward the VNC TCP port 5901 over SSH and use a VNC
> client on your client local port.
>
> I often use Windows as a client so use Putty for the port forwarding and
> TightVNC for the VNC client.
>
> This could well sound quite fiddly but it's fine when you get it setup.
>
> There are some notes here which might be useful
>
> https://www.theurbanpenguin.com/creating-an-ssh-tunnel-with-
> putty-to-secure-vnc/
>
> Cheers,
>
> Alex
>
>


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Alex Lennon

Hi Yahia,

On 13/09/2017 12:24, Aaron Schwartz wrote:
Tmux [0] also works well for this, and I've never tried it with Screen 
(a similar utility) so here's instructions using Tmux:


You need to install Tmux on the server you are using SSH to connect 
to, then as soon as you SSH into the server run `$ tmux`.  Then when 
you run `$ bitbake -c menuconfig ...` it will automatically open a 
second pane on the bottom half of your screen where you can edit your 
kernel config.  That pane will close automatically when you exit the 
menuconfig application.


I hope that helps!
Aaron





I mostly remote into my server via SSH too. And I use the screen method 
to run menuconfig and devshell and so forth. Works well.


As Yusuke says you can install screen on the server (if it is Ubuntu or 
similar) if you need to with


$ sudo apt install screen

You might need to tell the bitbake tooling to use the screen utility 
which you can do with something like


$ export  OE_TERMINAL=screen

I see there are some notes here

https://books.google.co.uk/books?id=yNi6BwAAQBAJ=PA35=PA35=yocto+OE_TERMINAL+screen=bl=HYab5gQgCg=-qLFfrNLtglXCKwagcbU2Uqg1WM=en=X=0ahUKEwie667diqLWAhUkLcAKHfXDBZwQ6AEIQzAD#v=onepage=yocto%20OE_TERMINAL%20screen=false

...

I hadn't heard of tmux. Thanks Aaron - I will have a look into that...

...

Sometimes I need a graphical environment. For example when I want to run 
up a Yocto Poky build for testing on a QEmu emulated machine easily.


For this I have VNC Server installed on the build box. I then run this 
up and it creates a new desktop. Your default desktop is usually :0 and 
in my case VNC then creates a :1 desktop


This usually ends up on build box local port 5901 as I recall (if not it 
will be a similar number, you can check with netstat -anp)


You can then port forward the VNC TCP port 5901 over SSH and use a VNC 
client on your client local port.


I often use Windows as a client so use Putty for the port forwarding and 
TightVNC for the VNC client.


This could well sound quite fiddly but it's fine when you get it setup.

There are some notes here which might be useful

https://www.theurbanpenguin.com/creating-an-ssh-tunnel-with-putty-to-secure-vnc/

Cheers,

Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Question about populate_sdk

2017-09-13 Thread Anders Darander
Hi, 

* Olaf Mandel  [170913 13:16]:

> I hope this is the right place to ask this: I wanted to generate an SDK
> bundle to work on an applications code outside of the bitbake
> environment (also without devtool, if possible). So I selected an image
> containing the application and ran the populate_sdk task of that image.
> But the generated SDK is missing some dependencies of the application.

> Is this expected? Or am I doing something wrong?

No, all the dependencies should be part of the generated SDK.

I've seen this, and unfortunately, not had time to debug it, nor create
a small test example. And when I took time to make a small test, I
didn't immediately find theh issue...

See Yocto #11724, at https://bugzilla.yoctoproject.org/show_bug.cgi?id=11724

> I made a minimal demo layer that shows the problem (see below for the 7
> files making up the demo). I ran "bitbake -c populate_sdk test-image"
> and I expected the file usr/lib/test-lib to be present in the SDK, but
> it is not.

Ah, a small test example? Perfect!
Could you add it the bug above? It would likely make it easier to debug.

Cheers
Anders

-- 
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Aaron Schwartz
Tmux [0] also works well for this, and I've never tried it with Screen (a
similar utility) so here's instructions using Tmux:

You need to install Tmux on the server you are using SSH to connect to,
then as soon as you SSH into the server run `$ tmux`.  Then when you run `$
bitbake -c menuconfig ...` it will automatically open a second pane on the
bottom half of your screen where you can edit your kernel config.  That
pane will close automatically when you exit the menuconfig application.

I hope that helps!
Aaron


0)  https://github.com/tmux/tmux/wiki

On Wed, Sep 13, 2017 at 7:17 AM, yahia farghaly 
wrote:

>
> can you give some steps on how to do this ?
>
>
> ‌
>
> On 13 September 2017 at 10:54, Yusuke Mitsuki <
> mickey.happygolu...@gmail.com> wrote:
>
>> Hello
>>
>> You can use screen.
>> If your host is ubuntu,you can get via apt as follows.
>>
>> sudo apt install screen.
>>
>> If necessary , you can set auto or screen to OE_TERMINAL environment.
>>
>> 2017/09/13 16:09 "yahia farghaly" :
>>
>>> Hi,
>>>
>>> I am working with yocto from a remote server using ssh. i want to
>>> execute *bitbake -c menuconfig virtual/kernel*  . It fails to open
>>> since it tries to open another shell.
>>> how can i redirect output of menuconfig to my current ssh session ?
>>>
>>> --
>>> Yahia Farghaly
>>> Graduated from Faculty of Engineering - Electronics and Communications
>>> Department at Cairo University.
>>> Linkedin  - GitHub
>>> 
>>>
>>>
>>>
>>> ‌
>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 

Aaron Schwartz
Production
Logic Supply
Direct: +1 802 861 2300 Ext. 530
Main: +1 802 861 2300
www.logicsupply.com

Google+  | Twitter
 | LinkedIn
 | YouTube

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread yahia farghaly
can you give some steps on how to do this ?


‌

On 13 September 2017 at 10:54, Yusuke Mitsuki  wrote:

> Hello
>
> You can use screen.
> If your host is ubuntu,you can get via apt as follows.
>
> sudo apt install screen.
>
> If necessary , you can set auto or screen to OE_TERMINAL environment.
>
> 2017/09/13 16:09 "yahia farghaly" :
>
>> Hi,
>>
>> I am working with yocto from a remote server using ssh. i want to execute 
>> *bitbake
>> -c menuconfig virtual/kernel*  . It fails to open since it tries to open
>> another shell.
>> how can i redirect output of menuconfig to my current ssh session ?
>>
>> --
>> Yahia Farghaly
>> Graduated from Faculty of Engineering - Electronics and Communications
>> Department at Cairo University.
>> Linkedin  - GitHub
>> 
>>
>>
>>
>> ‌
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Question about populate_sdk

2017-09-13 Thread Olaf Mandel
Hello,

I hope this is the right place to ask this: I wanted to generate an SDK
bundle to work on an applications code outside of the bitbake
environment (also without devtool, if possible). So I selected an image
containing the application and ran the populate_sdk task of that image.
But the generated SDK is missing some dependencies of the application.

Is this expected? Or am I doing something wrong?

I made a minimal demo layer that shows the problem (see below for the 7
files making up the demo). I ran "bitbake -c populate_sdk test-image"
and I expected the file usr/lib/test-lib to be present in the SDK, but
it is not.


# meta-test/conf/bblayers.conf.sample
LCONF_VERSION = "7"
BBLAYERS ?= " \
  ##OEROOT##/meta \
  ##OEROOT##/meta-test \
  "

# meta-test/conf/layer.conf
BBPATH .= ":${LAYERDIR}"
BBFILES += "${LAYERDIR}/recipes-core/*/*.bb"
BBFILE_COLLECTIONS += "test"
BBFILE_PATTERN_test = "^${LAYERDIR}/"
BBFILE_PRIORITY_test = "7"
LAYERDEPENDS_test = "core"

# meta-test/conf/local.conf.sample
CONF_VERSION = "1"
MACHINE = "qemux86-64"

# meta-test/recipes-core/images/test-image.bb
inherit core-image
IMAGE_INSTALL = "test-app"

# recipes-core/test-app/files/configure
#!/bin/sh
if [ -f "${PKG_CONFIG_SYSROOT_DIR:-}${libdir:-/usr/lib}/test-lib" ]; then
  echo "test-lib found."
else
  echo >&2 "test-lib not found!"
  exit 1
fi

# meta-test/recipes-core/test-app/test-app.bb
LICENSE = "PD"
LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/files/common-licenses/PD;md5=b3597d12946881e13cb3b548d1173851"
DEPENDS = "test-lib"
SRC_URI = "file://configure;subdir=${BPN}-${PV}"
do_configure () {
sh configure
}

# meta-test/recipes-core/test-lib/test-lib.bb
LICENSE = "PD"
do_install () {
install -d "${D}${libdir}"
touch "${D}${libdir}/test-lib"
}
FILES_${PN} = "${libdir}/test-lib"


Thank you for any suggestions,
Olaf
-- 
Olaf Mandel




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [bitbake] Failed to launch bitbake image -u -g depexp on a Debian 9 host system ?

2017-09-13 Thread Burton, Ross
On 12 September 2017 at 08:56, Karim ATIKI  wrote:

> *FATAL: Unable to import extension module "depexp" from bb.ui. Valid
> extension modules: knotty, ncurses or taskexp*
>

depexp was renamed to taskexp.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Yusuke Mitsuki
Hello

You can use screen.
If your host is ubuntu,you can get via apt as follows.

sudo apt install screen.

If necessary , you can set auto or screen to OE_TERMINAL environment.

2017/09/13 16:09 "yahia farghaly" :

> Hi,
>
> I am working with yocto from a remote server using ssh. i want to execute 
> *bitbake
> -c menuconfig virtual/kernel*  . It fails to open since it tries to open
> another shell.
> how can i redirect output of menuconfig to my current ssh session ?
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-13 Thread yahia farghaly
ok, i fixed this thanks for the note but it still gives me the error.



‌

On 13 September 2017 at 10:07, Andrea Galbusera  wrote:

>
>
> On Wed, Sep 13, 2017 at 10:04 AM, yahia farghaly 
> wrote:
>
>>
>> Thanks for replying but it gives me this error log
>>
>>
>>> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Unable to install packages.
>>> Command
>>> '/yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
>>>  install --force-yes --allow-unauthenticated run-postinsts
>>> packagegroup-core-boot kernel-modules rpi-config' returned 100:*
>>> *Reading package lists...*
>>> *Building dependency tree...*
>>> *Reading state information...*
>>> *Package rpi-config is not available, but is referred to by another
>>> package.*
>>> *This may mean that the package is missing, has been obsoleted, or**is
>>> only available from another source*
>>> *E: Package 'rpi-config' has no installation candidate*
>>>
>>> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Function failed: do_rootfs*
>>> *ERROR: Logfile of failure stored in:
>>> /yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/log.do_rootfs.2252**ERROR:
>>> Task
>>> (/yocto/poky/meta-raspberrypi/recipes-core/images/rpi-hwup-image.bb:do_rootfs)
>>> failed with exit code '1'*
>>
>>
>> All what i did is  IMAGE_INSTALL_append = "rpi-config" , the recipe file
>> is not exist in the meta-raspberry
>>
>
> You missed the space before rpi-config from the original suggestion in
> IMAGE_INSTALL_append. This is always required when overriding variables
> with _append
>
>
>>
>> ‌
>>
>> On 13 September 2017 at 09:27, Ayoub Zaki  wrote:
>>
>>> I ran into the same problem:
>>>
>>> ENABLE_UART = "1" is not enough you should also add INSTALL_append= "
>>> rpi-config" to your local.conf and Serial port will be enabled.
>>>
>>> On 12.09.2017 14:09, yahia farghaly wrote:
>>>
>>> I have bitbaked rpi-hwup-image for raspberry pi 3 on sd card and
>>> connected the serial ports to *usb to ttl device* . i have set the
>>> minicom to
>>> port: /dev/ttyUSB0
>>> baud rate: 115200
>>> the image is booting fine and i can see the prompt on the screen but
>>> cannot see in my serial console using minicom.
>>> *is serial enabled by default for this image ? *
>>> i also tried ENABLE_UART = "1" in local.conf but doesn't help.
>>>
>>> how to enable it ? and what the serial device name with respect to
>>> raspberry pi
>>>
>>> thanks,
>>>
>>> --
>>> Yahia Farghaly
>>> Graduated from Faculty of Engineering - Electronics and Communications
>>> Department at Cairo University.
>>> Linkedin  - GitHub
>>> 
>>>
>>>
>>>
>>> ‌
>>>
>>>
>>>
>>> --
>>>
>>> Ayoub Zaki
>>> Embedded Systems Consultant
>>>
>>> Vaihinger Str. 2/1
>>> 71634 Ludwigsburg
>>>
>>> e-mail: ayoub.z...@embexus.com
>>> Tel: +49176-62901545 <+49%20176%2062901545>https://embexus.com
>>>
>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>>
>> --
>> Yahia Farghaly
>> Graduated from Faculty of Engineering - Electronics and Communications
>> Department at Cairo University.
>> Linkedin  - GitHub
>> 
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-13 Thread Andrea Galbusera
On Wed, Sep 13, 2017 at 10:04 AM, yahia farghaly 
wrote:

>
> Thanks for replying but it gives me this error log
>
>
>> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Unable to install packages.
>> Command
>> '/yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
>>  install --force-yes --allow-unauthenticated run-postinsts
>> packagegroup-core-boot kernel-modules rpi-config' returned 100:*
>> *Reading package lists...*
>> *Building dependency tree...*
>> *Reading state information...*
>> *Package rpi-config is not available, but is referred to by another
>> package.*
>> *This may mean that the package is missing, has been obsoleted, or**is
>> only available from another source*
>> *E: Package 'rpi-config' has no installation candidate*
>>
>> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Function failed: do_rootfs*
>> *ERROR: Logfile of failure stored in:
>> /yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/log.do_rootfs.2252**ERROR:
>> Task
>> (/yocto/poky/meta-raspberrypi/recipes-core/images/rpi-hwup-image.bb:do_rootfs)
>> failed with exit code '1'*
>
>
> All what i did is  IMAGE_INSTALL_append = "rpi-config" , the recipe file
> is not exist in the meta-raspberry
>

You missed the space before rpi-config from the original suggestion in
IMAGE_INSTALL_append. This is always required when overriding variables
with _append


>
> ‌
>
> On 13 September 2017 at 09:27, Ayoub Zaki  wrote:
>
>> I ran into the same problem:
>>
>> ENABLE_UART = "1" is not enough you should also add INSTALL_append= "
>> rpi-config" to your local.conf and Serial port will be enabled.
>>
>> On 12.09.2017 14:09, yahia farghaly wrote:
>>
>> I have bitbaked rpi-hwup-image for raspberry pi 3 on sd card and
>> connected the serial ports to *usb to ttl device* . i have set the
>> minicom to
>> port: /dev/ttyUSB0
>> baud rate: 115200
>> the image is booting fine and i can see the prompt on the screen but
>> cannot see in my serial console using minicom.
>> *is serial enabled by default for this image ? *
>> i also tried ENABLE_UART = "1" in local.conf but doesn't help.
>>
>> how to enable it ? and what the serial device name with respect to
>> raspberry pi
>>
>> thanks,
>>
>> --
>> Yahia Farghaly
>> Graduated from Faculty of Engineering - Electronics and Communications
>> Department at Cairo University.
>> Linkedin  - GitHub
>> 
>>
>>
>>
>> ‌
>>
>>
>>
>> --
>>
>> Ayoub Zaki
>> Embedded Systems Consultant
>>
>> Vaihinger Str. 2/1
>> 71634 Ludwigsburg
>>
>> e-mail: ayoub.z...@embexus.com
>> Tel: +49176-62901545 <+49%20176%2062901545>https://embexus.com
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-13 Thread yahia farghaly
Thanks for replying but it gives me this error log


> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Unable to install packages.
> Command
> '/yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
>  install --force-yes --allow-unauthenticated run-postinsts
> packagegroup-core-boot kernel-modules rpi-config' returned 100:*
> *Reading package lists...*
> *Building dependency tree...*
> *Reading state information...*
> *Package rpi-config is not available, but is referred to by another
> package.*
> *This may mean that the package is missing, has been obsoleted, or**is
> only available from another source*
> *E: Package 'rpi-config' has no installation candidate*
>
> *ERROR: rpi-hwup-image-1.0-r0 do_rootfs: Function failed: do_rootfs*
> *ERROR: Logfile of failure stored in:
> /yocto/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/log.do_rootfs.2252**ERROR:
> Task
> (/yocto/poky/meta-raspberrypi/recipes-core/images/rpi-hwup-image.bb:do_rootfs)
> failed with exit code '1'*


All what i did is  IMAGE_INSTALL_append = "rpi-config" , the recipe file is
not exist in the meta-raspberry

‌

On 13 September 2017 at 09:27, Ayoub Zaki  wrote:

> I ran into the same problem:
>
> ENABLE_UART = "1" is not enough you should also add INSTALL_append= "
> rpi-config" to your local.conf and Serial port will be enabled.
>
> On 12.09.2017 14:09, yahia farghaly wrote:
>
> I have bitbaked rpi-hwup-image for raspberry pi 3 on sd card and connected
> the serial ports to *usb to ttl device* . i have set the minicom to
> port: /dev/ttyUSB0
> baud rate: 115200
> the image is booting fine and i can see the prompt on the screen but
> cannot see in my serial console using minicom.
> *is serial enabled by default for this image ? *
> i also tried ENABLE_UART = "1" in local.conf but doesn't help.
>
> how to enable it ? and what the serial device name with respect to
> raspberry pi
>
> thanks,
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>
>
>
> --
>
> Ayoub Zaki
> Embedded Systems Consultant
>
> Vaihinger Str. 2/1
> 71634 Ludwigsburg
>
> e-mail: ayoub.z...@embexus.com
> Tel: +49176-62901545https://embexus.com
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-13 Thread Ayoub Zaki

I ran into the same problem:

ENABLE_UART = "1" is not enough you should also add INSTALL_append= " 
rpi-config" to your local.conf and Serial port will be enabled.



On 12.09.2017 14:09, yahia farghaly wrote:
I have bitbaked rpi-hwup-image for raspberry pi 3 on sd card and 
connected the serial ports to /usb to ttl device/ . i have set the 
minicom to

port: /dev/ttyUSB0
baud rate: 115200
the image is booting fine and i can see the prompt on the screen but 
cannot see in my serial console using minicom.

*is serial enabled by default for this image ? *
i also tried ENABLE_UART = "1" in local.conf but doesn't help.

how to enable it ? and what the serial device name with respect to 
raspberry pi


thanks,

--
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications 
Department at Cairo University.
Linkedin  - GitHub 





‌




--

Ayoub Zaki
Embedded Systems Consultant

Vaihinger Str. 2/1
71634 Ludwigsburg

e-mail: ayoub.z...@embexus.com
Tel: +49176-62901545
https://embexus.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread yahia farghaly
Hi,

I am working with yocto from a remote server using ssh. i want to
execute *bitbake
-c menuconfig virtual/kernel*  . It fails to open since it tries to open
another shell.
how can i redirect output of menuconfig to my current ssh session ?

-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub




‌
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed

2017-09-13 Thread yahia farghaly
i want to install festival on the target image,
it gives me this error *"ERROR: festival-2.3-r0 do_compile: oe_runmake
failed"*
i have added the meta-oe to bblayer also .

how to solve this error ?

-- 
Yahia Farghaly
Graduated from Faculty of Engineering - Electronics and Communications
Department at Cairo University.
Linkedin  - GitHub




‌
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto