[yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

[Jerry Lian]

Hi, all:

I have a basic question: how to tell the difference between
"core-image-minimal" and "core-image-base"?
* If we look at file* \poky\meta\recipes-core\images\core-image-base.bb
*
===
SUMMARY = "A console-only image that fully supports the target device
hardware."

IMAGE_FEATURES += "splash"

LICENSE = "MIT"

inherit core-image
===
* how can we tell that "core-image-base" will include "support for a
variety of hardware such as WIFI, bluetooth...", as compare to
"core-image-minimal"?
* Do I miss any other document that I need to read?

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

[yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

[Jerry Lian]

Hi, all:

I have a basic question: how to tell the difference between
"core-image-minimal" and "core-image-base"?
* If we look at file* \poky\meta\recipes-core\images\core-image-base.bb
*

===
SUMMARY = "A console-only image that fully supports the target device
hardware."

IMAGE_FEATURES += "splash"

LICENSE = "MIT"

inherit core-image

===
* how can we tell that "core-image-base" will include "support for a
variety of hardware such as WIFI, bluetooth...", as compare to
"core-image-minimal"?
* Do I miss any other document that I need to read?

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

Re: [yocto] Basic question: "core-image-minimal" v.s "core-image-base" ?

[Jerry Lian]

Thanks for answers from Ross and Andre.
Now further question:
* If we look at file \poky\meta\recipes-core\images\core-image-minimal.bb
<http://core-image-base.bb>

SUMMARY = "A small image just capable of allowing a device to boot."

IMAGE_INSTALL = "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL}"

IMAGE_LINGUAS = " "

LICENSE = "MIT"

inherit core-image

* "inherit core-image" *comes after* "IMAGE_INSTALL = ..."
* Will the "IMAGE_INSTALL" in this file be overridden by "IMAGE_INSTALL" in
"core-image"

So what is the rule for "overridden"?

On Tue, Oct 10, 2017 at 6:07 PM, Andre McCurdy  wrote:

> On Fri, Oct 6, 2017 at 1:40 PM, Jerry Lian  wrote:
> > Hi, all:
> >
> > I have a basic question: how to tell the difference between
> > "core-image-minimal" and "core-image-base"?
> > * If we look at file \poky\meta\recipes-core\images\core-image-base.bb
> > 
> ===
> > SUMMARY = "A console-only image that fully supports the target device
> > hardware."
> >
> > IMAGE_FEATURES += "splash"
> >
> > LICENSE = "MIT"
> >
> > inherit core-image
> > 
> ===
> > * how can we tell that "core-image-base" will include "support for a
> variety
> > of hardware such as WIFI, bluetooth...", as compare to
> "core-image-minimal"?
> > * Do I miss any other document that I need to read?
>
> core-image-base takes the default value of IMAGE_INSTALL from
> meta/classes/core-image.bbclass, but core-image-minimal over-rides the
> default value and effectively removes packagegroup-base-extended.
>
> See meta/recipes-core/packagegroups/packagegroup-base.bb for more
> details of what gets pulled in by packagegroup-base-extended.
>
> > Thanks!
> > Jerry
> >
> > --
> > ___
> > 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] yocto documentation: no content, no PDF?

[Jerry Lian]

Just wondering:
* As an active project, why yocto documentation does not provide a content
(better be clickable)?
* Or PDF format for easy printing.

Isn't good documentation the basic requirement for a good project?
 (By the way, the yocto homepage is also ugly!)

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

[yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not sure whether it is a bug or an error:
* Quite often, bitbake will fail before finishing, with message like: ...
task failed with exit code 1...
* But if you rerun bitbake, it will continue to build.
* So sometimes I have to rerun many times for finish one build 
annoying!
(by the way, my CPU can run 16 threads)

Any idea to clear this annoying bug?
thanks.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)

On Wed, Nov 8, 2017 at 11:15 AM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:

> On Wed, Nov 8, 2017 at 5:13 PM, Jerry Lian  wrote:
> > So according to what you said: the build will fail no matter what.
> > But that is not my observation: my build succeed eventually (but you just
> > need to rerun many times)!!!
>
> ah. sorry, i missed that part. So then it's probably a bug in the
> recipe, missing dependency or something along these lines. It would be
> legit to report this bug then.
>
>
> >
> > On Wed, Nov 8, 2017 at 10:53 AM, Nicolas Dechesne
> >  wrote:
> >>
> >> On Wed, Nov 8, 2017 at 4:49 PM, Jerry Lian 
> wrote:
> >> > I am not sure whether it is a bug or an error:
> >> > * Quite often, bitbake will fail before finishing, with message like:
> >> > ...
> >> > task failed with exit code 1...
> >> > * But if you rerun bitbake, it will continue to build.
> >> > * So sometimes I have to rerun many times for finish one build 
> >> > annoying!
> >> > (by the way, my CPU can run 16 threads)
> >> >
> >> > Any idea to clear this annoying bug?
> >>
> >> it's not a bug. bitbake is using parallel tasks a lot. At any time it
> >> is running N tasks. When one task fails, it will wait for N-1 ongoing
> >> tasks to finish, and then stops.
> >>
> >> If you restart again, it will likely try N new tasks again, and the
> >> same task that failed,  will fail again, it will wait for N-1 tasks to
> >> complete.
> >>
> >> if you do that several times, you will  end up in a situation where
> >> the only task that can run is the 'failing' one, so it will try 1 task
> >> and fail immediately.
> >>
> >> > thanks.
> >> >
> >> > --
> >> > ___
> >> > yocto mailing list
> >> > yocto@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/yocto
> >> >
> >
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
wrote:

> Most likely a dependency problem of the package which fails w/ exit code 1.
> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>
> Cheers
> Eric
>
>
> Am 08.11.2017 16:49, schrieb Jerry Lian:
>
> I am not sure whether it is a bug or an error: * Quite often, bitbake will
>> fail before finishing, with message like: ... task failed with exit code
>> 1... * But if you rerun bitbake, it will continue to build. * So sometimes
>> I have to rerun many times for finish one build  annoying! (by the way,
>> my CPU can run 16 threads)
>>
>> Any idea to clear this annoying bug? thanks.
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 11:21 AM, Burton, Ross  wrote:

> On 8 November 2017 at 15:49, Jerry Lian  wrote:
>
>> I am not sure whether it is a bug or an error:
>> * Quite often, bitbake will fail before finishing, with message like: ...
>> task failed with exit code 1...
>> * But if you rerun bitbake, it will continue to build.
>> * So sometimes I have to rerun many times for finish one build 
>> annoying!
>> (by the way, my CPU can run 16 threads)
>>
>
> If you tell us what recipe is failing, and what the actual error is, then
> we may be able to help.  Generally this is a bug in the makefiles that the
> recipe is building and not a problem with Yocto itself.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

So that is further tricky part:
* it may fail when finishing 20%, 40% 60%, 80%
* And the failure last time may not appear next time.
* So it just pop-up randomly

(By the way, I just build brand new PC with 16 threads CPU, 32G memory, and
install Ubuntu 16.4.3 with ESXI-6.5)
(so really confused)



On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross  wrote:

> The autobuilder does about 50 builds a night using pure poky and we don't
> see this, so again: what recipe and what errors?
>
> Ross
>
> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>
>> I am not talking about my own layer or recipe.
>> It happens even when I run the demo QEMU/beaglebone builds.
>> (I just download poky, and make NO modifications)
>>
>>
>>
>>
>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
>> wrote:
>>
>>> Most likely a dependency problem of the package which fails w/ exit code
>>> 1.
>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>
>>> Cheers
>>> Eric
>>>
>>>
>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>
>>> I am not sure whether it is a bug or an error: * Quite often, bitbake
>>>> will fail before finishing, with message like: ... task failed with exit
>>>> code 1... * But if you rerun bitbake, it will continue to build. * So
>>>> sometimes I have to rerun many times for finish one build  annoying!
>>>> (by the way, my CPU can run 16 threads)
>>>>
>>>> Any idea to clear this annoying bug? thanks.
>>>>
>>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

Isn't my problem clear: the failure pop-up randomly!
Do you mean the random failure also help you for debugging?




On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross  wrote:

> Well next time it happens feel free to reply to this thread. Otherwise
> you're asking us "fix my problem" without saying what the problem is.
>
> Ross
>
> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>
>> So that is further tricky part:
>> * it may fail when finishing 20%, 40% 60%, 80%
>> * And the failure last time may not appear next time.
>> * So it just pop-up randomly
>>
>> (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
>> and install Ubuntu 16.4.3 with ESXI-6.5)
>> (so really confused)
>>
>>
>>
>> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
>> wrote:
>>
>>> The autobuilder does about 50 builds a night using pure poky and we
>>> don't see this, so again: what recipe and what errors?
>>>
>>> Ross
>>>
>>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>>
>>>> I am not talking about my own layer or recipe.
>>>> It happens even when I run the demo QEMU/beaglebone builds.
>>>> (I just download poky, and make NO modifications)
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
>>>> wrote:
>>>>
>>>>> Most likely a dependency problem of the package which fails w/ exit
>>>>> code 1.
>>>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>>>
>>>>> Cheers
>>>>> Eric
>>>>>
>>>>>
>>>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>>>
>>>>> I am not sure whether it is a bug or an error: * Quite often, bitbake
>>>>>> will fail before finishing, with message like: ... task failed with exit
>>>>>> code 1... * But if you rerun bitbake, it will continue to build. * So
>>>>>> sometimes I have to rerun many times for finish one build  annoying!
>>>>>> (by the way, my CPU can run 16 threads)
>>>>>>
>>>>>> Any idea to clear this annoying bug? thanks.
>>>>>>
>>>>>
>>>>
>>>> --
>>>> ___
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto documentation: no content, no PDF?

[Jerry Lian]

The mega-manual should have content like: at least one line for each
chapter, so that we can have a big picture.

By the way, where is the "real docs"?




On Wed, Nov 8, 2017 at 11:30 AM, Burton, Ross  wrote:

> On 8 November 2017 at 15:41, Jerry Lian  wrote:
>
>> Just wondering:
>> * As an active project, why yocto documentation does not provide a
>> content (better be clickable)?
>>
>
> The megamanual (Complete Documentation) doesn't have a top-level table of
> contents as that basically exists to search globally.  The real docs (such
> as Tasks Manual) have a top level table of contents.
>
> * Or PDF format for easy printing.
>>
>
> That would be massive.  The source is in git as docbook so it's fairly
> simple to generate a PDF.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

Really, only me got this problem?




On Wed, Nov 8, 2017 at 11:40 AM, Burton, Ross  wrote:

> The failure doesn't happen for anyone else.  You're literally saying "it
> breaks" but not even saying what "it" is, or how "it" is breaking.
>
> Ross
>
> On 8 November 2017 at 16:38, Jerry Lian  wrote:
>
>> Isn't my problem clear: the failure pop-up randomly!
>> Do you mean the random failure also help you for debugging?
>>
>>
>>
>>
>> On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross 
>> wrote:
>>
>>> Well next time it happens feel free to reply to this thread. Otherwise
>>> you're asking us "fix my problem" without saying what the problem is.
>>>
>>> Ross
>>>
>>> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>>>
>>>> So that is further tricky part:
>>>> * it may fail when finishing 20%, 40% 60%, 80%
>>>> * And the failure last time may not appear next time.
>>>> * So it just pop-up randomly
>>>>
>>>> (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
>>>> and install Ubuntu 16.4.3 with ESXI-6.5)
>>>> (so really confused)
>>>>
>>>>
>>>>
>>>> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
>>>> wrote:
>>>>
>>>>> The autobuilder does about 50 builds a night using pure poky and we
>>>>> don't see this, so again: what recipe and what errors?
>>>>>
>>>>> Ross
>>>>>
>>>>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>>>>
>>>>>> I am not talking about my own layer or recipe.
>>>>>> It happens even when I run the demo QEMU/beaglebone builds.
>>>>>> (I just download poky, and make NO modifications)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz <
>>>>>> e...@sw-optimization.com> wrote:
>>>>>>
>>>>>>> Most likely a dependency problem of the package which fails w/ exit
>>>>>>> code 1.
>>>>>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>>>>>
>>>>>>> Cheers
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>>>>>
>>>>>>> I am not sure whether it is a bug or an error: * Quite often,
>>>>>>>> bitbake will fail before finishing, with message like: ... task failed 
>>>>>>>> with
>>>>>>>> exit code 1... * But if you rerun bitbake, it will continue to build. 
>>>>>>>> * So
>>>>>>>> sometimes I have to rerun many times for finish one build  
>>>>>>>> annoying!
>>>>>>>> (by the way, my CPU can run 16 threads)
>>>>>>>>
>>>>>>>> Any idea to clear this annoying bug? thanks.
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> ___
>>>>>> yocto mailing list
>>>>>> yocto@yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

So bad: I do use Ryzen-7!
I will try new kernel, how about Ubuntu-17? or should be latest Debian?

On Wed, Nov 8, 2017 at 11:47 AM, Jerry Lian  wrote:

> Really, only me got this problem?
>
>
>
>
> On Wed, Nov 8, 2017 at 11:40 AM, Burton, Ross 
> wrote:
>
>> The failure doesn't happen for anyone else.  You're literally saying "it
>> breaks" but not even saying what "it" is, or how "it" is breaking.
>>
>> Ross
>>
>> On 8 November 2017 at 16:38, Jerry Lian  wrote:
>>
>>> Isn't my problem clear: the failure pop-up randomly!
>>> Do you mean the random failure also help you for debugging?
>>>
>>>
>>>
>>>
>>> On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross 
>>> wrote:
>>>
>>>> Well next time it happens feel free to reply to this thread. Otherwise
>>>> you're asking us "fix my problem" without saying what the problem is.
>>>>
>>>> Ross
>>>>
>>>> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>>>>
>>>>> So that is further tricky part:
>>>>> * it may fail when finishing 20%, 40% 60%, 80%
>>>>> * And the failure last time may not appear next time.
>>>>> * So it just pop-up randomly
>>>>>
>>>>> (By the way, I just build brand new PC with 16 threads CPU, 32G
>>>>> memory, and install Ubuntu 16.4.3 with ESXI-6.5)
>>>>> (so really confused)
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
>>>>> wrote:
>>>>>
>>>>>> The autobuilder does about 50 builds a night using pure poky and we
>>>>>> don't see this, so again: what recipe and what errors?
>>>>>>
>>>>>> Ross
>>>>>>
>>>>>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>>>>>
>>>>>>> I am not talking about my own layer or recipe.
>>>>>>> It happens even when I run the demo QEMU/beaglebone builds.
>>>>>>> (I just download poky, and make NO modifications)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz <
>>>>>>> e...@sw-optimization.com> wrote:
>>>>>>>
>>>>>>>> Most likely a dependency problem of the package which fails w/ exit
>>>>>>>> code 1.
>>>>>>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>> Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>>>>>>
>>>>>>>> I am not sure whether it is a bug or an error: * Quite often,
>>>>>>>>> bitbake will fail before finishing, with message like: ... task 
>>>>>>>>> failed with
>>>>>>>>> exit code 1... * But if you rerun bitbake, it will continue to build. 
>>>>>>>>> * So
>>>>>>>>> sometimes I have to rerun many times for finish one build  
>>>>>>>>> annoying!
>>>>>>>>> (by the way, my CPU can run 16 threads)
>>>>>>>>>
>>>>>>>>> Any idea to clear this annoying bug? thanks.
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> ___
>>>>>>> yocto mailing list
>>>>>>> yocto@yoctoproject.org
>>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto problem for Ryzen-7 cpu

[Jerry Lian]

(my Gmail does not accept new message for same subject? so I open a new
thread)

So bad: I do use Ryzen-7.
will Ubuntu-17 or latest Debian fix the problem?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto problem for Ryzen-7 cpu

[Jerry Lian]

(weird, yocto mails to me blocked by my gmail, treated as spam?)

Anyway, just change to Ubuntu-17, run first build, succeed with no
failures, good sign!
Will run more and see.





On Wed, Nov 8, 2017 at 12:06 PM, Jerry Lian  wrote:

> (my Gmail does not accept new message for same subject? so I open a new
> thread)
>
> So bad: I do use Ryzen-7.
> will Ubuntu-17 or latest Debian fix the problem?
>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto documentation: no content, no PDF?

[Jerry Lian]

It works! The PDF files are much better to read with better content.
(The HTML document on website is almost useless without the content)

Thank you guys!

On Thu, Nov 9, 2017 at 12:32 PM, Leonardo Sandoval <
leonardo.sandoval.gonza...@linux.intel.com> wrote:

> On Wed, 8 Nov 2017 16:30:39 +
> "Burton, Ross"  wrote:
>
> > On 8 November 2017 at 15:41, Jerry Lian  wrote:
> >
> > > Just wondering:
> > > * As an active project, why yocto documentation does not provide a
> content
> > > (better be clickable)?
> > >
> >
> > The megamanual (Complete Documentation) doesn't have a top-level table of
> > contents as that basically exists to search globally.  The real docs
> (such
> > as Tasks Manual) have a top level table of contents.
> >
> > * Or PDF format for easy printing.
> > >
>
> Try running
>
> make pdf DOC=ref-manual
>
>
> (then drink so coffee and wait) After it, the pdf manual is there. There
> are other manuals as well, this is just an example cmd.
>
> Leo
>
> >
> > That would be massive.  The source is in git as docbook so it's fairly
> > simple to generate a PDF.
>
>
>
> >
> > Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add support for "usb WIFI dongle"?

[Jerry Lian]

I am confused on adding support for "usb WIFI dongle":
* My boards do NOT have WIFI capability, so I will add a "usb WIFI dongle".
  (I have two boards: Raspberri-PI-2, SIMATIC IOT-2020)
* Suppose we start from "core-image-sato"
* What should I do to add support for "usb WIFI dongle"
* After we build/boot the image, how can we verify and bring the WIFI up?

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

Re: [yocto] How to add support for "usb WIFI dongle"?

[Jerry Lian]

Thanks Alan, I follow your instruction and it works eventually!

But I got another question:

   - I am using official Raspberry-PI WIFI dongle (BCM43143)
   - I configure kernel so that driver "brcm80211" is enabled, however,
   WIFI is not working.
   - Then I add driver "ipw2x00", then WIFI works.
   - So my question, why do we need both "ipw2x00" and "brcm80211" for
   official Raspberry-PI WIFI dongle?
   - (Sometimes the WIFI dongle works if I add drivers: "brcm80211,
   iwlwifi, rt2x00", without "ipw2x00", so I am really confused!)

Thanks!







On Tue, Nov 21, 2017 at 12:04 PM, Alan Martinovic  wrote:

> Some hints on where to start at:
>
> > What should I do to add support for "usb WIFI dongle"
>
> Am guessing the dongle works with Raspbian or id gets detected
> once you plug it into a desktop Linux machine.
> Once you do that type:
>
> dmesg
>
> And it will list the kernel modules related to your dongle.
> You can use those buzzwords to google for what does
> enabling the dongle actually translates to in terms of kernel config.
>
> After that (depending what linux you're using) figure out how to
> run menuconfig. It might be something like:
>
> bitbake your-kernel-package-name -c menuconfig
>
> and try checking out the boxes that you found out
> might be relevant to your wifi dongle.
> Save it, build the image, and see if it got you somewhere.
>
>
>
>
>
>
>
> On Tue, Nov 21, 2017 at 5:32 PM, Jerry Lian  wrote:
> > I am confused on adding support for "usb WIFI dongle":
> > * My boards do NOT have WIFI capability, so I will add a "usb WIFI
> dongle".
> >   (I have two boards: Raspberri-PI-2, SIMATIC IOT-2020)
> > * Suppose we start from "core-image-sato"
> > * What should I do to add support for "usb WIFI dongle"
> > * After we build/boot the image, how can we verify and bring the WIFI up?
> >
> > Thanks!
> > Jerry
> >
> > --
> > ___
> > 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] How to add support for "usb WIFI dongle"?

[Jerry Lian]

How can we tell whether "ipw2x00" is driver or firmware?
* I check wiki:
https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers
* It seems that "ipw2x00" IS a driver, right?

* (And logically, we should not be required to select firmware, right?)
* (I mean: logically, if we select the driver, yocoto should select
corresponding firmware automatically for us, right?)

Thanks!






On Tue, Nov 28, 2017 at 1:18 PM, Alan Martinovic 
wrote:

> I can't confirm, but it just might be that "ipw2x00" is actually a
> firmware.
> (Haven't seen a firware specified explicetly in the menu config before).
>
> Ref: https://wiki.debian.org/brcm80211
>
> I recently had a question that might share some light on the firmware
> - driver relation:
>  (given that it really is firmware you check in the menuconfig)
>
> https://electronics.stackexchange.com/questions/
> 342118/design-decision-for-dynamic-firmware-loading
>
>
> On Tue, Nov 28, 2017 at 4:00 PM, Jerry Lian  wrote:
> > Thanks Alan, I follow your instruction and it works eventually!
> >
> > But I got another question:
> >
> > I am using official Raspberry-PI WIFI dongle (BCM43143)
> > I configure kernel so that driver "brcm80211" is enabled, however, WIFI
> is
> > not working.
> > Then I add driver "ipw2x00", then WIFI works.
> > So my question, why do we need both "ipw2x00" and "brcm80211" for
> official
> > Raspberry-PI WIFI dongle?
> > (Sometimes the WIFI dongle works if I add drivers: "brcm80211, iwlwifi,
> > rt2x00", without "ipw2x00", so I am really confused!)
> >
> > Thanks!
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Nov 21, 2017 at 12:04 PM, Alan Martinovic
> >  wrote:
> >>
> >> Some hints on where to start at:
> >>
> >> > What should I do to add support for "usb WIFI dongle"
> >>
> >> Am guessing the dongle works with Raspbian or id gets detected
> >> once you plug it into a desktop Linux machine.
> >> Once you do that type:
> >>
> >> dmesg
> >>
> >> And it will list the kernel modules related to your dongle.
> >> You can use those buzzwords to google for what does
> >> enabling the dongle actually translates to in terms of kernel config.
> >>
> >> After that (depending what linux you're using) figure out how to
> >> run menuconfig. It might be something like:
> >>
> >> bitbake your-kernel-package-name -c menuconfig
> >>
> >> and try checking out the boxes that you found out
> >> might be relevant to your wifi dongle.
> >> Save it, build the image, and see if it got you somewhere.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Tue, Nov 21, 2017 at 5:32 PM, Jerry Lian 
> wrote:
> >> > I am confused on adding support for "usb WIFI dongle":
> >> > * My boards do NOT have WIFI capability, so I will add a "usb WIFI
> >> > dongle".
> >> >   (I have two boards: Raspberri-PI-2, SIMATIC IOT-2020)
> >> > * Suppose we start from "core-image-sato"
> >> > * What should I do to add support for "usb WIFI dongle"
> >> > * After we build/boot the image, how can we verify and bring the WIFI
> >> > up?
> >> >
> >> > Thanks!
> >> > Jerry
> >> >
> >> > --
> >> > ___
> >> > 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] Concept clarification: can we deploy Yocto SDK to target?

[Jerry Lian]

I am confused about the concept of Yocto SDK:
* when we use "bitbake -c populate_sdk some_image", we obtain sysroots for
both target and host.
* But why do we need sysroot for host?

* I know we can build application under target-sysroot (surely source the
environment), with fast speed.
* But can we deploy target-sysroot to hardware-target?
(Yes, I do want to compile/build application inside hardware-target, even
though it is slow)

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

Re: [yocto] Concept clarification: can we deploy Yocto SDK to target?

[Jerry Lian]

Thanks Paul for your expert explanation, though I may not fully understand
yet.
Here is my scenario when raising my question:
* After deploying yocto image to hardware-target, I try build an
application (Autotools-based)
* The build stopped and asked for linux kernel source.

* So my image already contains compilers and linkers?
* So am I missing libraries, or just linux-headers?
* what is difference between libraries and headers?

Thanks!








On Wed, Nov 29, 2017 at 6:03 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> Hi Jerry,
>
> On Thursday, 30 November 2017 10:35:32 AM NZDT Jerry Lian wrote:
> > I am confused about the concept of Yocto SDK:
> > * when we use "bitbake -c populate_sdk some_image", we obtain sysroots
> for
> > both target and host.
> > * But why do we need sysroot for host?
>
> The host sysroot actually contains the main part of the SDK - the cross-
> compiler and other tools that need to run on the host. The target part
> usually
> doesn't include any executable binaries, only libraries and debugging
> symbols.
>
> > * I know we can build application under target-sysroot (surely source the
> > environment), with fast speed.
> > * But can we deploy target-sysroot to hardware-target?
> > (Yes, I do want to compile/build application inside hardware-target, even
> > though it is slow)
>
> I would suggest an alternative - install the compiler and tools into your
> image. You could do this when building the image, or alternatively if you
> enable package management in the image you could install them after the
> fact.
> At the image level there's a "tools-sdk" IMAGE_FEATURES item that will
> install
> the appropriate packages; alternatively you can install
> packagegroup-core-sdk
> which is effectively the same thing or for something a little more
> lightweight
> there is packagegroup-core-buildessential (roughly equivalent to debian's
> build-essential).
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

I am new to embedded linux, and some concepts confuse me:
* I have downloaded an Autotools-based application to run on my board.
* If I boot the board with original image/original SDK, I normally
build/install it with steps:
- ./bootstrap
- ./configure
- make
- make install
* Now if I boot the board with yocto image without SDK, how can I deploy
the application?
 (surely I do "bitbake -c populate_sdk some-image", and source the
environment!)
- ./bootstrap (Yocto SDK on host)
- ./configure (Yocto SDK on host)
- make (Yocto SDK on host)
- make install (???)

* How to do "make install"? (I want to install it on target, but how?)

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

Re: [yocto] Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

Thanks Eric for your explanation!
* (I know I can build the app within yocto build, but sometimes I prefer
the SDK method outside yocto build.)
* So just copy manually? I thought there are some tricks  that I don't know.

Now I have follow-up question:
* It seems that "make install" will copy different files to different
folders
* Can I do like these:?
--- make
--- copy (via scp)
--- make install
* Or it needs to be:
--- make
--- make install
--- copy (via scp) -then how do I know: what files to go which folder?
--- can you explain:
"... you may supply a custom install prefix directory to configure."
--- how?

Thanks!





On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz 
wrote:

> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>
> Hi Jerry,
>>
>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>
>> I am new to embedded linux, and some concepts confuse me:
>>> * I have downloaded an Autotools-based application to run on my board.
>>> * If I boot the board with original image/original SDK, I normally
>>> build/install it with steps:
>>> - ./bootstrap
>>> - ./configure
>>> - make
>>> - make install
>>>
>>
>> You may build your app within yocto build process so your application is
>> contained in your rootFS directly.
>>
>> * Now if I boot the board with yocto image without SDK, how can I deploy
>>> the application?
>>>  (surely I do "bitbake -c populate_sdk some-image", and source the
>>> environment!)
>>>
>>> - ./bootstrap (Yocto SDK on host)
>>> - ./configure (Yocto SDK on host)
>>> - make (Yocto SDK on host)
>>> - make install (???)
>>>
>>
>> If you build it w/ the SDK outside of the yocto build process just
>> install it to a local directory and copy all the stuff w/ e.g. scp onto
>> your boards rootFS.
>>
>
> ... you may supply a custom install prefix directory to configure.
>
>
>
>> * How to do "make install"? (I want to install it on target, but how?)
>>>
>>> Thanks!
>>>
>>
>> Cheers
>> Eric
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

Thanks Eric again.
* So you mean "copy -Rfa" can match folder-by-folder, so long as the
folder-tree are the same?
(if yes, that is super great!!!)
* I check that "make install" copy files to one folder, so that is easy for
deployment!

Another question:
* My application actually has another step: "make modules_install" (surely
step "make modules" also)
* But I got error (see below):
   what could be wrong with "SSL error"? isn't build already
passed successfully?



jerry@yct:~/ecat-33b922$ make modules_install
make -C "/usr/src/linux-headers-4.10.0-28-generic"
M="/home/jerry/ecat-33b922" \
INSTALL_MOD_DIR="ethercat" modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
mkdir: cannot create directory ‘/lib/modules/4.10.0-28-generic/ethercat’:
Permission denied
Makefile:1536: recipe for target '_emodinst_' failed
make[1]: *** [_emodinst_] Error 1
make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
Makefile:934: recipe for target 'modules_install' failed
make: *** [modules_install] Error 2

jerry@yct:~/ecat-33b922$ sudo make modules_install
make -C "/usr/src/linux-headers-4.10.0-28-generic"
M="/home/jerry/ecat-33b922" \
INSTALL_MOD_DIR="ethercat" modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
  INSTALL /home/jerry/ecat-33b922/devices/ec_generic.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/jerry/ecat-33b922/examples/mini/ec_mini.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/jerry/ecat-33b922/master/ec_master.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  DEPMOD  4.10.0-28-generic
make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'

jerry@yct:~/ecat-33b922$
--------
---

Thanks!






On Fri, Dec 1, 2017 at 10:37 AM, Eric Schwarz 
wrote:

> Am 01.12.2017 16:15, schrieb Jerry Lian:
>
> Thanks Eric for your explanation!
>> * (I know I can build the app within yocto build, but sometimes I prefer
>> the SDK method outside yocto build.)
>>
>> * So just copy manually? I thought there are some tricks  that I don't
>> know.
>>
>>
> Acutally that's how we are doing it ...
>
> Now I have follow-up question:
>> * It seems that "make install" will copy different files to different
>> folders
>> * Can I do like these:?
>> --- make
>> --- copy (via scp)
>> --- make install
>> * Or it needs to be:
>> --- make
>> --- make install
>>
>
> Install the cross-compiled stuff on your local disc e.g. into a "transfer"
> directory. Then copy it to the target.
> On the target 'cp -Rfa /* /' should do it if the basic
> directory structure fits to your rootFS.
>
> --- copy (via scp) -then how do I know: what files to go which folder?
>> --- can you explain:
>> "... you may supply a custom install prefix directory to configure." ---
>> how?
>>
>>
> There is IMHO no standardized variable available. Just look into the
> configure script how the variable is named and if it is actually available
> at all.
>
>
> Thanks!
>>
>> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz 
>> wrote:
>> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>>
>> Hi Jerry,
>>
>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>
>> I am new to embedded linux, and some concepts confuse me:
>> * I have downloaded an Autotools-based application to run on my board.
>> * If I boot the board with original image/original SDK, I normally
>> build/install it with steps:
>> - ./bootstrap
>> - ./configure
>> - make
>> - make install
>> You may build your app within yocto build process so your application is
>> contained in your rootFS directly.
>>
>> * Now if I boot the board with yocto image without SDK, how c

Re: [yocto] Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

OK, that is what confused me: I DID try "make modules_install" on host!

So according to what you said, the right procedure is:
* do  "make install"on host, then copy to target:
* don't do "make modules_install" on host, but make a package first, then
copy to target and install.
* right?

* then how to make a package?
* how do I know which are "relevant other files"?

sorry for my newbie questions, thanks!





On Fri, Dec 1, 2017 at 11:30 AM, Eric Schwarz 
wrote:

> Am 01.12.2017 16:58, schrieb Jerry Lian:
>
> Thanks Eric again.
>> * So you mean "copy -Rfa" can match folder-by-folder, so long as the
>> folder-tree are the same?
>> (if yes, that is super great!!!)
>>
>
> Yes.
>
> * I check that "make install" copy files to one folder, so that is easy
>> for deployment!
>>
>> Another question:
>> * My application actually has another step: "make modules_install"
>> (surely step "make modules" also)
>> * But I got error (see below):
>> what could be wrong with "SSL error"? isn't build already passed
>> successfully?
>>
>
> You are doing the 'make modules_install' on the target or where else? You
> need to build the modules within the Yocto environment and may create a
> package e.g. *.deb you may install later on the target or copy the modules
> by hand including relevant other files needed. Obviously the system tries
> to recompile the kernel modules. That's what 'make modules_install' does.
>
>
>
>> 
>> 
>> jerry@yct:~/ecat-33b922$ make modules_install
>> make -C "/usr/src/linux-headers-4.10.0-28-generic"
>> M="/home/jerry/ecat-33b922" \
>> INSTALL_MOD_DIR="ethercat" modules_install
>> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
>> mkdir: cannot create directory '/lib/modules/4.10.0-28-generic/ethercat':
>> Permission denied
>> Makefile:1536: recipe for target '_emodinst_' failed
>> make[1]: *** [_emodinst_] Error 1
>> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
>> Makefile:934: recipe for target 'modules_install' failed
>> make: *** [modules_install] Error 2
>>
>> jerry@yct:~/ecat-33b922$ sudo make modules_install
>> make -C "/usr/src/linux-headers-4.10.0-28-generic"
>> M="/home/jerry/ecat-33b922" \
>> INSTALL_MOD_DIR="ethercat" modules_install
>> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
>> INSTALL /home/jerry/ecat-33b922/devices/ec_generic.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> INSTALL /home/jerry/ecat-33b922/examples/mini/ec_mini.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> INSTALL /home/jerry/ecat-33b922/master/ec_master.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> DEPMOD  4.10.0-28-generic
>> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
>>
>> jerry@yct:~/ecat-33b922$
>> 
>> ---
>>
>> Thanks!
>>
>> On Fri, Dec 1, 2017 at 10:37 AM, Eric Schwarz 
>> wrote:
>> Am 01.12.2017 16:15, schrieb Jerry Lian:
>>
>> Thanks Eric for your explanation!
>> * (I know I can build the app within yocto build, but sometimes I prefer
>> the SDK method outside yocto build.)
>>
>> * So just copy manually? I thought there are some tricks  that I don't
>> know.
>>
>> Acutally that's how we are doing it ...
>>
>> Now I have follow-up question:
>> * It seems that "make install" will copy different files to different
>> folders
>> * Can I do like these:?
>> --- make
>>

Re: [yocto] Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

Thanks Philip!
I will try "sshfs" later. Right now using copy (via scp) works fine for
both "make install" and "make modules_install", and my application runs.





On Sun, Dec 3, 2017 at 9:17 AM, Philip Balister  wrote:

> On 12/01/2017 10:15 AM, Jerry Lian wrote:
> > Thanks Eric for your explanation!
> > * (I know I can build the app within yocto build, but sometimes I prefer
> > the SDK method outside yocto build.)
> > * So just copy manually? I thought there are some tricks  that I don't
> know.
> >
> > Now I have follow-up question:
> > * It seems that "make install" will copy different files to different
> > folders
> > * Can I do like these:?
> > --- make
> > --- copy (via scp)
> > --- make install
> > * Or it needs to be:
> > --- make
> > --- make install
> > --- copy (via scp) -then how do I know: what files to go which
> folder?
> > --- can you explain:
> > "... you may supply a custom install prefix directory to configure."
> > --- how?
>
> I've used sshfs to mount the target on the machine with the sdk and then
> something like:
>
> make install DESTDIR=~/mydevice
>
> From:
>
> https://wiki.gnuradio.org/index.php/Cross_compile_an_
> OOT_and_install_on_target
>
> Philip
>
> >
> > Thanks!
> >
> >
> >
> >
> >
> > On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz 
> > wrote:
> >
> >> Am 01.12.2017 15:16, schrieb Eric Schwarz:
> >>
> >> Hi Jerry,
> >>>
> >>> Am 01.12.2017 15:07, schrieb Jerry Lian:
> >>>
> >>> I am new to embedded linux, and some concepts confuse me:
> >>>> * I have downloaded an Autotools-based application to run on my board.
> >>>> * If I boot the board with original image/original SDK, I normally
> >>>> build/install it with steps:
> >>>> - ./bootstrap
> >>>> - ./configure
> >>>> - make
> >>>> - make install
> >>>>
> >>>
> >>> You may build your app within yocto build process so your application
> is
> >>> contained in your rootFS directly.
> >>>
> >>> * Now if I boot the board with yocto image without SDK, how can I
> deploy
> >>>> the application?
> >>>>  (surely I do "bitbake -c populate_sdk some-image", and source the
> >>>> environment!)
> >>>>
> >>>> - ./bootstrap (Yocto SDK on host)
> >>>> - ./configure (Yocto SDK on host)
> >>>> - make (Yocto SDK on host)
> >>>> - make install (???)
> >>>>
> >>>
> >>> If you build it w/ the SDK outside of the yocto build process just
> >>> install it to a local directory and copy all the stuff w/ e.g. scp onto
> >>> your boards rootFS.
> >>>
> >>
> >> ... you may supply a custom install prefix directory to configure.
> >>
> >>
> >>
> >>> * How to do "make install"? (I want to install it on target, but how?)
> >>>>
> >>>> Thanks!
> >>>>
> >>>
> >>> Cheers
> >>> Eric
> >>>
> >>
> >
> >
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Build error: "u-boot-imx_2017.03.bb:do_compile" failed ( freescale I.MX 6 on Ubuntu 16.04) ?

[Jerry Lian]

I got an error when trying to build for freescale I.MX6 on Ubuntu
16.04.(see below)
(I just follow the guide from http://freescale.github.io)

Anybody got hints?

Thanks!
Jerry

===

| tools/libfdt_wrap.c:147:21: fatal error: Python.h: No such file or
directory
| compilation terminated.
| error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
|
/home/jerry/fsl-release-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2017.03-r0/git/tools/Makefile:123:
recipe for target 'tools/_libfdt.so' failed
| make[2]: *** [tools/_libfdt.so] Error 1
|
/home/jerry/fsl-release-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2017.03-r0/git/Makefile:1229:
recipe for target 'tools' failed
| make[1]: *** [tools] Error 2
| make[1]: Leaving directory
'/home/jerry/fsl-release-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2017.03-r0/build/mx6qsabresd_config'
| Makefile:150: recipe for target 'sub-make' failed
| make: *** [sub-make] Error 2
| make: Leaving directory
'/home/jerry/fsl-release-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2017.03-r0/git'
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/jerry/fsl-release-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2017.03-r0/temp/log.do_compile.9339)
ERROR: Task
(/home/jerry/fsl-release-bsp/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2017.03.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 4851 tasks of which 3009 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/jerry/fsl-release-bsp/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2017.03.bb:
do_compile
..

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

[yocto] Yocto SDK: how to rebuild *.dtb? (fatal error: dt-bindings/gpio/gpio.h: No such file or directory)

[Jerry Lian]

I installed yocto SDK for my beaglebone black.
But when I try to rebuild am335x-boneblack.dtb, I got error:

"arch/arm/boot/dts/am33xx.dtsi:11:10: fatal error:
dt-bindings/gpio/gpio.h: No such file or directory"

Any hint? Thanks!

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

[yocto] Editor (viewer) for device tree *.dts file? (I mean syntax highlighting)

[Jerry Lian]

Sorry that this question is not related to Yocto, but just wondering if
anybody knows:
* are there editors/viewers (with syntax highlighting) for device tree
*.dts file?

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

Re: [yocto] Editor (viewer) for device tree *.dts file? (I mean syntax highlighting)

[Jerry Lian]

Thanks Maciej, vim works well as expected!





On Wed, Jan 17, 2018 at 10:46 AM, Maciej Pijanowski <
maciej.pijanow...@3mdeb.com> wrote:

> I'm just using vim for everything. It highlights dts syntax.
>
> On 17.01.2018 16:37, Jerry Lian wrote:
>
> Sorry that this question is not related to Yocto, but just wondering if
> anybody knows:
> * are there editors/viewers (with syntax highlighting) for device tree
> *.dts file?
>
> Thanks,
> Jerry
>
>
>
> --
> Maciej Pijanowski
> Embedded Systems Engineerhttp://3mdeb.com | @3mdeb_com
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto for BeagleboneBlack: how to enable user-LEDs?

[Jerry Lian]

I build yocto image for BBB(Beaglebone Black) with default settings, then:
bitbake core-image-sato
* After I boot the image, all LEDs are off
* And I check folder "/sys/class/", there is no sub-folder "leds"

So how can I enable LEDs when building yocto image?
should I change/add image any distribution/feature, or package groups?

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

[yocto] ksize.py not working?

[Jerry Lian]

I want to check/analyze kernel image size, and I found:
* ksum.py works as expected!
* however, ksize.py produces results of "all zeros".

Anybody know the problem and how to fix it?

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