Bumped against similar issues with ssh servers (also dropbear) and the problem turned out to be a "lack of entropy". It takes the ssh server up to several minutes to initialize on an embedded system,

Guess you'll have to provide more than just "It doesn't work" if you want any serious assistance. The source code would help. Also telling us whether the drivers actually probe if you load them manual

Likely there's a problem with the underscore. Recipes (and packages) with an underscore don't work properly because it's used as a version separator. Rename "my_module" to "my-module". Having said tha

Hi Nicolas, I guess part of your problem is that DISTRO does not end up in any package grouping, unlike MACHINE and ARCH and so. So if OE/Yocto does The Right Thing, this means that it will have to re

Quick answer: Don't build multiple distros in one build directory. You might get away with setting TMPDIR = "tmp-${DISTRO}" to give each its own. But I'd rather advice to set up two separate builds an

I'd suggest adding some "bogus" things to your machine-extra.conf, because I don't think the file will actually be used (or even parsed) anywhere. You can override SERIAL_CONSOLES in your DISTRO confi

Ah, just writing to the list appeared to have helped. For the dependency to work, you need both a "Requires" and an "After" directive, i.e. [unit] ... Requires=sys-devices-platform-gpu-graphics-fb0.de

psplash doesn't work on my system because systemd attempts to start it at 1.6 seconds into boot, while the fb device is created 1.9 seconds after booting. This results in: [FAILED] Failed to start Sta

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijmans@...

#yocto

I tend to use a reasonably standard image, usually the one that will evolve into the product, and once the network (usb, ethernet or wifi) is up, use "opkg install" to grab whatever else I need from m

You can use both by changing the directory for downloads and sstate-cache. Put these in your local.conf: SSTATE_DIR = "/opt/sstate-cache" DL_DIR = "/opt/downloads" (You change "/opt" to some other loc

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijmans@...

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijmans@...

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijmans@...

#yocto

The simplest solution is to use autotools or Cmake for your project. That will automatically "do the right thing" to get the library properly installed and registered. Even if your project is just one

We're sharing the sstate-cache on plain Ubuntu LTS machines, all installed from wherever, and no issues with low hitrates. Even if the build server was running something like ubuntu 14 and "my" machin

Yes, a mounted ext4 partition can be resized. Some tools will try to keep you from doing that though, had to patch parted to stop whining about mounted partitions in "scripted" mode that to make it wo

My guess is that your busybox isn't configured to produce mdev. Run "bitbake -c menuconfig busybox" and enable it (and save the config fragment for later)

Lists.Yoctoproject.Org wrote: For anything more advanced than one or two C files, avoid handcrafting makefiles and use autotools or cmake. A helloworld makefile that takes "helloworld.c" or "helloworl

I tried compiling octave on an ARM board with 1GB of RAM (because octave is virtually impossible to cross-compile). There was one C++ in there that triggered a huge memory load of about 1GB, thus fail