Re: [yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed
failure stored in: > /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/temp/log.do_package_qa.111098* > *ERROR: Task > (/yocto/poky/meta-ros/recipes-extended/speech-tools/speech-tools_2.3.bb:do_package_qa) > failed with exit code '1'**NOTE: Tasks Summary: Attempted 2083 tasks of > which 2081 didn't need to be rerun and 2 failed.* > > *Summary: 2 tasks failed:* > * > /yocto/poky/meta-ros/recipes-extended/festival/festival_2.3.bb:do_compile* > * > /yocto/poky/meta-ros/recipes-extended/speech-tools/speech-tools_2.3.bb:do_package_qa**Summary: > There were 5 ERROR messages shown, returning a non-zero exit code.* On 13 September 2017 at 18:15, yahia farghaly <yahiafargh...@gmail.com> wrote: > 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 <yahiafargh...@gmail.com> > 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 <https://linkedin.com/in/yahiafarghaly> - GitHub >> <https://github.com/yahiafarghaly> >> >> >> >> >> > > > > -- > Yahia Farghaly > Graduated from Faculty of Engineering - Electronics and Communications > Department at Cairo University. > Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub > <https://github.com/yahiafarghaly> > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ 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
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 <yahiafargh...@gmail.com> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub > <https://github.com/yahiafarghaly> > > > > > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer
thanks for the note. On 13 September 2017 at 16:53, Martin Jansa <martin.ja...@gmail.com> 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 <yahiafargh...@gmail.com> > 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 <https://linkedin.com/in/yahiafarghaly> - GitHub >> <https://github.com/yahiafarghaly> >> >> >> >> >> >> -- >> ___ >> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer
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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to execute bitbake menuconfig from ssh server
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 <ajlen...@dynamicdevices.co.uk> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to execute bitbake menuconfig from ssh server
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 <ajlen...@dynamicdevices.co.uk> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to execute bitbake menuconfig from ssh server
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" <yahiafargh...@gmail.com>: > >> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub >> <https://github.com/yahiafarghaly> >> >> >> >> >> >> -- >> ___ >> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] enable serial communication pi 3
ok, i fixed this thanks for the note but it still gives me the error. On 13 September 2017 at 10:07, Andrea Galbusera <giz...@gmail.com> wrote: > > > On Wed, Sep 13, 2017 at 10:04 AM, yahia farghaly <yahiafargh...@gmail.com> > 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 <ayoub.z...@embexus.com> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub >>> <https://github.com/yahiafarghaly> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub >> <https://github.com/yahiafarghaly> >> >> -- >> ___ >> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] enable serial communication pi 3
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 <ayoub.z...@embexus.com> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub > <https://github.com/yahiafarghaly> > > > > > > > > -- > > 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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] how to execute bitbake menuconfig from ssh server
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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed
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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] enable serial communication pi 3
:( On 12 September 2017 at 14:09, yahia farghaly <yahiafargh...@gmail.com> 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 <https://linkedin.com/in/yahiafarghaly> - GitHub > <https://github.com/yahiafarghaly> > > > > > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] enable serial communication pi 3
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 <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] Could not inherit file classes/pypi.bbclass
ok,thanks it is now building. i have another question, i don't need to use the meta-gstreamer1.0 layer if i will use the gstreamer in your multimedia layer with *IMAGE_INSTALL_append = gstreamer ?* On 11 September 2017 at 13:58, Andrei Gherzan <and...@gherzan.ro> wrote: > > > On 11 Sep 2017 12:51, "yahia farghaly" <yahiafargh...@gmail.com> wrote: > > i cloned the latest pyro version with meta-raspberry pi . i added > meta-raspberrypi to bblayer and adjust the machine ?= "raspberry pi" when i > bitbake rpi-hwup-image*.* > > it throws me the error of > *ERROR: ParseError at > /home/yahia/Desktop/elinux_dev/bake_factory/git_versions/poky/meta-raspberrypi/recipes-devtools/python/rpi-gpio_0.6.3.bb:8 > <http://rpi-gpio_0.6.3.bb:8>: Could not inherit file classes/pypi.bbclass* > > > There is a dependency in the README which you missed in the bblayers. > Namely meta-python. > -- > Andrei Gherzan > gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] Could not inherit file classes/pypi.bbclass
i cloned the latest pyro version with meta-raspberry pi . i added meta-raspberrypi to bblayer and adjust the machine ?= "raspberry pi" when i bitbake rpi-hwup-image*.* it throws me the error of *ERROR: ParseError at /home/yahia/Desktop/elinux_dev/bake_factory/git_versions/poky/meta-raspberrypi/recipes-devtools/python/rpi-gpio_0.6.3.bb:8 <http://rpi-gpio_0.6.3.bb:8>: Could not inherit file classes/pypi.bbclass* -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to submit a patch
i found it in pyro docs, never mind <https://mailtrack.io/> Sent with Mailtrack <https://mailtrack.io/install?source=signature=en=yahiafargh...@gmail.com=22> On 8 September 2017 at 14:11, yahia farghaly <yahiafargh...@gmail.com> wrote: > How to submit a patch in yocto ? i come across this link for open embedded > https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded > should i follow it ? or there is something else? . more specifically, my > patch will be in pyro branch > > Thanks, > > > > -- > Yahia Farghaly > Graduated from Faculty of Engineering - Electronics and Communications > Department at Cairo University. > Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub > <https://github.com/yahiafarghaly> > > > > > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] how to submit a patch
How to submit a patch in yocto ? i come across this link for open embedded https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded should i follow it ? or there is something else? . more specifically, my patch will be in pyro branch Thanks, -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] initscript with yocto
Hi, Can someone provide me with a working example of using both rc.local and systemd for executing shell commands at startup. I tried systemd as explained here but it didn't work ( https://stackoverflow.com/questions/40431674/post-install-script-on-yocto-built-linux ) Thanks, -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] modify sources.list file
Hi, I am build a deb package manager for the target image. for that i set these variables in conf/local.conf > *PACKAGE_FEED_URIS = "http:///my-repo/yahia-repo/expiremental \* > > *"* > > *PACKAGE_FEED_BASE_PATHS = "deb"* > > *PACKAGE_FEED_ARCHS = "all"* > > and as expected the result was in sources.list > *deb http:///my-repo/yahia-repo/expiremental/deb/all ./ * Now , i want to make sources.list to be like this > *deb http:///my-repo/yahia-repo/expiremental/deb/all yahia main* > is there any way in yocto to achieve this ? i tried overwriting content by an exist file on machine with install command in do_install task but it doesn't work I also tried in image recipe > ROOTFS_POSTPROCESS_COMMAND += "modifysourcelist;" > > >> modifysourcelist(){ > > install -d ${D}/etc/apt > > install -m 0755 ${THISDIR}/../addfiles/keyfile/sources.list >> ${D}/etc/apt > > } > > and it was no effect. -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] apt-key not found
Hi, I have built an image with deb package support and for authorization of the incoming packages, i have to transfer a public key to the image and do the command apt-key add . i do this for the first time the image is booting but i want to automate the process when i build the image. i have already created recipe which copy the public key to image rootfs under /deb_key/keyFile then i tried to perform apt-key command in the image recipe with ROOTFS_POSTPROCESS_COMMAND += "addkeyfile;" > > >> addkeyfile(){ > > apt-key add ${D}/deb_key/keyFile > > } > > but it gives me an error log of > >1. | NOTE: Executing empty_var_volatile ... >2. | DEBUG: Executing shell function empty_var_volatile >3. | DEBUG: Shell function empty_var_volatile finished >4. | NOTE: Executing addkeyfile ... >5. | DEBUG: Executing shell function addkeyfile >6. | > > /home/yahia/Desktop/elinux_dev/bake_factory/poky-pyro-17.0.1/build/tmp/work/qemux86_64-poky-linux/apt-image/1.0-r0/temp/run.addkeyfile.12587: >108: > > /home/yahia/Desktop/elinux_dev/bake_factory/poky-pyro-17.0.1/build/tmp/work/qemux86_64-poky-linux/apt-image/1.0-r0/temp/run.addkeyfile.12587: >apt-key: not found >7. | WARNING: exit code 127 from a shell command. >8. | DEBUG: Python function do_rootfs finished >9. | ERROR: Function failed: addkeyfile (log file is located at > > /home/yahia/Desktop/elinux_dev/bake_factory/poky-pyro-17.0.1/build/tmp/work/qemux86_64-poky-linux/apt-image/1.0-r0/temp/log.do_rootfs.12587) >10. ERROR: Task > > (/home/yahia/Desktop/elinux_dev/bake_factory/poky-pyro-17.0.1/meta-mylayer/recipes-example/images/apt-image.bb:do_rootfs) >failed with exit code '1' > > So, what the right way to do this ? Thanks, -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] error in apt-key add
I fixed it by adding coreutils recipe with the gnupg since gnupg depends on it. I will try to patch it soon. Yahia On 30 August 2017 at 10:42, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 08/29/2017 08:38 PM, yahia farghaly wrote: > >> I am building a linux image using yocto which support deb package >> manager(apt-get). I created the repo with packages and i want to authorize >> this repo to my target machine. i followed these steps < >> https://help.ubuntu.com/community/CreateAuthenticatedRepository> for >> that purpose. I created the keyFile successfully for the server (host). and >> when transfer this keyFile to my target and execute apt-key add keyFile, it >> promotes me the error >> >> /usr/bin/apt-key: line 352: comm: command not found >> i use yocto pyro 17.0.1 and i built for core-image-sato plus adding the >> recipe gnupg which exist in meta/recipes-support/gnupg >> >> Why this error ? and possible ways to fix it ? >> > > Signing and authenticating .deb repositories is not supported or tested in > Yocto. Do not take Ubuntu instructions for it, they are not relevant and > not likely to work. > > You can use .deb repostories without having them signed, or you can switch > to rpm packaging (and master branch) where signing should work. Or you can > figure out where that error comes from and fix it and create a patchset, > but it's up to you to do the investigation and fixing. > > Alex > -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] error in apt-key add
I am building a linux image using yocto which support deb package manager(apt-get). I created the repo with packages and i want to authorize this repo to my target machine. i followed these steps <https://help.ubuntu.com/community/CreateAuthenticatedRepository> for that purpose. I created the keyFile successfully for the server (host). and when transfer this keyFile to my target and execute apt-key add keyFile, it promotes me the error > /usr/bin/apt-key: line 352: comm: command not found i use yocto pyro 17.0.1 and i built for core-image-sato plus adding the recipe gnupg which exist in meta/recipes-support/gnupg Why this error ? and possible ways to fix it ? -- Yahia Farghaly Graduated from Faculty of Engineering - Electronics and Communications Department at Cairo University. Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub <https://github.com/yahiafarghaly> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto