iWave Arria10 Mender integration

Gary Newman

unread,

Jan 30, 2019, 4:33:21 AM1/30/19

to Mender List mender.io

Hi,

I have recently ported my Mender build from an Intel Arria 10 board to an iWave Arria 10 board.

The u-boot build went smoothly but I am having some issue with the Mender kernel integration.

I am having issues running the mender do install function.

The error I am seeing is as follows:

| /home/gnewman/yocto/mender-iwg24m-release-bsp/build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/mender/1.6.0-r0/temp/run.do_install.24527: line 125: -Wl,--hash-style=gnu: command not found

| WARNING: /home/gnewman/yocto/mender-iwg24m-release-bsp/build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/mender/1.6.0-r0/temp/run.do_install.24527:1 exit 127 from 'GOOS=$(eval $(${GO} env) && echo $GOOS)'

| ERROR: Function failed: do_install (log file is located at /home/gnewman/yocto/mender-iwg24m-release-bsp/build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/mender/1.6.0-r0/temp/log.do_install.24527)

ERROR: Task (/home/gnewman/yocto/mender-iwg24m-release-bsp/layers/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.6.0.bb:do_install) failed with exit code '1'

I have attached the error log file & the do_install script.

Any pointers would be appreciated.

Regards,

Gary

run.do_install

log.do_install

Drew Moseley

unread,

Jan 30, 2019, 8:51:38 AM1/30/19

to men...@lists.mender.io

Hi Gary,

This looks suspiciously like you have some environment variables set that may be overriding the values computed by bitbake. Is there anything obvious? Are you setting BB_ENV_EXTRAWHITE in your environment by any chance?

Drew Moseley | Technical Solutions Architect | (+1) 480-797-0552 | https://mender.io

Northern.tech AS | @northerntechHQ | @drewmoseley

Mirza Krak

unread,

Jan 30, 2019, 2:42:47 PM1/30/19

to Mender List mender.io

On Wed, Jan 30, 2019 at 10:33 AM 'Gary Newman' via Mender List mender.io <men...@lists.mender.io> wrote:

Hi,

Hello Gary,

Which Yocto branch are you on?

Looking at the provided install script and log, it is not obvious what is unfortunately. The error "line 125: -Wl,--hash-style=gnu: command not found", hints some kind of incompatibility between "go" and the toolchain.

I do also notice that you are using Angstrom, which gcc version?

--

Mirza Krak | Embedded Solutions Architect | https://mender.io

Mirza Krak

unread,

Jan 30, 2019, 2:44:21 PM1/30/19

to Mender List mender.io

On Wed, Jan 30, 2019 at 10:33 AM 'Gary Newman' via Mender List mender.io <men...@lists.mender.io> wrote:

Hi,

I have recently ported my Mender build from an Intel Arria 10 board to an iWave Arria 10 board.

Also, would love to see these boards at:

https://hub.mender.io/

:).

Check out, https://hub.mender.io/t/about-the-yocto-project-category

--

Gary Newman

unread,

Feb 5, 2019, 8:25:12 AM2/5/19

to Mender List mender.io

Hi Drew,

No I cannot see BB_ENV_EXTRAWHITE being set anywhere.

Regards

Gary

Gary Newman

unread,

Feb 5, 2019, 10:41:18 AM2/5/19

to Mender List mender.io, mirza...@northern.tech

Hi Mirza,

Thanks for the reply.

Right I find myself a little confused because the install for the iWave board is somewhat different to what I have used before.

Previously I would install poky by doing a clone: git clone -b sumo git://git.yoctoproject.org/poky.git.

However this install was done via a repo command:

repo init -u git://github.com/Angstrom-distribution/angstrom-manifest -b angstrom-v2017.06- yocto2.3

repo sync

This seems to pull the following:

<manifest>

<default revision="pyro" sync-j="4"/>

<remote fetch="http://git.yoctoproject.org/git" name="yocto"/>

<remote fetch="git://git.openembedded.org" name="oe"/>

<remote fetch="https://github.com" name="github"/>

<remote fetch="http://git.linaro.org" name="linaro"/>

<remote fetch="http://git.shr-project.org" name="shr"/>

<project remote="linaro" name="openembedded/meta-linaro" path="layers/meta-linaro"/>

<project remote="oe" name="meta-handheld" path="layers/meta-handheld"/>

<project remote="github" name="openembedded/bitbake" path="bitbake" revision="1.34"/>

<project remote="github" name="openembedded/openembedded-core" path="layers/openembedded-core"/>

<project remote="github" name="openembedded/meta-openembedded" path="layers/meta-openembedded"/>

<project remote="github" name="shr-distribution/meta-smartphone" path="layers/meta-smartphone"/>

<project remote="github" name="Freescale/meta-freescale-3rdparty" path="layers/meta-freescale-3rdparty"/>

<project remote="github" name="96boards/meta-96boards" path="layers/meta-96boards"/>

<project remote="github" name="koenkooi/meta-dominion" path="layers/meta-dominion"/>

<project remote="github" name="koenkooi/meta-uav" path="layers/meta-uav"/>

<project remote="github" name="koenkooi/meta-photography" path="layers/meta-photography"/>

<project remote="github" name="koenkooi/meta-edison" path="layers/meta-edison"/>

<project remote="github" name="koenkooi/meta-kodi" path="layers/meta-kodi"/>

<project remote="github" name="ndechesne/meta-qcom" path="layers/meta-qcom"/>

<project remote="github" name="linux-sunxi/meta-sunxi" path="layers/meta-sunxi" />

<project remote="github" name="linux4sam/meta-atmel" path="layers/meta-atmel" revision="9deeb0a3ca64c7d8e48e2f861c4d1bffeba24220" upstream="morty"/>

<project remote="github" name="kraj/meta-altera" path="layers/meta-altera" revision="37ca0f7ab398e2e5bc61bd163b0bc16df535160f" upstream="master"/>

<project remote="github" name="kraj/meta-nslu2" path="layers/meta-nslu2" revision="8f35264fe9bb38439ece38c0c324cec792b22a8f" upstream="master"/>

<project remote="github" name="OSSystems/meta-browser" path="layers/meta-browser" revision="6edb45804c5e532fdbca31e9d358d9052eaee90b" upstream="master"/>

<project remote="github" name="meta-qt5/meta-qt5" path="layers/meta-qt5" revision="3ae86cb32edd1449f702e0a094929ae9b21ce191" upstream="master"/>

<project remote="github" name="bmwcarit/meta-ros" path="layers/meta-ros" revision="f591713a1494772882d6b4459c7cb1fa6bc059ba" upstream="master"/>

<project remote="github" name="schnitzeltony/meta-office" path="layers/meta-office" revision="3213948bafb7fae4fa00ce6dc997d1801e870b5e" upstream="master"/>

<project remote="github" name="Angstrom-distribution/meta-angstrom" path="layers/meta-angstrom" revision="angstrom-v2017.06-yocto2.3">

<copyfile dest="setup-environment" src="../../.repo/manifests/setup-environment"/>

</project>

<project remote="yocto" name="meta-freescale" path="layers/meta-freescale"/>

<project remote="yocto" name="meta-intel" path="layers/meta-intel"/>

<project remote="yocto" name="meta-xilinx" path="layers/meta-xilinx"/>

<project remote="yocto" name="meta-mono" path="layers/meta-mono"/>

<project remote="yocto" name="meta-raspberrypi" path="layers/meta-raspberrypi" revision="rocko" />

<project remote="yocto" name="meta-java" path="layers/meta-java"/>

<project remote="yocto" name="meta-maker" path="layers/meta-maker"/>

<project remote="yocto" name="meta-qt4" path="layers/meta-qt4"/>

<project remote="yocto" name="meta-intel-iot-middleware" path="layers/meta-intel-iot-middleware" revision="821cf14c8304669d9ce0c5b87b9be5a6eecff6e5" upstream="master"/>

<project remote="yocto" name="meta-ti" path="layers/meta-ti" revision="e57e6a3c1b9668b0b09d39e03fab7a557c392f81" upstream="master"/>

</manifest>

So the yocto version seems to be pyro.

This Angstrom build is a bit convoluted.

Gcc version seems to be 6.4:

ANGSTROM_GCC_VERSION ?= "6.4%"

GCCVERSION = "${ANGSTROM_GCC_VERSION}"

Although I'd expect this to be set to linaro-xx, so I'm not sure.

I'll have a look at moving this info over to https://hub.mender.io/

Regards,

Gary

Reply all

Reply to author

Forward