Can't thank you enough for your help! I was really despaired of this.
Not sure I did it right - to remove the rng-tools I added:
PACKAGE_EXCLUDE = "rng-tools"
That doesn't look like the best way to remove it, but works.
Best regards
Arno
--
___
Build a rootfs with Yocto 2.5 and 3.0 (Zeus). Got both working, but booting in
3.0 is terrible slow.
The reasons seems to be that random numbers are not generated for ssh. I found
that there is a new startup script:
/etc/init.d/rng-tools
that needs around 14s. But if I comment it out, it ssh
Switching from Yocto2.5 to 2.7 brings up new stuff. So the compiler
architecture changes from cortexa9hf to cortexa9t2hf.
Am I right this gives just the option to use thumb2, but without a dedicated
compiler option it still creates standard arm code?
Also my previous compiler option:
> Gesendet: Freitag, 12. April 2019 um 19:07 Uhr
> Von: "Mike Looijmans"
> An: "Arno Steffens"
> Cc: "meta xilinx"
> Betreff: Re: Aw: Re: [meta-xilinx] Kernel version, xilinx git repo, yocto
> kernel
>
> On 12-04-19 15:39, Arno Steffens wro
Sorry, attached file didn't work, I'll try this:
/dts-v1/;
/ {
#address-cells = <0x1>;
#size-cells = <0x1>;
compatible = "avnet,microzed", "xlnx,zynq-7000";
model = "Test Device";
chosen {
bootargs = "earlyprintk";
> Gesendet: Mittwoch, 10. April 2019 um 07:39 Uhr
> Von: "Mike Looijmans"
> An: "meta xilinx"
> Betreff: Re: [meta-xilinx] Kernel version, xilinx git repo, yocto kernel
>
> On 07-04-19 11:41, Arno Steffens wrote:
> > In fact, I think I have diffic
Uhr
> Von: "Mike Looijmans"
> An: "Arno Steffens"
> Cc: "meta xilinx"
> Betreff: Re: Aw: Re: [meta-xilinx] Kernel version, xilinx git repo, yocto
> kernel
>
> On 04-04-19 14:03, Arno Steffens wrote:
> > Thanks Mike for this clear (a
. Thats always magic
to me.
Kind regards, Arno
> Gesendet: Donnerstag, 04. April 2019 um 07:31 Uhr
> Von: "Mike Looijmans"
> An: "Arno Steffens" , "meta xilinx"
>
> Betreff: Re: [meta-xilinx] Kernel version, xilinx git repo, yocto kernel
>
> Simp
Hello, I am a bit confused to see that in GIT (linked in Yocto
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/ ->
git://git.yoctoproject.org/meta-xilinx ) there are no commits since August.
But in this mailing list I can see commits (especially regarding thud).
Is there another repo that
Hello,
After upgrade to Sumo I found some errors, that I can't understand.
As fas as I can see the microzed_zynq7 is still available?
ERROR: Nothing PROVIDES 'virtual/xilinx-platform-init' (but
/home/user/y/yocto25/poky/meta/recipes-bsp/u-boot/u-boot_2018.01.bb DEPENDS on
or otherwise requires
Hello,
I changed kernel from 4.9 to 4.14.
My previous /dev/spidev32766.0 is now listed as /dev/spidev0.0.
Honestly speaking, I have not been aware how the previous name "32766.0" is
coming from. But why this has been changed?
I would suspecz the devicetree, but that I haven't changed it at all.
There are many boards out there.
As a general question: Is there a kind of guide what and how to adapt to a new
board?
Is it better to creating a new own meta-layer or patching the meta-xilinx? And
if so - add a new board or modify an existing?
Regards
> Gesendet: Freitag, 09. Februar 2018 um
I want to issue an I2C-command before booting the kernel.
Does the u-boot for ZYNQ supports I2C? I didn't found it activated in any ZYNQ
board, so I am wondering why!?
Any hints how to activate?
My first experiments to enable it failed with a reboot:
Zynq> i2c probe
Valid chip addresses:Error,
I guess it has been this setting:
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
Not that I really understand that, but it seems to work now
> Gesendet: Dienstag, 18. Juli 2017 um 08:06 Uhr
> Von: "Arno Steffens" <s...@gmx.li>
> An: meta-xilinx@yoctoproject.org
> Betreff: R
isting SPI mode/phase settings?
>
> And you have a huge FPGA at your disposal if you have a Xilinx device of any
> kind. I'd suggest just solving this in a bit of FPGA logic instead of in
> userspace C code.
>
>
>
> On 09-05-17 14:54, Arno Steffens wrote:
> >
Hi,
using the Linux version 4.6.0-xilinx-v2016.3 kernel and have a problem.
My rootfs is on emmc. In general it works, but from time to time it ends up in
a crash:
It seem it tries to mount rootfs before the emmc subsystem is initialised.
Is there any trick to get this stable working?
error
> On 14 February 2017 at 23:22, Arno Steffens <s...@gmx.li> wrote:
> > If I increase the uboot environment (by patching zynq-common.h) it happens
> > that uboot stops working.
> > With a few lines changing/adding it seems to boot normal.
> > With more lines is sto
If I increase the uboot environment (by patching zynq-common.h) it happens that
uboot stops working.
With a few lines changing/adding it seems to boot normal.
With more lines is stops after "DRAM: ECC disabled 496 MiB"
Now I played with the patch and get once this (see below):
This looks a bit
.
These are all using:
/include/ "zynq-7000.dtsi" - but this is not in .../common
Is this intentionally?
And it seems the number of Bogomips is only half of previous values (even after
adding 2nd CPU)?
Regards
Arno
> Gesendet: Dienstag, 10. Januar 2017 um 08:31 Uhr
> Von: "Arno S
Keeping my previous system (yocto 2.1 uboot) I try to boot into recent yocto2.2
(xilinx 4.6) kernel.
It doesn't, last message is "Starting kernel ..."
I read that this has usually 2 reasons, mismatching bootcmd or MachineID.
I try to boot (working 4.4 kernel) with other machine id by setting in
Compared to previous versions of meta-xilinx in morty I miss in uboot-xlnx
2016-7
these config files
include/configs/zynq_microzed.h
include/configs/zynq_picozed.h
include/configs/zynq_zed.h
What happened with this files?
In previous versions I patched zynq_microzed.h as adaption for my own
I switched from an older yocto u-boot (2015.01) to recent one (2016.01). Now I
can't boot anymore:
Zynq> boot
QSPI: Kernel/Devicetree - NFS: rootfs
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total
16 MiB
device 0 offset 0x4b, size 0x1
SF: 65536 bytes @
22 matches
Mail list logo
