[yocto] Problem bitbaking server.cpp (Iotivity) in Yocto

2017-07-12 Thread Natalia Theologou 
Hello all,


I have also sent this email to iotivity list.

I am following the template of iotivity-simple-client inside recipes-apps in 
order to bitbake my custom simple server and simple client.

The client succeeds in bitbaking but the server has the errors:


Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 1 -e MAKEFLAGS=
| arm-poky-linux-gnueabi-g++  -march=armv7-a -mthumb-interwork -mfloat-abi=hard 
-mfpu=neon -mtune=cortex-a9 -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed 
--sysroot=/home/natalia/Downloads/release-bsp/build/tmp/sysroots/imx6dlsabreauto
  -O2 -pipe -g -feliminate-unused-debug-types -fvisibility-inlines-hidden   -c 
-o nickserver.o nickserver.cpp
| In file included from 
/home/natalia/Downloads/release-bsp/build/tmp/sysroots/imx6dlsabreauto/usr/include/c++/mutex:35:0,
|  from nickserver.cpp:34:
| 
/home/natalia/Downloads/release-bsp/build/tmp/sysroots/imx6dlsabreauto/usr/include/c++/bits/c++0x_warning.h:32:2:
 error: #error This file requires compiler and library support for the ISO C++ 
2011 standard. This support is currently experimental, and must be enabled with 
the -std=c++11 or -std=gnu++11 compiler options.
|  #error This file requires compiler and library support for the \
|   ^
| nickserver.cpp:38:19: fatal error: OCApi.h: No such file or directory
|  #include 
|^
| compilation terminated.
| make: *** [nickserver.o] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/natalia/Downloads/release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/iotivity-nick-server/1.0-r0/temp/log.do_compile.26572)
ERROR: Task 6 
(/home/natalia/Downloads/release-bsp/sources/meta-oic/recipes-apps/iotivity-nick-server/iotivity-nick-server.bb,
 do_compile) failed with exit code '1'



My .bb file is as follows:



SUMMARY = "Iotivity Simple server"
DESCRIPTION = "Iotivity Simple server example which talks to the Simple Server 
example."
HOMEPAGE = "https://www.iotivity.org/";
DEPENDS = "iotivity"
SECTION = "apps"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = 
"file://nickserver.cpp;beginline=1;endline=19;md5=fc5a615cf1dc3880967127bc853b3e0c"

SRC_URI = "file://iotivity-nick-server.tar.gz \
  "

S = "${WORKDIR}/iotivity-nick-server"

TARGET_CC_ARCH += "${LDFLAGS}"

IOTIVITY_BIN_DIR = "/opt/iotivity"
IOTIVITY_BIN_DIR_D = "${D}${IOTIVITY_BIN_DIR}"

do_install() {
install -d ${IOTIVITY_BIN_DIR_D}/apps/iotivity-nick-server
install -c -m 555 ${S}/nickserver 
${IOTIVITY_BIN_DIR_D}/apps/iotivity-nick-server
install -c -m 444 ${S}/oic_svr_db_server.dat 
${IOTIVITY_BIN_DIR_D}/apps/iotivity-nick-server
}

FILES_${PN} = "${IOTIVITY_BIN_DIR}/apps/iotivity-nick-server/nickserver \
   
${IOTIVITY_BIN_DIR}/apps/iotivity-nick-server/oic_svr_db_server.dat"
FILES_${PN}-dbg = "${IOTIVITY_BIN_DIR}/apps/iotivity-nick-server/.debug"
RDEPENDS_${PN} += "iotivity-resource"
BBCLASSEXTEND = "native nativesdk"

and my makefile:


YOCTOCXXFLAGS=-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/ 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/stack 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/ocrandom 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/logger 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/oc_logger

YOCTOLDFLAGS=-loc -loctbstack -loc_logger

all: nickserver

nickserveroff.o: nickserver.cpp
ifeq ($(PKG_CONFIG_SYSROOT_DIR),)
echo "Error: Yocto cross-toolchain environment not initialized"
exit 1
endif
$(CXX) -std=c++0x -c -o $@ $< $(YOCTOCXXFLAGS)

nickserver: nickserver.o
$(CXX) -o nickserver nickserver.o $(YOCTOLDFLAGS)

clean:
rm -rf nickserver *.o



I have -std=c++0x in the makefile which is the same  as -std=c++11, so I don't 
know why it has the error: #error This file requires compiler and library 
support for the ISO C++ 2011 standard. This support is currently experimental, 
and must be enabled with the -std=c++11 or -std=gnu++11 compiler.

Also the client succeded in bitbaking and it has the same makefile and the same 
.bb recipe.

Has anyone any idea regarding this?


Thank you in advance!


Best,
Natalia

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

Re: [yocto] Determining Load Addresses

2017-07-12 Thread Leonardo Sandoval 
On Wed, 2017-07-12 at 05:23 +, Kenny Koller wrote:
> I'm trying to piece together the various load addresses used in the
> boot sequence. I have built core-image-minimal for a Beaglebone. How
> can I determine which load address and entry point is used when
> mkimage is called for the kernel? Should I dig in to the recipe?
> Search some log files? I've tried a few difference things without
> results.
> 
> 
This type of info usually comes in the machine definition, thus look
there. Diong a simple git grep ^UBOOT shows the following related
variables

meta/conf/documentation.conf:UBOOT_ENTRYPOINT[doc] = "Specifies the
entry point for the U-Boot image."
meta/conf/documentation.conf:UBOOT_LOADADDRESS[doc] = "Specifies the
load address for the U-Boot image."



> Thanks.
> -- 
> ___
> 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] Release Candidate Build for yocto-2.3.1.rc1 now available

2017-07-12 Thread Michael Halstead 
A release candidate build for yocto-2.3.1.rc1 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1


Please begin QA on this build as soon as possible.


Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit:
git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com
" | sendmail -t
 in dir /home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build
(timeout 10 secs)
 watching logfiles {}
 argv: echo "To: yocto@yoctoproject.org
Cc: pi...@toganlabs.com, jose.perez.carra...@intel.com,
libertad.c...@intel.com, ota...@ossystems.com.br, yi.z...@windriver.com,
tracy.gray...@intel.com, joshua.g.l...@intel.com
Subject: Release Candidate Build for yocto-2.3.1.rc1 now available.


A release candidate build for yocto-2.3.1.rc1 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1


Please begin QA on this build as soon as possible.


Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f


-- 
Michael Halstead
Linux Foundation / SysAdmin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

2017-07-12 Thread Perez Carranza, Jose 
Hi Michael

You sent the mail for rc1 and there is an rc2 available, according to RP rc2 is 
the one that will be used for QA. 

Regards,
José


-Original Message-
From: Michael Halstead [mailto:mhalst...@linuxfoundation.org] 
Sent: Wednesday, July 12, 2017 11:38 AM
To: pi...@toganlabs.com; Perez Carranza, Jose ; 
Cruz, Libertad ; ota...@ossystems.com.br; Zhao, Yi 
(Wind River) ; Graydon, Tracy ; 
Lock, Joshua G ; yocto@yoctoproject.org
Subject: Release Candidate Build for yocto-2.3.1.rc1 now available

A release candidate build for yocto-2.3.1.rc1 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1


Please begin QA on this build as soon as possible.


Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit:
git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com " | 
sendmail -t  in dir /home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build
(timeout 10 secs)
 watching logfiles {}
 argv: echo "To: yocto@yoctoproject.org
Cc: pi...@toganlabs.com, jose.perez.carra...@intel.com, 
libertad.c...@intel.com, ota...@ossystems.com.br, yi.z...@windriver.com, 
tracy.gray...@intel.com, joshua.g.l...@intel.com
Subject: Release Candidate Build for yocto-2.3.1.rc1 now available.


A release candidate build for yocto-2.3.1.rc1 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1


Please begin QA on this build as soon as possible.


Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f


--
Michael Halstead
Linux Foundation / SysAdmin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

2017-07-12 Thread Michael Halstead 
The RC2 e-mail should arrive shortly. It was sent the normal way, directly
by the autobuilder.

On Wed, Jul 12, 2017 at 10:03 AM, Perez Carranza, Jose <
jose.perez.carra...@intel.com> wrote:

> Hi Michael
>
> You sent the mail for rc1 and there is an rc2 available, according to RP
> rc2 is the one that will be used for QA.
>
> Regards,
> José
>
>
> -Original Message-
> From: Michael Halstead [mailto:mhalst...@linuxfoundation.org]
> Sent: Wednesday, July 12, 2017 11:38 AM
> To: pi...@toganlabs.com; Perez Carranza, Jose <
> jose.perez.carra...@intel.com>; Cruz, Libertad ;
> ota...@ossystems.com.br; Zhao, Yi (Wind River) ;
> Graydon, Tracy ; Lock, Joshua G <
> joshua.g.l...@intel.com>; yocto@yoctoproject.org
> Subject: Release Candidate Build for yocto-2.3.1.rc1 now available
>
> A release candidate build for yocto-2.3.1.rc1 is now available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
>
>
> Please begin QA on this build as soon as possible.
>
>
> Build hash information:
> meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
> meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
> refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
> meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
> meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
> meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
> poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
>
> \nThis is an automated message from\nThe Yocto Project Autobuilder\nGit:
> git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com
> " | sendmail -t  in dir /home/pokybuild/yocto-autobuilder/yocto-worker/
> nightly/build
> (timeout 10 secs)
>  watching logfiles {}
>  argv: echo "To: yocto@yoctoproject.org
> Cc: pi...@toganlabs.com, jose.perez.carra...@intel.com,
> libertad.c...@intel.com, ota...@ossystems.com.br, yi.z...@windriver.com,
> tracy.gray...@intel.com, joshua.g.l...@intel.com
> Subject: Release Candidate Build for yocto-2.3.1.rc1 now available.
>
>
> A release candidate build for yocto-2.3.1.rc1 is now available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
>
>
> Please begin QA on this build as soon as possible.
>
>
> Build hash information:
> meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
> meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
> refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
> meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
> meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
> meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
> poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
>
>
> --
> Michael Halstead
> Linux Foundation / SysAdmin
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Release Candidate Build for yocto-2.3.1.rc2 now available.

2017-07-12 Thread Poky Build User 

A release candidate build for yocto-2.3.1.rc2 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc2


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d 
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd 
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6 
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6 
poky : 6bd890d9e011014cf323e61267f8b256949d44aa 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: 
git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] setting security attributes to device file(/dev/ipc)

2017-07-12 Thread Kumar, Shrawan 
Hello Team ,

I want to set ACL and SMACK/SELinux rules to device files (line /dev/ipc2  
/dev/galcore etc .. )   from the build system . But device files are 
dynamically populated at runtime.

Do we have some way in "Yocto"  to achieve the goal  ?



Thanks & Regards
Shrawan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Determining Load Addresses

2017-07-12 Thread Robert Berger 

Hi,

On 2017-07-12 08:23, Kenny Koller wrote:
I'm trying to piece together the various load addresses used in the boot 
sequence. I have built core-image-minimal for a Beaglebone. How can I 
determine which load address and entry point is used when mkimage is 
called for the kernel? Should I dig in to the recipe? Search some log 
files? I've tried a few difference things without results.


You don't need to bake a board specific address into uImage.

Like this you could create an uImage without a baked in address. Check 
here between lines 98 and 112


https://github.com/RobertBerger/meta-mainline/blob/pyro-training-v4.9.x/multi-v7-ml/conf/machine/multi-v7-ml.conf#L98




Thanks.




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

[yocto] RPi fails when build is with deb packages works okay with rpm packages.

2017-07-12 Thread Edward Vidal 
Hello All,Does anyone know if recipes are available for 
gcc-arm-none-eabi & binutils-arm-none-eabi?

My build works okay when I use package_rpm and fails with package_deb.
My bblayers.conf & local.conf are at 
https://github.com/develone/raspberrypi2_yocto/tree/master/poky2.2/raspberrypi2/conf_files
Any and all help is appreciated.


Parsing recipes: 100% |##| Time: 0:00:46
~/wkg/yocto/RaspberryPi2/poky/build$ diff conf/local.conf 
~/wkg/raspberrypi2_yocto/poky2.2/raspberrypi2/conf_files/local.conf 
124c124
< PACKAGE_CLASSES ?= "package_deb"
---
> PACKAGE_CLASSES ?= "package_rpm"

Parsing of 1931 .bb files complete (0 cached, 1931 parsed). 2616 targets, 170 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION    = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-16.04"
TARGET_SYS    = "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi2"
DISTRO    = "poky"
DISTRO_VERSION    = "2.2"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
cortexa7"
TARGET_FPU    = "hard"
meta  
meta-poky 
meta-yocto-bsp    = "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c"
meta-raspberrypi  = "master:6bd1bfe472ea491c0edeb7c854d1c0cc5192afeb"
meta-oe   
meta-python   
meta-multimedia   
meta-gnome    = "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c"
meta-browser  = "master:1edcce7791b4cee9a515c1f11b351753a4f8b12e"

Initialising tasks: 100% |###| Time: 0:00:19
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks

ERROR: core-image-sato-1.0-r0 do_rootfs: Unable to install packages. Command 
'/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/x86_64-linux/usr/bin/apt-get
  install --force-yes --allow-unauthenticated opencv xchat gsl 
packagegroup-base-extended psplash-raspberrypi libftdi1-2 libgtk-3.0 apt geany 
libmad0 texinfo pv minicom cmake libmtp9 python-pip ghostscript 
packagegroup-core-sdk python-imaging git dpkg tcl v4l-utils yasm 
packagegroup-core-ssh-dropbear rsync linux-firmware lame gtkmm 
packagegroup-core-x11-base packagegroup-core-x11-sato iproute2 gperf liba52-0 
iputils vlc packagegroup-core-boot packagegroup-core-standalone-sdk-target 
packagegroup-core-x11-sato-games tk xterm squashfs-tools gnuplot tar chkconfig 
openjpeg tree man libgtk-2.0' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 packagegroup-core-x11-base : Depends: packagegroup-core-x11-utils but it is 
not going to be installed
 vlc : Depends: libgl-mesa (>= 12.0.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

ERROR: core-image-sato-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.2105
ERROR: Task 
(/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-sato/images/core-image-sato.bb:do_rootfs)
 failed with exit code '1'



Thanks in advance.

Cheers,

 Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Help With TEMPLATECONF & Automated Continuous Integration (CI)

2017-07-12 Thread Thomas A. F. Thorne MEng AUS MIET 
Good morning,

I am trying to setup an automate Jenkins CI server to build an image. 
To do this I need to automate the process of setting up the Yocto work
area completely.  As part of this process I am trying to eliminate the
use of or automate the production of local.conf and bblayers.conf
files.  It is working out how to deal with the selection of layers to
include that I am having difficulty with right now. 

_TEMPLATECONF_
In the documentation I have found a reference to the .templateconf file
which can be edited to set the TEMPLATECONF variable to point at a set
of templates for the local.conf and bblayers.conf files.  I suppose I
could somehow overwrite any existing .templateconf file with my own
version copied from somewhere but that seems a little messy when all the
other files are checked out of source control and manipulated only via
bitbake.  I wonder if a TEMPLATECONF environment variable would be
picked up as that would feel a little tidier to me, I shall experiment
after lunch. 

_What I Have Working_
The top level work area is formed using the Gerrit Repo tool.  This
gives me the basic set of core layers and my proprietary layer
(imaginatively named meta-net2edge).  Jenkins is able to operate repo as
it can other SCM options. 

I think I have eliminated the need to a hand crafted local.conf file
already.  I have a proprietary Yocto Board Support Package (BSP) a
costume Image Class and a set of packagegroups added to image using
IMAGE_INSTALL.  With the target MACHINE set using an environment
variable on the call to `source oe-init-build-env` there is no need to
hand craft the local.conf. 

_General Questions_
I also feel like I may have missed some documentation or instruction
that discusses going from prototyping in local.conf and bblayers.conf to
a more formal production system that minimises their use.  The
documentation for creating BSPs is good.  The documentation for creating
distributions and feature packages is a little weak in places.  Maybe I
am wrongly expecting structure where Yocto tries to be flexible. 
Am I just overcomplicating things by trying to minimise the work any one
user or machine needs to do besides checking out the work area with repo? 
How do other people perform CI or continuous delivery for their Yocto
targets?

Any help or advice would be most gratefully received. 

Regards,

-- 
Thomas A. F. Thorne MEng. AUS MIET
*Software Engineer*

*NET2EDGE*

Tel: +44 3450 130 030 
Email: thomas.tho...@net2edge.com 
Web: http://www.Net2Edge.com/ 

Net2Edge Limited is a company registered in England & Wales (Company No.
2438435, VAT No. GB 537553821) Kulite House, Stroudley Road, Basingstoke
RG24 8UG. This email transmission is confidential and intended solely
for the person or organisation to whom it is addressed (i.e. the Yocto
public community mailgroupin this case). If you are not the intended
recipient, you must not copy, distribute or disseminate the information,
or take any action in reliance of it. Any views expressed in this
message are those of the individual sender, except where the sender
specifically states them to be the views of any organisation or
employer. If you have received this message in error, do not open any
attachment but please notify the sender (above) and delete this message
from your system. Please rely on your own virus check. Although all
outbound mail is checked for viruses, no responsibility is taken by the
sender for any damage rising out of any bug or virus infection.



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

[yocto] [ARM][Renesas Salvator x Board R-car] PERF events support

2017-07-12 Thread george emad 
Hello All ,

I want to ask if anyone managed to Run the PERF tool utilities that depends on 
the "perf events" as i have problem
finding the path "/sys/kernel/debug/tracing/events" in my build even after 
configuring all the necessary options and recipes and many tries.


some information about my system :
- salvator x board M3
-Renesas Yocto Version tested 2.9 And 2.16



Thank you in Advance

Best Regards,

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

Re: [yocto] Wifi on wandboard with Yoct0 Morty

2017-07-12 Thread Umamahesh Yelchuruvenkata 



Hello All,
Could you help me in resolving the following issue in Yocto Morty for wifi

Enabled the drivers,

<*> Broadcom FullMAC wireless cards support │ │ 
│ │ [*] SDIO bus interface support 

At the target getting following errors,

root@wandboard:~# dmesg | grep brcm
[ 1.739333] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.bin failed with error -2
[ 1.748200] brcmfmac_sdio mmc1:0001:1: Falling back to user helper
[ 62.783879] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
[ 63.793963] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
root@wandboard:~# 





From: Umamahesh Yelchuruvenkata
Sent: 07 July 2017 16:02
To: Ayoub Zaki; yocto@yoctoproject.org
Subject: RE: [yocto] Wifi on wandboard with Yoct0 Morty




Please check the dmesg log posted, how to overcome the issue. Do you have procedure how to compile for meta-freescale and meta-freescale-3rdparty layers.


From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] on behalf of Ayoub Zaki [ayoub.z...@embexus.com]
Sent: 07 July 2017 13:35
To: yocto@yoctoproject.org
Subject: Re: [yocto] Wifi on wandboard with Yoct0 Morty




Fo wandboard I use meta-freescale and meta-freescale-3rdparty layers.
Wifi works out of the box :-)


On 07.07.2017 09:59, Umamahesh Yelchuruvenkata wrote:


Hi 
I am trying to bring up Wifi on wandboard Rev C1 and using Yocto Morty version(2.2.2) , I downloaded the firmware bin files from following


wget -c 
https://git.kernel.org/cgit/linux/kerne ... 0-sdio.bin
wget -c 
https://rcn-ee.com/repos/git/meta-fsl-a ... 0-sdio.txt

Created a folder firmware/brcm under tmp/work/wandboard-fslc-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/lib

Enabled the drivers,

<*> Broadcom FullMAC wireless cards support │ │ 
│ │ [*] SDIO bus interface support 

At the target getting following errors,

root@wandboard:~# dmesg | grep brcm
[ 1.739333] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.bin failed with error -2
[ 1.748200] brcmfmac_sdio mmc1:0001:1: Falling back to user helper
[ 62.783879] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
[ 63.793963] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
root@wandboard:~# 


Please suggest



::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,

lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents

(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.

Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the

views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,

distribution and / or publication of this message without the prior written consent of authorized representative of

HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

Before opening any email and/or attachments, please check them for viruses and other defects.


 


-- 

Ayoub Zaki

ayoub.z...@embexus.com
Mobile: +49(0)176-62901545
Skype: ayoub.zaki_2
https://embexus.com








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