Re: [yocto] [EXTERNAL] Re: Compilation error : No GNU_HASH in elf bianry

2017-06-28 Thread Pawar, Alok 
Hi Raj, 

I am not using any Makefile, actually I am only copying multiple binary and 
library(which are already compiled) using bb file.

Best Regards
Alok Pawar
Sr. Engineer Product Development

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: Thursday, June 29, 2017 10:21 AM
To: Pawar, Alok 
Cc: yocto@yoctoproject.org
Subject: [EXTERNAL] Re: [yocto] Compilation error : No GNU_HASH in elf bianry

On Wed, Jun 28, 2017 at 9:29 PM, Pawar, Alok  wrote:
> Hi,
>
>
>
> I am using krogoth release and I am facing one issue in custom bitbake file.
>
>
>
> When I am doing bitbake with custom bb file the following error is coming :
>
> “No GNU_HASH in the elf binary”
>
> In custom bb file, I am trying to copy precompiled binary and library.
>
> I tried also with Flag : FILES_${PN} += , but face same issue.
>

this error means you have an issue in Makefiles where linker flags are not 
being respected.

I would suggest to add CFLAGS and LDFLAGS both to linker cmdline in Makefile.

Other option is to set

TARGET_CC_ARCH += "${LDFLAGS}"

in your bb file but I would rather like to see it fixed in right place which is 
the Makefile.

>
>
> Best Regards
>
> Alok Pawar
>
> Sr. Engineer Product Development
>
> Harman Connected Services
>
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://clicktime.symantec.com/a/1/KmDUgKYmGtGWoFjtvLywehOB3j7J_v0-QB3
> RBcIFFrY=?d=376g77TeeW532rZh2Wu03kKk9048zWevkFXyWLaxfc2Mym07eRMyv6qekUBZ8dojsxaRg8GHDWQerzJnxzrWFudZ89GDPBM2OCgRwdVrijXugVocnXKaL9uIeHpWjfqfETpZRI0NFwsOn41_dChURQ1f91zfSu8_sm0tk_Ho116AhWPL4uaTC-Hq3eZqJa4CB0B_ulI6sekYyXygHA4PGznxIHhuMHprFn15Uo37UORgfpVzzBrzHhrsIi-VdhiRr9Z4ThMHNXCIFSsvehqTO3tcKGOkXCN8SmHL8bVeix3w4cCU_O_FMEiWqYEILaLTX9zMAa1FTHAEbyoL7t-fpcfM2F40ypDkNPKjmPCvsQgjac85F-pb4IGzsXmdOB7e4zuJX-evKFtmPITwikHYU7sNAW3tYJWuL9yqKauhSpQE6g%3D%3D=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compilation error : No GNU_HASH in elf bianry

2017-06-28 Thread Khem Raj 
On Wed, Jun 28, 2017 at 9:29 PM, Pawar, Alok  wrote:
> Hi,
>
>
>
> I am using krogoth release and I am facing one issue in custom bitbake file.
>
>
>
> When I am doing bitbake with custom bb file the following error is coming :
>
> “No GNU_HASH in the elf binary”
>
> In custom bb file, I am trying to copy precompiled binary and library.
>
> I tried also with Flag : FILES_${PN} += , but face same issue.
>

this error means you have an issue in Makefiles where
linker flags are not being respected.

I would suggest to add CFLAGS and LDFLAGS both to
linker cmdline in Makefile.

Other option is to set

TARGET_CC_ARCH += "${LDFLAGS}"

in your bb file but I would rather like to see it fixed in
right place which is the Makefile.

>
>
> Best Regards
>
> Alok Pawar
>
> Sr. Engineer Product Development
>
> Harman Connected Services
>
>
>
>
>
>
> --
> ___
> 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] Compilation error : No GNU_HASH in elf bianry

2017-06-28 Thread Pawar, Alok 
Hi,

I am using krogoth release and I am facing one issue in custom bitbake file.

When I am doing bitbake with custom bb file the following error is coming :
"No GNU_HASH in the elf binary"
In custom bb file, I am trying to copy precompiled binary and library.
I tried also with Flag : FILES_${PN} += , but face same issue.

Best Regards
Alok Pawar
Sr. Engineer Product Development
Harman Connected Services


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

[yocto] [meta-chip][PATCH V3 4/4] chip: Add chip-u-boot-scr recipe and flash script

2017-06-28 Thread drew . moseley 
From: Drew Moseley 

Add a U-Boot script to handle flashing the SPL, U-Boot
and UBI root filesystem images into the onboard flash.
Also generate a script showing how to execute the flash
steps.

Signed-off-by: Drew Moseley 
---
 README  | 91 -
 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb  | 89 
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full | 32 +
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in   | 43 
 recipes-bsp/u-boot/u-boot-chip_git.bb   |  1 +
 5 files changed, 255 insertions(+), 1 deletion(-)
 create mode 100644 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in

diff --git a/README b/README
index 32f70b2..9fc1dd1 100644
--- a/README
+++ b/README
@@ -62,4 +62,93 @@ To build a machine supported by this BSP layer follow the 
next steps:
 II. Flashing a C.H.I.P. board
 
 
-
+As part of the build including this BSP layer, a U-Boot script and a
+shell script are created to assist in flashing your images to the CHIP
+board. Note that this script assumes a maximum size for your UBI
+image of 167772160 (0x0A00) bytes. If your UBI image exceeds
+that, then you will need to adapt this to your environment.
+
+To successfully run this script you will first need to set your board
+into FEL mode. Insert a wire into the U14 header between pin 7 (FEL)
+and GND. Then connect the board with a USB cable to your host. More
+details here:
+https://docs.getchip.com/chip.html#flash-chip-with-an-os
+
+You need to specify the base filename of your UBI image using the
+UBI_IMAGE shell variable before invoking the generated script as
+follows:
+
+# UBI_IMAGE=chip-hwup-image-chip.ubi \
+./tmp/deploy/images/chip/flash_CHIP_board.sh
+
+This script will take some time to execute. The output of this script
+as run on your host machine should look similar to the following:
+
+# UBI_IMAGE=chip-hwup-image-chip.ubi 
./tmp/deploy/images/chip/flash_CHIP_board.sh
+100% []  3537 kB,  513.9 
kB/s
+100% []   619 kB,  551.1 
kB/s
+100% [] 2 kB,  476.0 
kB/s
+100% [] 71303 kB,  531.1 
kB/s
+
+If you have a serial console connected to your board, you will see
+progress and a message on the console indicating when flashing is
+complete:
+
+U-Boot 2016.01 (Jun 20 2017 - 02:54:42 -0400) Allwinner Technology
+
+CPU:   Allwinner A13 (SUN5I)
+I2C:   ready
+DRAM:  512 MiB
+NAND:  8192 MiB
+video-mode 720x480-24@60 not available, falling back to 1024x768-24@60
+Setting up a 720x480i composite-ntsc console (overscan 40x20)
+In:serial
+Out:   serial
+Err:   serial
+Net:   usb_ether
+starting USB...
+No controllers found
+Hit any key to stop autoboot:  0
+(FEL boot)
+## Executing script at 4310
+Erasing NAND
+
+NAND erase.chip: device 0 whole chip
+Skipping bad block at  0xeb00
+Skipping bad block at  0x1b100
+Erasing at 0x1ffc0 -- 100% complete.
+OK
+Writing SPL (with ECC) to NAND address 0x
+
+NAND write:  3537408 bytes written: OK
+Writing SPL (with ECC) to NAND address 0x40
+
+NAND write:  3537408 bytes written: OK
+Writing UBoot image to address 0x80
+
+NAND write: device 0 offset 0x80, size 0x97236
+ 619062 bytes written: OK
+Enabling Splash
+Setting Video Mode
+Saving default environment
+Saving Environment to NAND...
+Erasing NAND...
+Erasing at 0xc0 -- 100% complete.
+Writing to NAND... OK
+Writing UBI rootfs to NAND address 0x100
+
+NAND write: device 0 offset 0x100, size 0xa00
+ 167772160 bytes written: OK
+===
+Flashing Complete. Please power down and disable FEL mode.
+===
+
+Additionally, once the image is properly flashed, the status LED on
+the CHIP board will flash on and off every 2 seconds. This indicates
+that it is safe to power down your board and disable FEL mode.
+
+WARNING: This will erase the entire contents of your CHIP board.
+
+NOTE: This setup is still compatible with the CHIP flashing utility
+available at http://flash.getchip.com if you choose to reinstall the
+stock images.
diff --git a/recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb 
b/recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
new file mode 100644
index 000..6945c42
--- /dev/null
+++ b/recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
@@ -0,0 +1,89 @@

[yocto] [meta-chip][PATCH V3 3/4] chip: Build sunxi-tools-native.

2017-06-28 Thread drew . moseley 
From: Drew Moseley 

Add LAYERDEPENDS on meta-sunxi and add the sunxi-tools-native
pacakage to EXTRA_IMAGEDEPENDS.

Signed-off-by: Drew Moseley 
---
 README | 3 +++
 conf/layer.conf| 3 +++
 conf/machine/chip.conf | 2 +-
 3 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/README b/README
index cccf59e..32f70b2 100644
--- a/README
+++ b/README
@@ -14,6 +14,9 @@ This layer depends on:
   layers: meta
   branch: master
 
+  URI: git://github.com/linux-sunxi/meta-sunxi.git
+  branch: master
+
 
 Patches
 ===
diff --git a/conf/layer.conf b/conf/layer.conf
index 5dad66e..1f34ea0 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -8,3 +8,6 @@ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 BBFILE_COLLECTIONS += "meta-chip"
 BBFILE_PATTERN_meta-chip = "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-chip = "6"
+
+# Add this to get access to sunxi-tools recipe
+LAYERDEPENDS_meta-chip = "meta-sunxi"
diff --git a/conf/machine/chip.conf b/conf/machine/chip.conf
index f053976..ff5a213 100644
--- a/conf/machine/chip.conf
+++ b/conf/machine/chip.conf
@@ -5,7 +5,7 @@
 MACHINE_EXTRA_RRECOMMENDS = " kernel-modules"
 MACHINE_ESSENTIAL_EXTRA_RDEPENDS = " kernel-image kernel-devicetree"
 
-EXTRA_IMAGEDEPENDS += "u-boot"
+EXTRA_IMAGEDEPENDS += "u-boot sunxi-tools-native"
 
 DEFAULTTUNE ?= "cortexa8t-neon"
 include conf/machine/include/tune-cortexa8.inc
-- 
2.7.4

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

[yocto] [meta-chip][PATCH V3 1/4] chip: Make page size into a variable.

2017-06-28 Thread drew . moseley 
From: Drew Moseley 

Signed-off-by: Drew Moseley 
---
 conf/machine/chip.conf | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/conf/machine/chip.conf b/conf/machine/chip.conf
index 0a45a2f..dad1bdb 100644
--- a/conf/machine/chip.conf
+++ b/conf/machine/chip.conf
@@ -30,5 +30,6 @@ MACHINE_FEATURES = "usbgadget usbhost wifi"
 MACHINE_EXTRA_RRECOMMENDS += "kernel-module-r8723bs rtl8723bs"
 
 UBI_VOLNAME = "rootfs"
-MKUBIFS_ARGS = "--min-io-size 16384 --leb-size 2064384 --max-leb-cnt 2000"
-UBINIZE_ARGS = "--min-io-size 16384 --peb-size 2097152 --sub-page-size 16384"
+CHIP_UBI_PAGE_SIZE = "16384"
+MKUBIFS_ARGS = "--min-io-size ${CHIP_UBI_PAGE_SIZE} --leb-size 2064384 
--max-leb-cnt 2000"
+UBINIZE_ARGS = "--min-io-size ${CHIP_UBI_PAGE_SIZE} --peb-size 2097152 
--sub-page-size 16384"
-- 
2.7.4

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

[yocto] [meta-chip][PATCH V3 2/4] u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file.

2017-06-28 Thread drew . moseley 
From: Drew Moseley 

Signed-off-by: Drew Moseley 
---
 conf/machine/chip.conf| 1 +
 recipes-bsp/u-boot/u-boot-chip_git.bb | 6 ++
 2 files changed, 7 insertions(+)

diff --git a/conf/machine/chip.conf b/conf/machine/chip.conf
index dad1bdb..f053976 100644
--- a/conf/machine/chip.conf
+++ b/conf/machine/chip.conf
@@ -21,6 +21,7 @@ KERNEL_IMAGETYPE = "zImage"
 KERNEL_DEVICETREE = "sun5i-r8-chip.dtb"
 
 SPL_BINARY = "sunxi-spl.bin"
+SPL_ECC_BINARY = "sunxi-spl-with-ecc.bin"
 UBOOT_BINARY = "u-boot-dtb.bin"
 UBOOT_MACHINE = "CHIP_defconfig"
 
diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb 
b/recipes-bsp/u-boot/u-boot-chip_git.bb
index 8e2be50..6de2e9d 100644
--- a/recipes-bsp/u-boot/u-boot-chip_git.bb
+++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
@@ -19,7 +19,13 @@ SRC_URI = " \
 S = "${WORKDIR}/git"
 
 do_compile_append() {
+install ${B}/spl/${SPL_ECC_BINARY} ${B}/${SPL_ECC_BINARY}
 install ${B}/spl/${SPL_BINARY} ${B}/${SPL_BINARY}
 }
 
 COMPATIBLE_MACHINE = "chip"
+
+do_deploy_append() {
+install -m 644 ${B}/${SPL_ECC_BINARY} 
${DEPLOYDIR}/${SPL_ECC_BINARY}-${PV}-${PR}
+ln -sf ${SPL_ECC_BINARY}-${PV}-${PR} ${DEPLOYDIR}/${SPL_ECC_BINARY}
+}
-- 
2.7.4

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

[yocto] [meta-chip][PATCH V3 0/4] Initial attempt at flashing instructions.

2017-06-28 Thread drew . moseley 
From: Drew Moseley 

* V3:

Cleanup README.

Add CHIP_UBI_PAGE_SIZE variable to reuse the data from the machine 
configuration.

* V2:

Updated README and layer dependencies.

Added error checking to flashing script

* V1:

This set of patches adds the native tools and target components needed to
reflash the CHIP boards.  Additionally a shell script is added to the deploy
directory showing how to kick off a flash update. It's not ideal as I've
hardcoded a max size for the UBI image into the script and didn't see much
of an alternative. It does function though.

Drew

The following changes since commit 0079e6ac10fc371d6f527270c23b887561f717aa:

  chip: Append to MACHINE_EXTRA_RRECOMMENDS rather than overwriting (2017-06-15 
13:37:19 +0100)

are available in the git repository at:

  g...@github.com:drewmoseley/meta-chip.git flashing-instructions-v3

for you to fetch changes up to 69920ec23cef400687a2a8c1ab1a825a911278d2:

  chip: Add chip-u-boot-scr recipe and flash script (2017-06-28 19:06:01 -0400)


Drew Moseley (4):
  chip: Make page size into a variable.
  u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file.
  chip: Build sunxi-tools-native.
  chip: Add chip-u-boot-scr recipe and flash script

 README  | 94 -
 conf/layer.conf |  3 +
 conf/machine/chip.conf  |  8 ++-
 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb  | 89 +++
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full | 32 +
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in   | 43 +++
 recipes-bsp/u-boot/u-boot-chip_git.bb   |  7 ++
 7 files changed, 272 insertions(+), 4 deletions(-)
 create mode 100644 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in

Drew Moseley (4):
  chip: Make page size into a variable.
  u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file.
  chip: Build sunxi-tools-native.
  chip: Add chip-u-boot-scr recipe and flash script

 README  | 94 -
 conf/layer.conf |  3 +
 conf/machine/chip.conf  |  8 ++-
 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb  | 89 +++
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full | 32 +
 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in   | 43 +++
 recipes-bsp/u-boot/u-boot-chip_git.bb   |  7 ++
 7 files changed, 272 insertions(+), 4 deletions(-)
 create mode 100644 recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.full
 create mode 100644 recipes-bsp/chip-u-boot-scr/files/boot.cmd.in

-- 
2.7.4

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

[yocto] Issue cross-compiling Asterisk 13.16.0

2017-06-28 Thread Chris Trobridge 

I am updating the asterisk recipe to 13.16.0 to fix some security advisories 
and hit an issue in the configuration script new to me:

config.log:
configure:17599: checking if we have usable eventfd support
configure:17602: error: in 
`/home/chris/yocto/build/tmp/work/core2-32-poky-linux/asterisk/13.16.0-r0/asterisk-13.16.0':
configure:17604: error: cannot run test program while cross compiling

configure:
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking if we have usable eventfd 
support" >&5
$as_echo_n "checking if we have usable eventfd support... " >&6; }
if test "$cross_compiling" = yes; then :
  { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot run test program while cross compiling
See \`config.log' for more details" "$LINENO" 5; }

configure.ac:
AC_MSG_CHECKING([if we have usable eventfd support])
AC_RUN_IFELSE(
  [AC_LANG_PROGRAM([#include ],
      [return eventfd(0, EFD_NONBLOCK | EFD_SEMAPHORE) == -1;])],
  AC_MSG_RESULT(yes)
  AC_DEFINE([HAVE_EVENTFD], 1, [Define to 1 if your system supports eventfd and 
the EFD_NONBLOCK and EFD_SEMAPHORE flags.]),
  AC_MSG_RESULT(no)
)

I can see how this follows through but it's not clear how to fix it.  Thus far 
I think to avoid the test I need to provide a suitable cached value in a site 
file.   A bit of searching found "CACHED_CONFIGUREVARS", which appears to do 
this, but what would the variable name be?

Is this a test I can bypass in this way?

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

Re: [yocto] Saving all files using source mirror isn't capturing build packages

2017-06-28 Thread Jimi Damon 
Please ignore if you received this twice. My email client wasn't giving 
me confirmation /sent mail.



Problem was solved with




MIRRORS ?= "\
git://.*/.*file://media/build/mirror/ \n \
git://.*/.*/.* file://media/build/mirror/ \n \
ftp://.*/.*file://media/build/mirror/ \n \
http://.*/.*   file://media/build/mirror/ \n \
svn://.*/.*file://media/build/mirror/ \n \
https://.*/.*file://media/build/mirror/ \n \
"


BB_FETCH_PREMIRRORONLY = "1"
SOURCE_MIRROR_URL ?= "file:///media/build/mirror/"





On 06/28/2017 12:39 PM, Jimi Damon wrote:


Hi,


I'm trying to save the entire build PLUS the tools used to create the 
build and I'm finding that when I initially perform the



bitbake -c fetchall b2qt-embedded-qt5-image

followed by a copy of the required downloaded .tar.gz files to the 
mirror directory and then creating a new build directory  ( with new 
local.conf and bb.layers ) with the lines


SOURCE_MIRROR_URL ?= "file://media/build/mirror/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NO_NETWORK = "1"

and I try to build , I get errors saying that certain Native tools are 
missing like gcc-source, bison-native, flex-native...etc


Example



Initialising tasks: 100% 
|| 
Time: 0:00:06

NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: gcc-source-6.2.0-6.2.0-r0 do_fetch: Network access disabled 
through BB_NO_NETWORK (or set indirectly due to use of 
BB_FETCH_PREMIRRORONLY) but access requested with command 
/usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate 
-P /media/build/NewestBuild/build-nitrogen6x/../downloads 
'http://ftp.gnu.org/gnu/gcc/gcc-6.2.0/gcc-6.2.0.tar.bz2' (for url None)

ERROR: gcc-source-6.2.0-6.2.0-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work-shared/gcc-6.2.0-r0/temp/log.do_fetch.30899
ERROR: Task 
(/media/build/NewestBuild/sources/poky/meta/recipes-devtools/gcc/gcc-source_6.2.bb:do_fetch) 
failed with exit code '1'
ERROR: bison-native-3.0.4-r0 do_unpack: Unpack failure for URL: 
'http://ftp.gnu.org/gnu/bison/bison-3.0.4.tar.xz'. Unpack command 
PATH="/media/build/NewestBuild/sources/poky/scripts/native-intercept:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin/texinfo-dummy-native:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots-uninative/x86_64-linux/usr/bin:/media/build/NewestBuild/sources/poky/scripts:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/sbin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/sbin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/bin:/media/build/NewestBuild/sources/poky/scripts:/media/build/NewestBuild/sources/poky/bitbake/bin:/media/build/NewBuild:/home/jdamon/.rvm/gems/ruby-2.4.0/bin:/home/jdamon/.rvm/gems/ruby-2.4.0@global/bin:/home/jdamon/.rvm/rubies/ruby-2.4.0/bin:/home/jdamon/.rvm/bin:/usr/bin:/bin:/sbin:/sbin:/bin:/usr/bin:/usr/local/bin:/usr/sbin:/home/jdamon/Scripts:/usr/games:/usr/lib/lapack:/opt/local/bin:/home/jdamon/Tools/bin:/home/jdamon/Scripts/Work:/home/jdamon/Tools/android-sdk-linux/platform-tools:/home/jdamon/Tools/android-ndk-r10e:/Developer/SDKs/android-sdk-mac_86/tools/:/opt/local/lib/mysql5/bin:/usr/share/apache-maven-3.0.5/bin:/home/jdamon/.rvm/bin:/home/jdamon/.rvm/bin:/home/jdamon/.rvm/bin" 
xz -dc 
/media/build/NewestBuild/build-nitrogen6x/../downloads/bison-3.0.4.tar.xz 
| tar x --no-same-owner -f - failed with return value 2

ERROR: bison-native-3.0.4-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work/x86_64-linux/bison-native/3.0.4-r0/temp/log.do_unpack.30904
ERROR: Task 
(virtual:native:/media/build/NewestBuild/sources/poky/meta/recipes-devtools/bison/bison_3.0.4.bb:do_unpack) 
failed with exit code '1'
ERROR: flex-native-2.6.0-r0 do_fetch: Network access disabled through 
BB_NO_NETWORK (or set indirectly due to use of 
BB_FETCH_PREMIRRORONLY) but access requested with command 
/usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate 
-P /media/build/NewestBuild/build-nitrogen6x/../downloads 
'http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2' (for url None)

ERROR: flex-native-2.6.0-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work/x86_64-linux/flex-native/2.6.0-r0/temp/log.do_fetch.30905
ERROR: Task 
(virtual:native:/media/build/NewestBuild/sources/poky/meta/recipes-devtools/flex/flex_2.6.0.bb:do_fetch) 
failed with exit code '1'
NOTE: Tasks

Re: [yocto] Saving all files using source mirror isn't capturing build packages

2017-06-28 Thread Jimi Damon 

Fixed : PEBKAC


I needed the two following elements




MIRRORS ?= "\
git://.*/.*file://media/build/mirror/ \n \
git://.*/.*/.* file://media/build/mirror/ \n \
ftp://.*/.*file://media/build/mirror/ \n \
http://.*/.*   file://media/build/mirror/ \n \
svn://.*/.*file://media/build/mirror/ \n \
https://.*/.*file://media/build/mirror/ \n \
"


BB_FETCH_PREMIRRORONLY = "1"
SOURCE_MIRROR_URL ?= "file:///media/build/mirror/"


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

[yocto] Saving all files using source mirror isn't capturing build packages

2017-06-28 Thread Jimi Damon 

Hi,


I'm trying to save the entire build PLUS the tools used to create the 
build and I'm finding that when I initially perform the



bitbake -c fetchall b2qt-embedded-qt5-image

followed by a copy of the required downloaded .tar.gz files to the 
mirror directory and then creating a new build directory  ( with new 
local.conf and bb.layers ) with the lines


SOURCE_MIRROR_URL ?= "file://media/build/mirror/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NO_NETWORK = "1"

and I try to build , I get errors saying that certain Native tools are 
missing like gcc-source, bison-native, flex-native...etc


Example



Initialising tasks: 100% 
|| 
Time: 0:00:06

NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: gcc-source-6.2.0-6.2.0-r0 do_fetch: Network access disabled 
through BB_NO_NETWORK (or set indirectly due to use of 
BB_FETCH_PREMIRRORONLY) but access requested with command /usr/bin/env 
wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P 
/media/build/NewestBuild/build-nitrogen6x/../downloads 
'http://ftp.gnu.org/gnu/gcc/gcc-6.2.0/gcc-6.2.0.tar.bz2' (for url None)

ERROR: gcc-source-6.2.0-6.2.0-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work-shared/gcc-6.2.0-r0/temp/log.do_fetch.30899
ERROR: Task 
(/media/build/NewestBuild/sources/poky/meta/recipes-devtools/gcc/gcc-source_6.2.bb:do_fetch) 
failed with exit code '1'
ERROR: bison-native-3.0.4-r0 do_unpack: Unpack failure for URL: 
'http://ftp.gnu.org/gnu/bison/bison-3.0.4.tar.xz'. Unpack command 
PATH="/media/build/NewestBuild/sources/poky/scripts/native-intercept:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin/texinfo-dummy-native:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots-uninative/x86_64-linux/usr/bin:/media/build/NewestBuild/sources/poky/scripts:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/sbin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/usr/bin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/sbin:/media/build/NewestBuild/build-nitrogen6x/tmp/sysroots/x86_64-linux/bin:/media/build/NewestBuild/sources/poky/scripts:/media/build/NewestBuild/sources/poky/bitbake/bin:/media/build/NewBuild:/home/jdamon/.rvm/gems/ruby-2.4.0/bin:/home/jdamon/.rvm/gems/ruby-2.4.0@global/bin:/home/jdamon/.rvm/rubies/ruby-2.4.0/bin:/home/jdamon/.rvm/bin:/usr/bin:/bin:/sbin:/sbin:/bin:/usr/bin:/usr/local/bin:/usr/sbin:/home/jdamon/Scripts:/usr/games:/usr/lib/lapack:/opt/local/bin:/home/jdamon/Tools/bin:/home/jdamon/Scripts/Work:/home/jdamon/Tools/android-sdk-linux/platform-tools:/home/jdamon/Tools/android-ndk-r10e:/Developer/SDKs/android-sdk-mac_86/tools/:/opt/local/lib/mysql5/bin:/usr/share/apache-maven-3.0.5/bin:/home/jdamon/.rvm/bin:/home/jdamon/.rvm/bin:/home/jdamon/.rvm/bin" 
xz -dc 
/media/build/NewestBuild/build-nitrogen6x/../downloads/bison-3.0.4.tar.xz 
| tar x --no-same-owner -f - failed with return value 2

ERROR: bison-native-3.0.4-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work/x86_64-linux/bison-native/3.0.4-r0/temp/log.do_unpack.30904
ERROR: Task 
(virtual:native:/media/build/NewestBuild/sources/poky/meta/recipes-devtools/bison/bison_3.0.4.bb:do_unpack) 
failed with exit code '1'
ERROR: flex-native-2.6.0-r0 do_fetch: Network access disabled through 
BB_NO_NETWORK (or set indirectly due to use of BB_FETCH_PREMIRRORONLY) 
but access requested with command /usr/bin/env wget -t 2 -T 30 -nv 
--passive-ftp --no-check-certificate -P 
/media/build/NewestBuild/build-nitrogen6x/../downloads 
'http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2' (for url None)

ERROR: flex-native-2.6.0-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/media/build/NewestBuild/build-nitrogen6x/tmp/work/x86_64-linux/flex-native/2.6.0-r0/temp/log.do_fetch.30905
ERROR: Task 
(virtual:native:/media/build/NewestBuild/sources/poky/meta/recipes-devtools/flex/flex_2.6.0.bb:do_fetch) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 92 tasks of which 83 didn't need to be 
rerun and 3 failed.



Why aren't these being downloaded when I did my initial fetchall ?

Also, what is the way to capture all of the required packages for an 
image AND the development tools required to build the image ?



Thanks


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

[yocto] [meta-oic][PATCH] Hotfix: Include functional header for g++-7.1.0

2017-06-28 Thread Philippe Coval 
Reason is described in gcc7 porting notes:
"Several C++ Standard Library headers
have been changed to no longer include the  header.
As such, C++ programs that used components defined in 
without explicitly including that header will no longer compile."

It was tested on yocto poky master on iotivity-1.2.1 (and later)

Signed-off-by: Philippe Coval 
---

Origin: 
https://github.com/tizenteam/meta-oic/tree/sandbox/pcoval/on/master/review

...rce-Include-functional-header-for-g-7.1.0.patch | 62 ++
 recipes-core/iotivity/iotivity_1.2.1.bb|  3 ++
 2 files changed, 65 insertions(+)
 create mode 100644 
recipes-core/iotivity/files/0189-resource-Include-functional-header-for-g-7.1.0.patch

diff --git 
a/recipes-core/iotivity/files/0189-resource-Include-functional-header-for-g-7.1.0.patch
 
b/recipes-core/iotivity/files/0189-resource-Include-functional-header-for-g-7.1.0.patch
new file mode 100644
index 000..2e40f97
--- /dev/null
+++ 
b/recipes-core/iotivity/files/0189-resource-Include-functional-header-for-g-7.1.0.patch
@@ -0,0 +1,62 @@
+From fd9c363689646784303197da5a21d6693cc6cbc9 Mon Sep 17 00:00:00 2001
+From: Philippe Coval 
+Date: Wed, 28 Jun 2017 04:54:05 +0200
+Subject: [PATCH 189/189] resource: Include functional header for g++-7.1.0
+
+It was tested on yocto poky master on iotivity-1.2.1 (and later):
+
+  resource/include/OCUtilities.h: \
+  In function 'OCStackResult OC::nil_guard(PtrT&&, FnT&&, ParamTs&& ...)':
+  resource/include/OCUtilities.h:85:21: \
+  error: 'bind' is not a member of 'std'
+  return std::bind(fn, p, std::ref(params)...)();
+
+  resource/include/OCApi.h: At global scope:
+  resource/include/OCApi.h:362:18: \
+  error: 'function' in namespace 'std' does not name a template type
+  typedef std::function FindCallback;
+
+Change-Id: Ie1cab497c33fde394f77490a1d636eb36a563396
+Origin: https://gerrit.iotivity.org/gerrit/#/c/21069/
+Signed-off-by: Philippe Coval 
+Reviewed-on: https://gerrit.iotivity.org/gerrit/21067
+Reviewed-by: Thiago Macieira 
+Tested-by: jenkins-iotivity 
+(cherry picked from commit 26c2798188497da22e0a70efebc47991dd755db2)
+Reviewed-on: https://gerrit.iotivity.org/gerrit/21069
+Reviewed-by: Sudarsana Babu Nagineni 
+Reviewed-by: Mats Wichmann 
+---
+ resource/include/OCApi.h   | 2 --
+ resource/include/OCUtilities.h | 1 +
+ 2 files changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/resource/include/OCApi.h b/resource/include/OCApi.h
+index ff2d212..47981d5 100644
+--- a/resource/include/OCApi.h
 b/resource/include/OCApi.h
+@@ -27,9 +27,7 @@
+ #include 
+ #include 
+ #include 
+-#if defined(_MSC_VER)
+ #include 
+-#endif
+ 
+ #include "octypes.h"
+ #include "OCHeaderOption.h"
+diff --git a/resource/include/OCUtilities.h b/resource/include/OCUtilities.h
+index 85039d0..f1c9304 100644
+--- a/resource/include/OCUtilities.h
 b/resource/include/OCUtilities.h
+@@ -26,6 +26,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include 
+ #include 
+-- 
+2.7.4
+
diff --git a/recipes-core/iotivity/iotivity_1.2.1.bb 
b/recipes-core/iotivity/iotivity_1.2.1.bb
index c01ea46..c8fb8fd 100644
--- a/recipes-core/iotivity/iotivity_1.2.1.bb
+++ b/recipes-core/iotivity/iotivity_1.2.1.bb
@@ -1,3 +1,4 @@
+PR = "r1"
 SUMMARY = "IoTivity framework and SDK sponsored by the Open Connectivity 
Foundation."
 DESCRIPTION = "IoTivity is an open source software framework enabling seamless 
device-to-device connectivity to address the emerging needs of the Internet of 
Things."
 HOMEPAGE = "https://www.iotivity.org/;
@@ -12,6 +13,8 @@ branch_iotivity = "1.2-rel"
 SRCREV = "0c90ca6ffcbb6a2c56c977ec11bebb7b1d14053b"
 SRC_URI = 
"git://github.com/iotivity/iotivity.git;destsuffix=${S};branch=${branch_iotivity};protocol=http"
 SRC_URI += 
"file://0364-yocto-Use-tools-from-sysroot-before-system-PATH-agai.patch"
+SRC_URI += "file://0189-resource-Include-functional-header-for-g-7.1.0.patch"
+
 
 url_tinycbor = "git://github.com/01org/tinycbor.git"
 SRCREV_tinycbor = "31c7f81d45d115d2007b1c881cbbd3a19618465c"
-- 
2.7.4

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

Re: [yocto] [meta-chip][PATCH V2 0/3] Initial attempt at flashing instructions.

2017-06-28 Thread Andrei Gherzan 
On Wed, Jun 28, 2017 at 2:06 PM, Drew Moseley 
wrote:

>
> On Jun 28, 2017, at 9:03 AM, Trevor Woerner  wrote:
>
> On Sun, Jun 25, 2017 at 3:55 PM,   wrote:
>
> From: Drew Moseley 
>
> * V2:
>
> Updated README and layer dependencies.
>
> Added error checking to flashing script
>
> * V1:
>
> This set of patches adds the native tools and target components needed to
> reflash the CHIP boards.  Additionally a shell script is added to the
> deploy
> directory showing how to kick off a flash update. It's not ideal as I've
> hardcoded a max size for the UBI image into the script and didn't see much
> of an alternative. It does function though.
>
>
>
> Looks and works great! Thanks for investigating and getting this working
> :-)
>
> Tested-by: Trevor Woerner 
>
>
> FYI, additional discussion is ongoing at https://github.com/
> agherzan/meta-chip/pull/9.  I’ll have a V3 in a few days. The V3 changes
> are primarily cosmetic.
>

Correct. There are some small things to tweak. Nothing major and it will
get in soon.
--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-chip][PATCH V2 0/3] Initial attempt at flashing instructions.

2017-06-28 Thread Drew Moseley 

> On Jun 28, 2017, at 9:03 AM, Trevor Woerner  wrote:
> 
> On Sun, Jun 25, 2017 at 3:55 PM,   wrote:
>> From: Drew Moseley 
>> 
>> * V2:
>> 
>> Updated README and layer dependencies.
>> 
>> Added error checking to flashing script
>> 
>> * V1:
>> 
>> This set of patches adds the native tools and target components needed to
>> reflash the CHIP boards.  Additionally a shell script is added to the deploy
>> directory showing how to kick off a flash update. It's not ideal as I've
>> hardcoded a max size for the UBI image into the script and didn't see much
>> of an alternative. It does function though.
> 
> 
> Looks and works great! Thanks for investigating and getting this working :-)
> 
> Tested-by: Trevor Woerner 

FYI, additional discussion is ongoing at 
https://github.com/agherzan/meta-chip/pull/9 
.  I’ll have a V3 in a few days. 
The V3 changes are primarily cosmetic.

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

Re: [yocto] [meta-chip][PATCH V2 0/3] Initial attempt at flashing instructions.

2017-06-28 Thread Trevor Woerner 
On Sun, Jun 25, 2017 at 3:55 PM,   wrote:
> From: Drew Moseley 
>
> * V2:
>
> Updated README and layer dependencies.
>
> Added error checking to flashing script
>
> * V1:
>
> This set of patches adds the native tools and target components needed to
> reflash the CHIP boards.  Additionally a shell script is added to the deploy
> directory showing how to kick off a flash update. It's not ideal as I've
> hardcoded a max size for the UBI image into the script and didn't see much
> of an alternative. It does function though.


Looks and works great! Thanks for investigating and getting this working :-)

Tested-by: Trevor Woerner 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] : cmake and create_symlink using cmake 3.5 and yocto 2.2.2

2017-06-28 Thread Ehrlich Andrei 
Thanks a lot!

This proposal solved my problem ☺

BR
Andrei

Von: Jussi Kukkonen [mailto:jussi.kukko...@intel.com]
Gesendet: Dienstag, 27. Juni 2017 10:45
An: Ehrlich Andrei
Cc: yocto@yoctoproject.org
Betreff: Re: [yocto] : cmake and create_symlink using cmake 3.5 and yocto 2.2.2

On 26 June 2017 at 21:46, Ehrlich Andrei 
> wrote:
> Please excuse the newbie question I want to ask, but I started with yocto and 
> cmake 3 month ago and now I have a couple of recipes based on cmake. One of 
> that cmake files installs links using following code:
>
> install(
> CODE "execute_process( \
> COMMAND ${CMAKE_COMMAND} -E create_symlink \
> __tool \
> ${CMAKE_INSTALL_PREFIX}/bin/tool_${DST_NAME} \
> )"
>
> When the code is executed in yocto  the do_install task fails with following 
> error:
> failed to create symbolic link '/usr/bin/tool_intf': Permission denied

The code should account for DESTDIR I think: maybe something like 
"$ENV{DESTDIR}/${CMAKE_INSTALL_PREFIX}/bin/tool_${DST_NAME}" as the target

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

[yocto] RNDIS Broken in linux-yocto 4.1.39, working in 4.1.37

2017-06-28 Thread Martin Townsend 
Hi,

I recently upgraded to 4.1.39 linux-yocto and Ethernet Gadget stopped
working with Windows hosts, here's the output from the Journal:

Jun 22 20:31:37 varsomam43-bb5eda kernel: g_ether gadget: rndis
reqa1.01 v i l4096
Jun 22 20:31:37 varsomam43-bb5eda kernel: g_ether gadget: rndis
req21.00 v i l28
Jun 22 20:31:37 varsomam43-bb5eda kernel: gen_ndis_query_resp:
RNDIS_OID_GEN_SUPPORTED_LIST
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.457796] IPv6:
ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.481614] g_ether
gadget: rndis req21.00 v i l24
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.481946]
rndis_msg_parser: RNDIS_MSG_INIT
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.528733] g_ether
gadget: rndis reqa1.01 v i l4096
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.530206] g_ether
gadget: rndis req21.00 v i l28
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.530322]
gen_ndis_query_resp: RNDIS_OID_GEN_SUPPORTED_LIST
Jun 22 20:31:37 varsomam43-bb5eda kernel: g_ether gadget: rndis
reqa1.01 v i l4096
Jun 22 20:31:37 varsomam43-bb5eda kernel: g_ether gadget: rndis
req21.00 v i l32
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser: unknown
RNDIS message 0x8004 len 136
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser: 04
00 00 80 88 00 00 00 03 00 00 00 00 00 00 00  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0010: 70
00 00 00 10 00 00 00 01 01 01 00 02 01 01 00  p...
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0020: 03
01 01 00 04 01 01 00 06 01 01 00 07 01 01 00  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0030: 0a
01 01 00 0b 01 01 00 0c 01 01 00 0d 01 01 00  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0040: 16
01 01 00 0e 01 01 00 11 01 01 00 14 01 01 00  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0050: 02
02 01 00 01 01 02 00 02 01 02 00 03 01 02 00  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0060: 04
01 02 00 05 01 02 00 01 01 01 01 02 01 01 01  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0070: 03
01 01 01 05 01 01 01 04 01 01 01 01 01 02 01  
Jun 22 20:31:37 varsomam43-bb5eda kernel: rndis_msg_parser0080: 02
01 02 01 03 01 02 01  
Jun 22 20:31:37 varsomam43-bb5eda kernel: RNDIS command error -524, 32/32
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.592722] g_ether
gadget: rndis reqa1.01 v i l4096
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.594360] g_ether
gadget: rndis req21.00 v i l32
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.594699]
rndis_msg_parser: unknown RNDIS message 0x8004 len 136
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601671]
rndis_msg_parser: 04 00 00 80 88 00 00 00 03 00 00 00 00 00 00
00  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601697]
rndis_msg_parser0010: 70 00 00 00 10 00 00 00 01 01 01 00 02 01 01
00  p...
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601718]
rndis_msg_parser0020: 03 01 01 00 04 01 01 00 06 01 01 00 07 01 01
00  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601739]
rndis_msg_parser0030: 0a 01 01 00 0b 01 01 00 0c 01 01 00 0d 01 01
00  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601759]
rndis_msg_parser0040: 16 01 01 00 0e 01 01 00 11 01 01 00 14 01 01
00  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601779]
rndis_msg_parser0050: 02 02 01 00 01 01 02 00 02 01 02 00 03 01 02
00  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601800]
rndis_msg_parser0060: 04 01 02 00 05 01 02 00 01 01 01 01 02 01 01
01  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601820]
rndis_msg_parser0070: 03 01 01 01 05 01 01 01 04 01 01 01 01 01 02
01  
Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601839]
rndis_msg_parser0080: 02 01 02 01 03 01 02 01

Jun 22 20:31:37 varsomam43-bb5eda kernel[242]: [ 7459.601858] RNDIS
command error -524, 32/32

Not only has it stopped working but it often locks up the Windows host
when you try things like re-installing the Windows RNDIS driver, or
enabling the RNDIS/Ethernet Gadget Network adapter.

I reverted back to 4.1.37 and everything is fine again.  I'm using a
TI AM4378 based board.  Has anyone else seen this problem?

Many Thanks,

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