Re: [yocto] Populate /var/lib/opkg/status
On 12 September 2014 06:36, Dag Björklund d...@iki.fi wrote: Thanks, found this in the documentation now as well. Unfortunately I don't see a difference. Should I find a /var/lib/opkg/status file after adding the feature and building? Yes, assuming that you've told bitbake to use opkg and not dpkg or rpm (PACKAGE_CLASSES). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto 1.6 - beaglebone black - cape manager
On Thu, Sep 11, 2014 at 10:24 AM, TakkTakk tomek82...@gazeta.pl wrote: Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot. When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2, USR3 stay lit steadily. I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and everything was ok. Without the console serial cable (on UART0) is hard to guess what's going wrong. What is your o uEnv.txt content and the files inside the FAT partition? Regards, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.br http://www.embarcados.com.br/?utm_source=assinatura_diegoutm_medium=e-mailutm_campaign=Assinatura%20Email%20Diego /*long live rock 'n roll*/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] Mono updated to 3.8.0
I've updated support for Mono build in meta-mono master from 3.4.0 to 3.8.0 (the current release). I've performed basic build testing on an x64 host targetting an i.MX6 platform and succesfully run up a commercial application which makes use of console / X. If anybody has the time and inclination to perform build and smoke testing all feedback would be appreciated and incorporated into the README. Note that there is a still an outstanding issue with Mono not working correctly with ARM hardfp targets. ref: https://bugzilla.xamarin.com/show_bug.cgi?id=20239 I have been unable to determine why this is to date. If anybody is interested in working with me to track down the issue please contact me directly. Cheers, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] error-report-web: Sorting error tables
On Monday 08 September 2014 17:07:41 Roxana Ciobanu wrote: Add sorting functionality to the search results page. [YOCTO #6539] Signed-off-by: Roxana Ciobanu roxana.ciob...@intel.com Merged, thanks. Cheers, Paul -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [error-report-web][PATCH] Centering pagination when table rows are less than 10
When the number of errors returned by a search is less than 10,
the show rows menu disappears. This caused the pagination controls
at the bottom of the table to be right-aligned. This patch makes
sure the pagination controls remain center-aligned even when the
show rows menu does not display.
Signed-off-by: Belen Barros Pena belen.barros.p...@linux.intel.com
---
templates/search-details.html | 88 +--
1 file changed, 43 insertions(+), 45 deletions(-)
diff --git a/templates/search-details.html b/templates/search-details.html
index fbba5a9..b297cfe 100644
--- a/templates/search-details.html
+++ b/templates/search-details.html
@@ -318,50 +318,6 @@
/tbody
/table
div class=pagination
pagination-centered
- form
class=form-inline pull-right
- {% if no 10 %}
- labelShow
rows:/label
- form
- select
class=paginationLimit input-mini onchange=javascript:reload_params({'page':
'1', 'items' : +this.value })
-
{% ifequal items 10 %}
-
option selected=selected value = 1010/option
-
option value = 2525/option
-
option value = 5050/option
-
option value = 100100/option
-
option value = 150150/option
-
{%endifequal%}
-
{% ifequal items 25%}
-
option value = 1010/option
-
option selected=selected value = 2525/option
-
option value = 5050/option
-
option value = 100100/option
-
option value = 150150/option
-
{%endifequal%}
-
{% ifequal items 50%}
-
option value = 1010/option
-
option value = 2525/option
-
option selected=selected value = 5050/option
-
option value = 100100/option
-
option value = 150150/option
-
{%endifequal%}
-
{% ifequal items 100%}
-
option value = 1010/option
-
option value = 2525/option
-
option value = 5050/option
-
option selected=selected value = 100100/option
-
option value = 150150/option
-
{%endifequal%}
-
{% ifequal items 150%}
-
option value = 1010/option
-
option value = 2525/option
-
Re: [yocto] [meta-selinux][PATCH 0/3] Version number cleanup
Hello Xin, Just noticed that you pushed these patches to the meta-selinux repo but with your name and a slightly different commit message in one case. Other than forgetting to copy you on my initial message to the list was there a problem with my patches? Just want to be sure that the next time I send out patches I get them right if there was in fact an issue with these ones. Thanks, Philip On 09/08/2014 08:03 AM, Philip Tricca wrote: Patch set to use wildcards in the version numbers of the at and shadow bbappends and to remove the 3.4 kernel bbappend. Philip Tricca (3): shadow: Use wildcard for version number in bbappend. at: Use wildcard for version number in bbappend. linux-yocto: Remove bbappend for old 3.4 kernel. recipes-extended/at/at_%.bbappend |7 +++ recipes-extended/at/at_3.1.14.bbappend |7 --- recipes-extended/shadow/shadow_%.bbappend |5 + recipes-extended/shadow/shadow_4.1.4.3.bbappend |5 - recipes-kernel/linux/linux-yocto_3.4.bbappend |7 --- 5 files changed, 12 insertions(+), 19 deletions(-) create mode 100644 recipes-extended/at/at_%.bbappend delete mode 100644 recipes-extended/at/at_3.1.14.bbappend create mode 100644 recipes-extended/shadow/shadow_%.bbappend delete mode 100644 recipes-extended/shadow/shadow_4.1.4.3.bbappend delete mode 100644 recipes-kernel/linux/linux-yocto_3.4.bbappend -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto-bsp create question
Hi all, We are trying to create a custom BSP based off of valleyisland-64 using the yocto-bsp script. When we are presented choices for which BSP to branch from, valleyisland isn't one of the choices. We have tried all of the different kernel options presented, but no luck. I'm pretty sure we have the layers added correctly, as we can build valleyisland-32 and valleyisland-64 inside of hob with no problems. Any idea what we are doing wrong? All the best, Michael Michael Kotson Chief Technology Officer (Tel: (303) 412-2055 *E-Mail: mkot...@octagonsystems.com mailto:mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto-bsp create question
On Fri, 2014-09-12 at 10:07 -0600, Michael Kotson wrote: Hi all, We are trying to create a custom BSP based off of valleyisland-64 using the yocto-bsp script. When we are presented choices for which BSP to branch from, valleyisland isn’t one of the choices. We have tried all of the different kernel options presented, but no luck. I’m pretty sure we have the layers added correctly, as we can build valleyisland-32 and valleyisland-64 inside of hob with no problems. Any idea what we are doing wrong? Nothing that you're doing wrong, it's just that the valleyisland BSPs are built a little differently from the normal BSPs - instead of a machine branch, they do a merge of a valleyisland-io branch into another branch and the yocto-bsp tools aren't set up to do that. They'd need to be enhanced to enhanced to handle cases like that. I'd suggest filing a an enhancement bug so we can add that capability.. Thanks, Tom All the best, Michael Michael Kotson Chief Technology Officer (Tel: (303) 412-2055 *E-Mail: mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/2] Add support for MIPS32r2
Add support for MIPS32r2.
Signed-off-by: Vicente Olivert Riera vincent.ri...@imgtec.com
---
meta/conf/machine/include/tune-mips32r2.inc | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-mips32r2.inc
diff --git a/meta/conf/machine/include/tune-mips32r2.inc
b/meta/conf/machine/include/tune-mips32r2.inc
new file mode 100644
index 000..b36d00a
--- /dev/null
+++ b/meta/conf/machine/include/tune-mips32r2.inc
@@ -0,0 +1,25 @@
+DEFAULTTUNE ?= mips32r2
+
+require conf/machine/include/mips/arch-mips.inc
+
+TUNEVALID[mips32r2] = Enable mips32r2 specific processor optimizations
+TUNECONFLICTS[mips32r2] = n64 n32
+TUNE_CCARGS .= ${@bb.utils.contains(TUNE_FEATURES, mips32r2,
-march=mips32r2, , d)}
+
+AVAILTUNES += mips32r2 mips32r2el mips32r2-nf mips32r2el-nf
+
+TUNE_FEATURES_tune-mips32r2 = ${TUNE_FEATURES_tune-mips} mips32r2
+MIPSPKGSFX_VARIANT_tune-mips32r2 = mips32r2
+PACKAGE_EXTRA_ARCHS_tune-mips32r2 = mips mips32r2
+
+TUNE_FEATURES_tune-mips32r2el = ${TUNE_FEATURES_tune-mipsel} mips32r2
+MIPSPKGSFX_VARIANT_tune-mips32r2el = mips32r2el
+PACKAGE_EXTRA_ARCHS_tune-mips32r2el = mipsel mips32r2el
+
+TUNE_FEATURES_tune-mips32r2-nf = ${TUNE_FEATURES_tune-mips-nf} mips32r2
+MIPSPKGSFX_VARIANT_tune-mips32r2-nf = mips32r2
+PACKAGE_EXTRA_ARCHS_tune-mips32r2-nf = mips-nf mips32r2-nf
+
+TUNE_FEATURES_tune-mips32r2el-nf = ${TUNE_FEATURES_tune-mipsr2el-nf} mips32r2
+MIPSPKGSFX_VARIANT_tune-mips32r2el-nf = mips32r2el
+PACKAGE_EXTRA_ARCHS_tune-mips32r2el-nf = mipsel-nf mips32r2el-nf
--
1.7.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/2] Add support for MIPS32r2 and CI20 to Yocto
Add support for the MIPS Creator CI20 machine. That board has a MIPS32r2 architecture so we also add support for that. Vicente Olivert Riera (2): Add support for MIPS32r2 Add MIPS Creator CI20 machine meta-yocto-bsp/conf/machine/ci20.conf | 10 ++ meta/conf/machine/include/tune-mips32r2.inc | 25 + 2 files changed, 35 insertions(+), 0 deletions(-) create mode 100644 meta-yocto-bsp/conf/machine/ci20.conf create mode 100644 meta/conf/machine/include/tune-mips32r2.inc -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/2] Add MIPS Creator CI20 machine
Add support for the MIPS Creator CI20 machine. You will need to build a working kernel for this board using this kernel repository on GitHub: https://github.com/MIPS/CI20_linux More information about this board can be found at: http://elinux.org/MIPS_Creator_CI20 Signed-off-by: Vicente Olivert Riera vincent.ri...@imgtec.com --- meta-yocto-bsp/conf/machine/ci20.conf | 10 ++ 1 files changed, 10 insertions(+), 0 deletions(-) create mode 100644 meta-yocto-bsp/conf/machine/ci20.conf diff --git a/meta-yocto-bsp/conf/machine/ci20.conf b/meta-yocto-bsp/conf/machine/ci20.conf new file mode 100644 index 000..bd26815 --- /dev/null +++ b/meta-yocto-bsp/conf/machine/ci20.conf @@ -0,0 +1,10 @@ +#@TYPE: Machine +#@NAME: CI20 +#@DESCRIPTION: MIPS Creator CI20 + +require conf/machine/include/tune-mips32r2.inc + +DEFAULTTUNE = mips32r2el +MACHINE_FEATURES = serial +SERIAL_CONSOLE = 115200 ttyS4 +IMAGE_FSTYPES ?= tar.bz2 -- 1.7.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
Just double checking that you are specifying the toolchain root location as your top level build directory (the one above /conf/local.conf - the directory where you run bitbake). Yes that occurred to me too, since the phrasing is a bit unclear. I tried both. Here's a depiction of my directory structure: oe-core | build | conf (including local.conf) | downloads | tmp-eglibc | environment-setup-blahblah | etc. | etcc | bitbake | gcc-toolchain | meta | etc. lots more I tried with the root at build, and in build/tmp-eglibc with no luck. Is it possible the toolchain didn't get built? I'm just wondering since that's what the error claims. Is there any way to confirm that the toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but our system is large and I'm not familiar with every aspect of it. Is it possible some other settings elsewhere got changed in a way that would prevent the toolchain from building? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/2] Add MIPS Creator CI20 machine
On 14-09-12 12:35 PM, Vicente Olivert Riera wrote: Add support for the MIPS Creator CI20 machine. You will need to build a working kernel for this board using this kernel repository on GitHub: https://github.com/MIPS/CI20_linux More information about this board can be found at: http://elinux.org/MIPS_Creator_CI20 All of the meta-yocto-bsp reference machines are using the kernel, and kernel version of linux-yocto* so we can ensure a consistent update cadence and set of features. Something that I'd like to see continue. I can see how the ability to re-use the tune files makes sense, but the BSP should follow the format and structure of the existing ones, otherwise, the value in pulling it into the common layers isn't there. Bruce Signed-off-by: Vicente Olivert Riera vincent.ri...@imgtec.com --- meta-yocto-bsp/conf/machine/ci20.conf | 10 ++ 1 files changed, 10 insertions(+), 0 deletions(-) create mode 100644 meta-yocto-bsp/conf/machine/ci20.conf diff --git a/meta-yocto-bsp/conf/machine/ci20.conf b/meta-yocto-bsp/conf/machine/ci20.conf new file mode 100644 index 000..bd26815 --- /dev/null +++ b/meta-yocto-bsp/conf/machine/ci20.conf @@ -0,0 +1,10 @@ +#@TYPE: Machine +#@NAME: CI20 +#@DESCRIPTION: MIPS Creator CI20 + +require conf/machine/include/tune-mips32r2.inc + +DEFAULTTUNE = mips32r2el +MACHINE_FEATURES = serial +SERIAL_CONSOLE = 115200 ttyS4 +IMAGE_FSTYPES ?= tar.bz2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Enabling Ramdisk Support
All, I am having some issues with initrd using u-boot and yocto. My current .config file in build/tmp/work/mitysom_5csx-poky-linux-gnueabi/linux-mitysom-5csx/3.12-r2/linux-socfpga-socfpga-3.12-7cb4fc4 has the following settings: CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_RD_GZIP=y Whenever I attempt to boot up with an initrd, I get a message saying that the kernel was unable to mount the rootfs. What concerns me, though, is I don't see any RAMDISK initialization messages on startup. Looking online, I figure I should see something like this: [root]# dmesg | grep RAMDISK RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize When I boot up, or at least some sort of error from RAMDISK. Is there a way I can verify that this option is actually being built into my system? -Nick Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.commailto:nicholas.cr...@saabsensis.com This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote: Just double checking that you are specifying the toolchain root location as your top level build directory (the one above /conf/local.conf - the directory where you run bitbake). Yes that occurred to me too, since the phrasing is a bit unclear. I tried both. Here's a depiction of my directory structure: oe-core | build | conf (including local.conf) | downloads | tmp-eglibc | environment-setup-blahblah | etc. | etcc | bitbake | gcc-toolchain | meta | etc. lots more I tried with the root at build, and in build/tmp-eglibc with no luck. Is it possible the toolchain didn't get built? What happens when you source your environment script? You should have your path set up to find your cross toolchain. If that's the case, you should be able to run the toolchain on the command line. I work with the powerpc toolchain, so I can cross-compile a simple test app after sourcing my env script: powerpc64-poky-linux-gcc main.c -o tst and verify I have generated a 64-bit powerpc ELF executable with file tst I'm just wondering since that's what the error claims. Is there any way to confirm that the toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but our system is large and I'm not familiar with every aspect of it. Is it possible some other settings elsewhere got changed in a way that would prevent the toolchain from building? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Basic build fails
Hi all, I am new to the yocto project and was following the steps given in the quick start guide. I made a slight change as given in the superuser section. I used the fetchall option to get all the packages first and then started the build, now when i use this command bitbake -k core-image-sato i get the following error / ERROR: Task 595 (/home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2729 tasks of which 1784 didn't need to be rerun and 1 failed. No currently running tasks (2729 of 5634) Summary: 1 task failed: /home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. / any idea or hint where i might be going wrong? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Basic build fails
On 12 September 2014 20:42, Arun Kumar arunkr.li...@gmail.com wrote: Hi all, I am new to the yocto project and was following the steps given in the quick start guide. I made a slight change as given in the superuser section. I used the fetchall option to get all the packages first and then started the build, now when i use this command bitbake -k core-image-sato i get the following error / ERROR: Task 595 (/home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2729 tasks of which 1784 didn't need to be rerun and 1 failed. No currently running tasks (2729 of 5634) Summary: 1 task failed: /home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. / any idea or hint where i might be going wrong? You've trimmed the output at just the place where it was telling you what went wrong. Re-run bitbake gcc-cross, and paste the output of that. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/2] Add MIPS Creator CI20 machine
On 12 September 2014 17:57, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 14-09-12 12:35 PM, Vicente Olivert Riera wrote: Add support for the MIPS Creator CI20 machine. You will need to build a working kernel for this board using this kernel repository on GitHub: https://github.com/MIPS/CI20_linux More information about this board can be found at: http://elinux.org/MIPS_Creator_CI20 All of the meta-yocto-bsp reference machines are using the kernel, and kernel version of linux-yocto* so we can ensure a consistent update cadence and set of features. Something that I'd like to see continue. I can see how the ability to re-use the tune files makes sense, but the BSP should follow the format and structure of the existing ones, otherwise, the value in pulling it into the common layers isn't there. What Bruce said. You've a specific machine that needs a specific kernel, so this can happily live on as a Yocto-compatible BSP layer outside of meta-yocto. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto-bsp create question
Hi Tom, Thanks for the response. I filed an enhancement request, but in the meantime is there a preferred method to create our own BSP from Valleyisland? All the best, Michael Michael Kotson Chief Technology Officer OTel: (303) 412-2055 TE-Mail: mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -Original Message- From: Tom Zanussi [mailto:tom.zanu...@intel.com] Sent: Friday, September 12, 2014 10:26 AM To: Michael Kotson Cc: yocto@yoctoproject.org Subject: Re: [yocto] yocto-bsp create question On Fri, 2014-09-12 at 10:07 -0600, Michael Kotson wrote: Hi all, We are trying to create a custom BSP based off of valleyisland-64 using the yocto-bsp script. When we are presented choices for which BSP to branch from, valleyisland isn’t one of the choices. We have tried all of the different kernel options presented, but no luck. I’m pretty sure we have the layers added correctly, as we can build valleyisland-32 and valleyisland-64 inside of hob with no problems. Any idea what we are doing wrong? Nothing that you're doing wrong, it's just that the valleyisland BSPs are built a little differently from the normal BSPs - instead of a machine branch, they do a merge of a valleyisland-io branch into another branch and the yocto-bsp tools aren't set up to do that. They'd need to be enhanced to enhanced to handle cases like that. I'd suggest filing a an enhancement bug so we can add that capability.. Thanks, Tom All the best, Michael Michael Kotson Chief Technology Officer (Tel: (303) 412-2055 *E-Mail: mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto-bsp create question
On Fri, 2014-09-12 at 15:09 -0600, Michael Kotson wrote: Hi Tom, Thanks for the response. I filed an enhancement request, but in the meantime is there a preferred method to create our own BSP from Valleyisland? Thanks for filing the request, it's been assigned to me and I'll try to get to it as soon as I can. In the meantime, I guess what I'd suggest is that you start by copying the valleyisland bsp you're interested in and modifying it to suit your needs. This is essentially what users had to do before yocto-bsp existed and is the reason it was created - to take all the cut-and-paste drudgery out of that exercise. Tom All the best, Michael Michael Kotson Chief Technology Officer OTel: (303) 412-2055 TE-Mail: mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -Original Message- From: Tom Zanussi [mailto:tom.zanu...@intel.com] Sent: Friday, September 12, 2014 10:26 AM To: Michael Kotson Cc: yocto@yoctoproject.org Subject: Re: [yocto] yocto-bsp create question On Fri, 2014-09-12 at 10:07 -0600, Michael Kotson wrote: Hi all, We are trying to create a custom BSP based off of valleyisland-64 using the yocto-bsp script. When we are presented choices for which BSP to branch from, valleyisland isn’t one of the choices. We have tried all of the different kernel options presented, but no luck. I’m pretty sure we have the layers added correctly, as we can build valleyisland-32 and valleyisland-64 inside of hob with no problems. Any idea what we are doing wrong? Nothing that you're doing wrong, it's just that the valleyisland BSPs are built a little differently from the normal BSPs - instead of a machine branch, they do a merge of a valleyisland-io branch into another branch and the yocto-bsp tools aren't set up to do that. They'd need to be enhanced to enhanced to handle cases like that. I'd suggest filing a an enhancement bug so we can add that capability.. Thanks, Tom All the best, Michael Michael Kotson Chief Technology Officer (Tel: (303) 412-2055 *E-Mail: mkot...@octagonsystems.com NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto 1.6 - beaglebone black - cape manager
i build core-image-base
My uEnv.txt content :
kernel_file=uImage
console=ttyO0,115200n8
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext4 rootwait
loaduimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
mmcargs=setenv bootargs console=${console} root=${mmcroot}
rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loaduimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}
optargs=quiet drm.debug=7 capemgr.enable_partno=BB-UART4
--
files inside the FAT partition:
uEnv.txt
uImage
u-boot.img
MLO
dtbs/am335x-boneblack.dtb
2014-09-12 11:55 GMT+02:00 Diego Sueiro diego.sue...@gmail.com:
On Thu, Sep 11, 2014 at 10:24 AM, TakkTakk tomek82...@gazeta.pl wrote:
Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot.
When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2,
USR3 stay lit steadily.
I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and
everything was ok.
Without the console serial cable (on UART0) is hard to guess what's going
wrong.
What is your o uEnv.txt content and the files inside the FAT partition?
Regards,
--
*dS
Diego Sueiro
Administrador do Embarcados
www.embarcados.com.br
/*long live rock 'n roll*/
--
TakTak
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
Yes - I can source the script, and I do successfully get my path updated. That's unfortunate. I can run the toolchain on the command line, but the developers I am working with need to use Eclipse. The plug-in seems like the right solution, so I would very much like to get this to work. It occurred to me that these issues might be because I'm using an older version of bitbake: $ bitbake --version BitBake Build Tool Core version 1.20.0, bitbake version 1.20.0 Could that have something to do with the failure? On Fri, Sep 12, 2014 at 12:24 PM, Bob Cochran yo...@mindchasers.com wrote: On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote: Just double checking that you are specifying the toolchain root location as your top level build directory (the one above /conf/local.conf - the directory where you run bitbake). Yes that occurred to me too, since the phrasing is a bit unclear. I tried both. Here's a depiction of my directory structure: oe-core | build | conf (including local.conf) | downloads | tmp-eglibc | environment-setup-blahblah | etc. | etcc | bitbake | gcc-toolchain | meta | etc. lots more I tried with the root at build, and in build/tmp-eglibc with no luck. Is it possible the toolchain didn't get built? What happens when you source your environment script? You should have your path set up to find your cross toolchain. If that's the case, you should be able to run the toolchain on the command line. I work with the powerpc toolchain, so I can cross-compile a simple test app after sourcing my env script: powerpc64-poky-linux-gcc main.c -o tst and verify I have generated a 64-bit powerpc ELF executable with file tst I'm just wondering since that's what the error claims. Is there any way to confirm that the toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but our system is large and I'm not familiar with every aspect of it. Is it possible some other settings elsewhere got changed in a way that would prevent the toolchain from building? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Basic build fails
Thanks for the reply ross, but the build noise is too much form me to put it in here. I will post the last few lines of which i can make some sense, but the rest is somewhat incomprehensible. /--- | make[1]: *** [s-attrtab] Killed | make[1]: *** Waiting for unfinished jobs | make[1]: Leaving directory `/home/arun/Documents/Dev/yocto/tmp/work/x86_64-poky-linux/gcc-cross-i586/4.9.1-r0/gcc-4.9.1/build.x86_64-linux.i586-poky-linux/gcc' | make: *** [all-gcc] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /home/arun/Documents/Dev/yocto/build/../tmp/work/x86_64-poky-linux/gcc-cross-i586/4.9.1-r0/temp/log.do_compile.29857) ERROR: Task 595 (/home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2729 tasks of which 2728 didn't need to be rerun and 1 failed. No currently running tasks (307 of 5634) Summary: 1 task failed: /home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile Summary: There was 1 ERROR message shown, returning a non-zero exit code. /--- here is the pastebin link to the whole error http://pastebin.com/Y1JsA8dt hope this helps On Saturday 13 September 2014 01:37 AM, Burton, Ross wrote: On 12 September 2014 20:42, Arun Kumar arunkr.li...@gmail.com wrote: Hi all, I am new to the yocto project and was following the steps given in the quick start guide. I made a slight change as given in the superuser section. I used the fetchall option to get all the packages first and then started the build, now when i use this command bitbake -k core-image-sato i get the following error / ERROR: Task 595 (/home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2729 tasks of which 1784 didn't need to be rerun and 1 failed. No currently running tasks (2729 of 5634) Summary: 1 task failed: /home/arun/Documents/Dev/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_compile Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. / any idea or hint where i might be going wrong? You've trimmed the output at just the place where it was telling you what went wrong. Re-run bitbake gcc-cross, and paste the output of that. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
