Re: [yocto] Suitable machine for yocto

[Usman Haider]

On Mon, Sep 11, 2017 at 1:21 PM, Burton, Ross  wrote:

> On 10 September 2017 at 12:00, Chris Tapp  wrote:
>
>> I have a similar spec, except I use an SSD for the build area and only
>> 16GB RAM (I don’t see more than about 12GB used during a build) - a build
>> from scratch (excluding download time) takes just under an hour.
>>
>
> The thing to remember with SSDs is that builds can write *a lot* of data
> and this can destroy SSDs faster than you'd like.
>
> Personally I find lots of RAM more cost effective.  If you've got a
> moderate amount then a slow commit time in fstab lets the kernel batch
> writes wisely.  If you've got plenty of RAM (my machine has 64GB) then a
> good sized tmpfs (32GB here) mounted at TMPDIR (the local.conf setting, not
> /tmp) in with rm_work means you literally have no I/O latency.  To persist
> files either copy them out or for example set DEPLOY_DIR to a real disk.
>
> Ross
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

Thanks,

I'll consider this too. A lot of techincal stuff to learn here on this
mailing list :)

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

Re: [yocto] Suitable machine for yocto

[Usman Haider]

On Mon, Sep 11, 2017 at 11:51 AM, Alex Lennon <ajlen...@dynamicdevices.co.uk
> wrote:

>
>
> On 11/09/2017 00:56, Mark Hatle wrote:
>
>> On 9/10/17 2:31 PM, Alex Lennon wrote:
>>
>>>
>>> On 10/09/2017 19:17, Mark Hatle wrote:
>>>
>>>> On 9/10/17 11:14 AM, Alex Lennon wrote:
>>>>
>>>>> On 10/09/2017 17:06, Mark Hatle wrote:
>>>>>
>>>>>> On 9/10/17 2:00 AM, Usman Haider wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Can someone please recommend some good machine for yocto environment
>>>>>>> and
>>>>>>> building sdks. I am interested in RAM, hard disk space, processor.
>>>>>>>
>>>>>> You want fast I/O, as much RAM and as many (fast) cores as you can
>>>>>> afford.  I
>>>>>> don't think there is a single answer as what is 'best'.  It also
>>>>>> depends on
>>>>>> which Yocto Project versions, and which layers you are using as to
>>>>>> which
>>>>>> combination is best.
>>>>>>
>>>>>> I run builds on my laptop, 4-core/8-thread & SSD and 16 GB of ram
>>>>>> from a few
>>>>>> years ago.  It's fast, but I wouldn't want to do all of my
>>>>>> development on it.
>>>>>>
>>>>>> I've had 8-core/16-thread (32GB ram/standard disk), 16-core/32-thread
>>>>>> (72GB
>>>>>> ram/SAS-3 RAID), 24-core/48-thread (64GB ram/SATA - software RAID),
>>>>>> 72-core/144
>>>>>> thread (256 GB ram/hardware raid/SAS-3), and recently upgraded to
>>>>>> 96-core/192-thread (256 GB ram/hardware raid/SAS-3).
>>>>>>
>>>>>> I would not go below quad-core (8-thread) myself.  You can get a quad
>>>>>> core, good
>>>>>> quality machine for $1000 or less these day.  If you move up to the
>>>>>> larger
>>>>>> machines, you can even be able to get to a 24-core for less then
>>>>>> $5000.  By the
>>>>>> time you get to 96-core and all of the googles you are likely talking
>>>>>> $5 or
>>>>>> more.
>>>>>>
>>>>>> By clock raid, the 24-core machine is the fastest..  While the
>>>>>> 96-core monster
>>>>>> can do the builds the quickest.  But when you figure out
>>>>>> cost/performance/etc..
>>>>>> the 24-core is probably the best performance per dollar, and with
>>>>>> adequate RAM
>>>>>> (I'd say at least 64GB if not 128GB), and fast I/O you'll probably
>>>>>> get the
>>>>>> lowest price for the best performance in that category.
>>>>>>
>>>>>> If you need sheer speed and price is no option, then the (4 CPU w/ 24
>>>>>> core each)
>>>>>> 96-core monster (or even better) is what you want to go with.  256GB
>>>>>> ram would
>>>>>> be a minimum with that configuration (I'm not sure if more is
>>>>>> actually helpful,
>>>>>> I rarely end up in swap -- but I go get into situations where more
>>>>>> then 50% of
>>>>>> ram is used.)  With that many cores, disk I/O starts to become
>>>>>> obvious.  So
>>>>>> faster the better... SSDs would be the fastest, but of course the
>>>>>> most expensive.
>>>>>>
>>>>>> If your employer is paying for the machine, you may be able to get a
>>>>>> better then
>>>>>> normal machine by explaining how much time a faster machine will save
>>>>>> and how
>>>>>> comparing to your salary a machine is inexpensive.  (If you are a
>>>>>> contractor or
>>>>>> student, that changes of course.)  :)
>>>>>>
>>>>>> So my point is really, figure out how much money you have to spend.
>>>>>> My rule of
>>>>>> thumb is roughly:
>>>>>>
>>>>>> 1) Buy as many cores as you can.  Try to get a CPU that has
>>>>>> Hyperthreading or
>>>>>> equivalent to double the effective core count.  Fastest processing
>>>>>> speed helps
>>>>>> in repetitive ca

[yocto] Suitable machine for yocto

[Usman Haider]

Hi,

Can someone please recommend some good machine for yocto environment and
building sdks. I am interested in RAM, hard disk space, processor.

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

Re: [yocto] meta-raspberrypi issue

[Usman Haider]

Thanks,

I'll definitely move to morty. I was following I guide that uses daisy.

--
Usman

On Wed, Feb 8, 2017 at 5:09 PM, Gary Thomas <g...@mlbassoc.com> wrote:

> On 2017-02-01 18:24, Khem Raj wrote:
>
>>
>>
>> On 2/1/17 8:08 AM, Usman Haider wrote:
>>
>>> Hi,
>>>
>>> I am new to yocto and just started working on it. I am having issue
>>> with meta-raspberrypi. I did inside poky
>>>
>>> $ git checkout -b work_branch -t origin/daisy
>>>
>>> $ git clone git://git.yoctoproject.org/meta-raspberrypi
>>> <http://git.yoctoproject.org/meta-raspberrypi>
>>>
>>>
>> you need to checkout daisy branch of meta-raspberrypi as well.
>>
>
> That said, daisy is REALLY OLD.  You'd probably be much better off with
> something recent, e.g. morty.
>
>
>
>> $ source oe-init-build-env rpi-build
>>>
>>> updated the local.conf and bblayer.conf files inside rpi-build
>>>
>>> In local.conf
>>>
>>> BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
>>> PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
>>> MACHINE ?= "raspberrypi"
>>>
>>> In bblayer.conf
>>> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
>>> # changes incompatibly
>>> LCONF_VERSION = "6"
>>>
>>> BBPATH = "${TOPDIR}"
>>> BBFILES ?= ""
>>>
>>> BBLAYERS ?= " \
>>>   /home/vm/poky/meta \
>>>   /home/vm/poky/meta-yocto \
>>>   /home/vm/poky/meta-yocto-bsp \
>>>   /home/vm/poky/meta-raspberrypi \
>>>   "
>>> BBLAYERS_NON_REMOVABLE ?= " \
>>>   /home/vm/poky/meta \
>>>   /home/vm/poky/meta-yocto \
>>>   "
>>>
>>> When I run bitbake rpi-basic-image, I get following
>>>
>>>
>>> *
>>>
>>> vm@sdr-vm:~/poky/rpi-build$ bitbake rpi-basic-image
>>> WARNING: Host distribution "Ubuntu-16.04" has not been validated with
>>> this version of the build system; you may possibly experience unexpected
>>> failures. It is recommended that you use a tested distribution.
>>> Parsing recipes: 100% |#| Time:
>>> 00:02:37
>>> Parsing of 882 .bb files complete (0 cached, 882 parsed). 1241 targets,
>>> 63 skipped, 0 masked, 0 errors.
>>> ERROR: No recipes available for:
>>>
>>> /home/vm/poky/meta-raspberrypi/recipes-multimedia/gstreamer/
>>> gstreamer1.0-omx_1.10%.bbappend
>>>
>>> /home/vm/poky/meta-raspberrypi/recipes-multimedia/gstreamer/
>>> gstreamer1.0-omx_1.2.0.bbappend
>>> ERROR: Command execution failed: Exited with 1
>>>
>>> *
>>>
>>> What could be the issue?
>>>
>>> --
>>> Usman
>>>
>>>
>>>
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
>
> --
> ___
> 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] meta-raspberrypi issue

[Usman Haider]

Hi,

I am new to yocto and just started working on it. I am having issue
with meta-raspberrypi. I did inside poky

$ git checkout -b work_branch -t origin/daisy

$ git clone git://git.yoctoproject.org/meta-raspberrypi

$ source oe-init-build-env rpi-build

updated the local.conf and bblayer.conf files inside rpi-build

In local.conf

BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
MACHINE ?= "raspberrypi"

In bblayer.conf
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/vm/poky/meta \
  /home/vm/poky/meta-yocto \
  /home/vm/poky/meta-yocto-bsp \
  /home/vm/poky/meta-raspberrypi \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /home/vm/poky/meta \
  /home/vm/poky/meta-yocto \
  "

When I run bitbake rpi-basic-image, I get following


*

vm@sdr-vm:~/poky/rpi-build$ bitbake rpi-basic-image
WARNING: Host distribution "Ubuntu-16.04" has not been validated with this
version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution.
Parsing recipes: 100% |#| Time:
00:02:37
Parsing of 882 .bb files complete (0 cached, 882 parsed). 1241 targets, 63
skipped, 0 masked, 0 errors.
ERROR: No recipes available for:

/home/vm/poky/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.10%.bbappend

/home/vm/poky/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bbappend
ERROR: Command execution failed: Exited with 1

*

What could be the issue?

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