Re: [yocto] [PATCH 3/3] recipes-bsp/u-boot: update to the latest version
a previous patch of yours did a:
require recipes-bsp/u-boot/u-boot-common.inc
which defines this SRCREV
my subtle point being: I don't get the impression you're testing your
patches, or at least not testing them correctly.
the fact you're CCing Romain suggests your either using a very old branch
of https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/ or that you're
submitting patches to me for https://github.com/rockchip-linux/meta-rockchip
?
Unfortunately for me, when https://github.com/rockchip-linux/meta-rockchip
did a clone of https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/,
they left my and Romain's names as maintainers in the README (along with
instructions for github)
On Wed, May 8, 2019 at 12:19 PM ayaka wrote:
>
> On 5/6/19 9:31 PM, Trevor Woerner wrote:
> > On Sat 2019-05-04 @ 06:43:34 PM, ayaka wrote:
> >> On 5/4/19 11:06 AM, Trevor Woerner wrote:
> >>> On Wed 2019-04-24 @ 10:59:18 PM, Randy 'ayaka' Li wrote:
> From: Randy Li
>
> Signed-off-by: Randy Li
> ---
> recipes-bsp/u-boot/u-boot-rockchip_git.bb | 18 ++
> 1 file changed, 18 insertions(+)
> create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_git.bb
>
> diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> new file mode 100644
> index 000..aa4b84d
> --- /dev/null
> +++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> @@ -0,0 +1,18 @@
> +# Copyright (C) 2019 SUMOMO Computer Assocation
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +include u-boot-rockchip.inc
> +
> +DESCRIPTION = "Rockchip U-Boot"
> +
> +LIC_FILES_CHKSUM =
> "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
> +
> +SRC_URI = " \
> + git://github.com/rockchip-linux/u-boot.git;branch=release; \
> + file://binutils-2.28-ld-fix.patch \
> + file://gcc7_fixup.patch \
> + "
> +
> +S = "${WORKDIR}/git"
> +PV = "v2019.01"
> >>> This doesn't even get past the fetching stage:
> >> I am sorry, I forget that ssh git protocol only work for those users who
> >> uploaded their key to the github, I would change it back to https.
> >>> WARNING: u-boot-rockchip-1_v2019.01-r0 do_fetch: Failed to fetch
> URL git://github.com/rockchip-linux/u-boot.git;branch=release;,
> attempting MIRRORS if available
> >>> ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure:
> Unable to find revision 3c99166441bf3ea325af2da83cfe65430b49c066 in branch
> release even from upstream
> >>> ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure for
> URL: 'git://github.com/rockchip-linux/u-boot.git;branch=release;'. Unable
> to fetch URL from any source.
> >>> ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch:
> >>> ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Function failed:
> base_do_fetch
> >>> ERROR: Task
> (/opt/oe/configs/z/build-master/meta-rockchip/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb:do_fetch)
> failed with exit code '1'
> > The problem is that it's trying to fetch commit 3c9916 which doesn't
> exist on
> > github.com/rockchip-linux/u-boot.git. That revision is on upstream
> U-Boot.
> How comes? I didn't write any commit id there, it is based on the branch
> at all.
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/3] recipes-bsp/u-boot: update to the latest version
On 5/6/19 9:31 PM, Trevor Woerner wrote:
On Sat 2019-05-04 @ 06:43:34 PM, ayaka wrote:
On 5/4/19 11:06 AM, Trevor Woerner wrote:
On Wed 2019-04-24 @ 10:59:18 PM, Randy 'ayaka' Li wrote:
From: Randy Li
Signed-off-by: Randy Li
---
recipes-bsp/u-boot/u-boot-rockchip_git.bb | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_git.bb
diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb
b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
new file mode 100644
index 000..aa4b84d
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
@@ -0,0 +1,18 @@
+# Copyright (C) 2019 SUMOMO Computer Assocation
+# Released under the MIT license (see COPYING.MIT for the terms)
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+include u-boot-rockchip.inc
+
+DESCRIPTION = "Rockchip U-Boot"
+
+LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
+
+SRC_URI = " \
+ git://github.com/rockchip-linux/u-boot.git;branch=release; \
+ file://binutils-2.28-ld-fix.patch \
+ file://gcc7_fixup.patch \
+ "
+
+S = "${WORKDIR}/git"
+PV = "v2019.01"
This doesn't even get past the fetching stage:
I am sorry, I forget that ssh git protocol only work for those users who
uploaded their key to the github, I would change it back to https.
WARNING: u-boot-rockchip-1_v2019.01-r0 do_fetch: Failed to fetch URL
git://github.com/rockchip-linux/u-boot.git;branch=release;, attempting MIRRORS
if available
ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure: Unable
to find revision 3c99166441bf3ea325af2da83cfe65430b49c066 in branch release
even from upstream
ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure for URL:
'git://github.com/rockchip-linux/u-boot.git;branch=release;'. Unable to fetch
URL from any source.
ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch:
ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Function failed:
base_do_fetch
ERROR: Task
(/opt/oe/configs/z/build-master/meta-rockchip/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb:do_fetch)
failed with exit code '1'
The problem is that it's trying to fetch commit 3c9916 which doesn't exist on
github.com/rockchip-linux/u-boot.git. That revision is on upstream U-Boot.
How comes? I didn't write any commit id there, it is based on the branch
at all.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days
> On May 7, 2019, at 2:47 AM, Bas Mevissen wrote: > > On 2019-05-07 07:20, Behan Webster wrote: > >> > On May 6, 2019, at 8:36 AM, Bas Mevissen wrote: >> > On 5/6/19 12:45 PM, Josef Holzmayr wrote: >> > I'd actually word it a little bit differently: >> > If there is only *ONE* attendee who did not properly do the homework, it >> > will have a massive impact an the rest of the group. And that somebody >> > will show up unpreparedly is absolutely certain in my opinion. >> > With sufficient trainers, one can continue for most and provide some >> > assistance to the one falling behind. > >> Usually more than one. And this is generally very disruptive to the class as >> a whole. > >> >> As someone who actually got started through the YPDD beginner track (and >> >> also often recommends it to new beginners), my opinion is clearly that >> >> we either should have it, be it only for a handful of attendees, or >> >> offer a *real* replacement, with face to face training. My experience is >> >> that this personal thing in the very beginning is an absolutely >> >> essential part of many YP/OE careers. >> > >> > I agree. That is how I started, next to a compressed Linux Foundation >> > Yocto training that was offered just before the event then. > >> Yes. By me and my colleagues who train for the Linux Foundation. > >> > So it might be wise to ask LF or get something organised. It would mostly >> > require a room and a sponsor for some small devkit. > >> We've run the beginner track for the last few years. The discussion is >> precisely that the YP event is proposing to not run the beginner track this >> year at all. > > But why? There appears to be a constant demand. An excellent question. I agree with you. I don’t have an answer however. Not my decision. >> We're happy to do it again if given the space. > > Yes, both for LF and YP it are off-the-shelf trainings that do not require > much preperation. Speaking as a course maintainer for LF, keeping the YP course updated is actually a tremendous amount of work (I’m the co-maintainer for the LF YP course). However, the beginner slides tend not to need more than a few hours of updates every 6 months (which again is something I do). Either may appear off-the-shelf, but they aren’t from my perspective. ;) Thanks, Behan-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] samhain: add more tests and fix ret checks
Signed-off-by: Armin Kuster
---
lib/oeqa/runtime/cases/samhain.py | 31 +++
1 file changed, 27 insertions(+), 4 deletions(-)
diff --git a/lib/oeqa/runtime/cases/samhain.py
b/lib/oeqa/runtime/cases/samhain.py
index e4bae7b..5043a38 100644
--- a/lib/oeqa/runtime/cases/samhain.py
+++ b/lib/oeqa/runtime/cases/samhain.py
@@ -1,6 +1,7 @@
# Copyright (C) 2019 Armin Kuster
#
import re
+import os
from oeqa.runtime.case import OERuntimeTestCase
from oeqa.core.decorator.depends import OETestDepends
@@ -11,10 +12,32 @@ class SamhainTest(OERuntimeTestCase):
@OEHasPackage(['samhain-standalone'])
@OETestDepends(['ssh.SSHTest.test_ssh'])
-def test_samhain_standalone_help(self):
+def test_samhain_help(self):
+machine = self.td.get('MACHINE', '')
+status, output = self.target.run('echo "127.0.0.1 %s.localdomain %s"
>> /etc/hosts' % (machine, machine))
+msg = ("samhain can't append hosts. "
+ 'Status and output:%s and %s' % (status, output))
+self.assertEqual(status, 0, msg = msg)
+
status, output = self.target.run('samhain --help')
-match = re.search('Please report bugs to supp...@la-samhna.de.',
output)
+msg = ('samhain command does not work as expected. '
+ 'Status and output:%s and %s' % (status, output))
+self.assertEqual(status, 0, msg = msg)
+
+@OETestDepends(['samhain.SamhainTest.test_samhain_help'])
+def test_samhain_init_db(self):
+status, output = self.target.run('samhain -t init')
+match = re.search('FAILED: 0 ', output)
+if not match:
+msg = ('samhain database init had an unexpected failure. '
+ 'Status and output:%s and %s' % (status, output))
+self.assertEqual(status, 0, msg = msg)
+
+@OETestDepends(['samhain.SamhainTest.test_samhain_init_db'])
+def test_samhain_db_check(self):
+status, output = self.target.run('samhain -t check')
+match = re.search('FAILED: 0 ', output)
if not match:
-msg = ('samhain-standalone command does not work as expected. '
+msg = ('samhain errors found in db. '
'Status and output:%s and %s' % (status, output))
-self.assertEqual(status, 1, msg = msg)
+self.assertEqual(status, 0, msg = msg)
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] (no subject)
STOP -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [meta-ti] Meta-yocto-bsp fails to boot with META-TI [ Yocto-2.6.1]
HI Denys / Robert , Thanks , got the board boot up now. Followed below mentioned steps ( just in case if any one face similar problem ) 1) Erase the MMC => mmc dev 1 => mmc erase 0 512 2) Install TFTP server on host https://askubuntu.com/questions/201505/how-do-i-install-and-run-a-tftp-server 3) Transfer the dtb & zImage => setenv gatewayip 192.168.1.1 => setenv ipaddr 192.168.1.2 => setenv serverip 192.168.1.3 => ping 192.168.1.3 => tftp 0x8200 zImage => tftp 0x8800 am335x-boneblack.dtb => bootz 0x8200 - 0x8800 Thanks Ashish On Tue, May 7, 2019 at 10:44 PM Denys Dmytriyenko wrote: > On Tue, May 07, 2019 at 11:51:41AM -0500, Robert Nelson wrote: > > On Sun, May 5, 2019 at 9:43 AM AshishKumar Mishra > > wrote: > > > > > > Hi All , > > > I am starting to learn Yocto & following the manual from the Yocto > website > > > > > > I have added meta-ti to yocto and create the images > > > > > > Can team please provide some pointer to resolve the below error > > > or let me know if i am doing any thing wong. > > > > > > When flashed the images on SD card , the uboot is struck with below > mentioned error > > > > > > > > > U-Boot# > > > U-Boot# > > > U-Boot# > > > U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) > > > reading args > > > spl_load_image_fat_os: error reading image args, err - -1 > > > reading u-boot.img > > > reading u-boot.img > > > > > > > > > U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) > > > > Clear out your eMMC, you have a really old build of u-boot installed > > to eMMC that is blocking your new image.. > > Yes, I even had that mentioned in the corresponding README: > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/meta-yocto-bsp/README.hardware#n134 > > Denys > > > > Regards, > > > > -- > > Robert Nelson > > https://rcn-ee.com/ > > -- > > ___ > > meta-ti mailing list > > meta...@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/meta-ti > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] Eclipse (plugin, settings)
Nevertheless, you are welcome to resurrect the plugin, if you are willing to do the maintenance work. Yocto is what you make it. Alex On Wed, 8 May 2019 at 15:37, Zoran Stojsavljevic wrote: > > https://marc.info/?l=openembedded-core=155482339222316=2 > > (do not shoot the messenger, thank you) > > Zoran > ___ > > On Wed, May 8, 2019 at 1:11 PM Arno Steffens wrote: > > > > I want to use Eclipse as IDE for coding/debugging. > > What do I have to set to get the proper compiler prefixes and pathes, libs > > and includes ? > > Or any way to combine the environment setup with start of eclipse? > > > > I have seen there was a Eclipse plugin, but not for newer versions as > > 2019.03. > > > > Here (https://www.yoctoproject.org/software-item/eclipse-ide-plug-in/) is > > referenced to the eSDK manual, but no word about eclipse in it. Til now I > > just use SDK. > > > > Thanks > > Arno > > -- > > ___ > > 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse (plugin, settings)
https://marc.info/?l=openembedded-core=155482339222316=2 (do not shoot the messenger, thank you) Zoran ___ On Wed, May 8, 2019 at 1:11 PM Arno Steffens wrote: > > I want to use Eclipse as IDE for coding/debugging. > What do I have to set to get the proper compiler prefixes and pathes, libs > and includes ? > Or any way to combine the environment setup with start of eclipse? > > I have seen there was a Eclipse plugin, but not for newer versions as 2019.03. > > Here (https://www.yoctoproject.org/software-item/eclipse-ide-plug-in/) is > referenced to the eSDK manual, but no word about eclipse in it. Til now I > just use SDK. > > Thanks > Arno > -- > ___ > 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] Eclipse (plugin, settings)
I want to use Eclipse as IDE for coding/debugging. What do I have to set to get the proper compiler prefixes and pathes, libs and includes ? Or any way to combine the environment setup with start of eclipse? I have seen there was a Eclipse plugin, but not for newer versions as 2019.03. Here (https://www.yoctoproject.org/software-item/eclipse-ide-plug-in/) is referenced to the eSDK manual, but no word about eclipse in it. Til now I just use SDK. Thanks Arno -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDK build fails at latest thud
Done. Hopefully it went to right place. I noticed that core-image-minimal does not fail, but if you add for example 'bash' to it, it fails like it does on my image. t. Teemu On Tue, May 7, 2019 at 11:57 PM akuster808 wrote: > > Teemu, > > > > On 5/1/19 11:50 PM, Teemu K wrote: > > On Thu, Mar 28, 2019 at 6:36 AM Teemu K wrote: > >> On Mon, Mar 18, 2019 at 7:21 AM Teemu K wrote: > >>> On Fri, Mar 15, 2019 at 2:17 AM akuster wrote: > > > On 3/13/19 9:50 PM, Teemu K wrote: > > Hi, > > I noticed that when trying to build sdk on thud it fails on latest > version. Actually it broke somewhere between commits: > > 1cab405d88149fd63322a867c6adb4a80ba68db3 (old) > 7c76c5d78b850a9c1adccf8b11ed0164da608f1c (new) > > I'm using it with meta-freescale - layer to build image to iMX8. > > I'm using command 'populate_sdk' and it works fine on older version, > but newer version it fails with error: > > Can you provide the steps to reproduce? > >>> bitbake my-image-name -c populate_sdk > >>> > == > The following packages have unmet dependencies: > target-sdk-provides-dummy : Conflicts: coreutils > E: Unable to correct problems, you have held broken packages. > > > There is a change sitting in stable/thud-next: > > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stable/thud-next=af5cf78b275ab5226354337d25d8dc1c41a08904 > > which might be related. Can you try that branch? > > git://git.yoctoproject.org/poky-contrib stable/thud-next > >>> That did not solve the problem. I have coreutils in my image and it > >>> kept conflicting. When I removed coreutils from my image it solved > >>> that problem, but there were some problems with perl etc. From the > >>> working version all those are missing from > >>> target-sdk-provices-dummy.bb and my original image works just fine. > >> I see that thud-branch has gotten even more 'fixes' for this sdk thing > >> in last week, but the actual problem still stays. If image-recipe uses > >> coreutils - recipe sdk build fails there because > >> target-sdk-provides-dummy.bb has it listed. And if I remove that then > >> it fails on next package.In my case it's bash-dev. > >> > >> Does those changes need something different how sdk is build or how to > >> build sdk with those changes? I'm not sure why they are listed there > >> in the first place if it overrides the actual package and does not > >> provide 'dummy' if/when needed. > >> > >> To create sdk I use this command: bitbake -c populate_sdk > >> > >> -Teemu > > I updated to latest thud and this is still an issue. Isn't anyone else > > building sdk or what I'm doing wrong? > > > > I use command: bitbake -c populate_sdk to generate sdk. > > > > With unedited poky - meta layer it stops at error: > > > > -- > > The following packages have unmet dependencies: > > target-sdk-provides-dummy : Conflicts: coreutils > > -- > > > > If I remove that from > > poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb > > > > The next error is: > > -- > > The following packages have unmet dependencies: > > apt-dev : Depends: apt (= 1.2.24-r0) but it is not going to be installed > >Recommends: bash-dev > > -- > > > > If I remove that from file mentioned before the next error is about > > perl-dev. If I remove that it ends up on this error: > > > > -- > > > > The following packages have unmet dependencies: > > target-sdk-provides-dummy-dev : Depends: target-sdk-provides-dummy (= > > 1.0-r0) but it is not going to be installed > > -- > > > > For testing purposes I removed everything from that file except bash > > and after that the sdk generated just fine. > > > > I don't know enough about yocto/poky so what is the use of this > > target-sdk-provides-dummy thingie and why things are added there that > > keep breaking the sdk generation or do I need to generate sdk now > > someway differently? Atm. I'm either stuck on that older thud - > > version or I have to manually edit this > > target-sdk-provides-dummy-dev.bb - file. > > Can you log a bug. We are not seeing this in the AutoBuilders. > > https://bugzilla.yoctoproject.org/ > > > > -Teemu > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
