[yocto] Yocto General purpose evaluation

Timothy Froehlich tfroehlich at archsys.io
Mon Feb 18 11:37:22 PST 2019


Sounds like you should be using an embedded Linux, since only including the
minimum required software will help keep your image small and power usage
down. Removing audio, video and usb, including from your kernel config,
should drastically reduce your size.

You should consider the value of a read only FS, since I'd assume you'll
have random power loss due to solar being your primary power source.
Yocto/Buildroot will be much better with that.

For Yocto vs Buildroot, here's a good place to start for your research:
https://lwn.net/Articles/682540/. In my experience, Buildroot is easy,
simple, and great as long as you're building one thing. Yocto is much more
powerful and if you need more than what Buildroot can provide then you're
better off investing your time learning Yocto instead of learning how to
modify Buildroot, IMO.

On Mon, Feb 18, 2019 at 10:33 AM <andrew.rudd at aktyon.com> wrote:

> Hello,
>
>
>
> I’m looking to evaluate the general purpose/utility of a custom build
> Yocto embedded OS. I’m trying to get my head around the benefits of using
> such an OS. I’m sure it’s on case by case basis so let me provide my
> background and requirements.
>
>
>
> Background/requirements
>
> Currently using Debian OS on my prototype build based on a Beaglebone
> green wireless.
>
> Custom software is constructed in java.
>
> System utilizes 9 axis accelerometer, vibration sensor, Bluetooth, WiFi,
> LTE-M, GNSS, power management (through BB I2c and GPIO channels)
>
> It runs on a battery and solar.
>
> Power usage is important. Standby is used and still needs to listen for
> vibration sensor, Bluetooth and LTE-m cellular events.
>
> Only constrained by power usage and data usage. Processor or memory usage
> are unconstrained except for in relation to power usage.
>
> Minimizing data usage if an OS update is needed would be an advantage.
>
> No audio , video, USB or GUI is used.
>
>
>
>
>
> So would there be a significant benefit seen by using a custom Yocto build
> or would a GUIless version of Debian be just as effective? Also considering
> Buildroot if that would be just as effective and simpler to execute. If
> anyone has any other thoughts or concerns I would love to discuss. Thank
> you for your time.
>
>
>
> Thank you,
>
> Andrew Rudd
>
> President, Aktyon
>
> 352-256-8086
>
> Andrew.Rudd at Aktyon.com
>
> [image: AktyonLogoAndFontSignature]
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
Tim Froehlich
Embedded Linux Engineer
tfroehlich at archsys.io
215-218-8955
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190218/8ac976e9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8028 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190218/8ac976e9/attachment-0001.png>


More information about the yocto mailing list