I've run "bitbake rpi-hwup-image" using the daisy branch:
meta-yocto-bsp= "daisy:1e668ccf1a05c5d730de9747bc1c2b0446bda556"
meta-raspberrypi.git = "daisy:946b69299737cc2f1378c864f1b9075280db1b53"
However, whenever I boot the created sdimage it will lock up during
boot. Typically I will see so
Hello Liviu,
Thank you very much for your reply. I got a very useful information from your
reply.
At the beginning , I want to add the cross compiler to eclipse project and
not use the default installer directory, but it appears the above problem.
In eclipse project, the setting as these:
On 12/17/2014 04:00 PM, John Unland wrote:
> Hello everyone,
>
> I am developing a linux distro for small businesses and I am wanting to
> have a easy to use tool to develop that OS. However with the main-line
> distros there is a lot of hoops to jump over to get to that point
> (re-branding, remo
Hello everyone,
I am developing a linux distro for small businesses and I am wanting to
have a easy to use tool to develop that OS. However with the main-line
distros there is a lot of hoops to jump over to get to that point
(re-branding, remove certain software, etc). So I was wondering is it
pos
On Mon, Dec 08, 2014 at 10:17:37AM -0800, Matt Schuckmann wrote:
> I'm looking for some tips on debugging package install problems.
> Recently I've had a problem where edits to a pkg_postinst function in one of
> my recipes was not getting run when rebuilding my image. The only way I could
> get
On 14-12-17 01:02 PM, Cody P Schafer wrote:
It looks like http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/
is still sitting at 3.17.6, are their plans to merge the 3.18 changes?
Or does linux-yocto-dev wait on stable kernel releases?
Or is this blocked on something else I'm unaware of?
It looks like http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/
is still sitting at 3.17.6, are their plans to merge the 3.18 changes?
Or does linux-yocto-dev wait on stable kernel releases?
Or is this blocked on something else I'm unaware of?
--
Cody
--
... or easier, you can directly use the
poky_dir/meta/recipes-core/init-ifupdown/init-ifupdown-1.0/interfaces to
set up interfaces. An eg. would be:
auto eth0
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
I'd install a custom /etc/network/interfaces file via a bbappend or
similar method. There is numerous examples in google of how to set up a
static Ip via the interfaces file.
Philip
On 12/16/2014 05:08 AM, Constantin, Costin C wrote:
> Hello Sachin
>
> The easiest way to do this is by modifying
The size of the resulting image of poky-tiny + systemd is a lot smaller than
poky itself, even with the systemd kernel/glibc requirement set in. The poky
distro also pulls a lot more package into the mix that I do not need for my
tasks. I could go and disable those, but that is actually what p
Hello Neil,
Your problem is that the toolchain is installed with the location of the
sysroot hardcoded as the default installation path for the tool-chain.
You can see this location with:
$ arm-poky-linux-gnueabi-gcc --print-sysroot // or whatever
cross-compiler you built
However, after you
Hello ,all
I build the toolchain via bitbake core-image-minimal –c populate_sdk. Then I
install the toolchain.
If I install the toolchain in default directory(default: /opt/poky/1.7.1),
everything is ok.
But, if I not install in the default directory, it will appears the problem
that can’t
12 matches
Mail list logo
