Re: [yocto] loading FPGA bitfile with u-boot spl on ZYBO

[Alan Levy]

This is really a question for the meta-xilinx list but I'll answer it here 
anyway. 

You need to add the following command (suitably edited) to uEnv.txt on the SD 
card:

fatload mmc 0   && fpga loadb 0  


 is a location in RAM in which the bitstream is temporarily stored 
(e.g. 0x10 but it depends on what else you have in memory)
 is the name of the bitstream file (e.g. fpga.bit)
 is the size of the bitstream file.

To get to the U-boot prompt just keep hitting return rapidly during the boot 
process. If that works then you can set the countdown to (e.g.) 3 seconds using 
the following command:

setenv bootdelay 3
saveenv

This assumes that your version of U-Boot has the FGPA load and boot delay 
functionality built in. If not you'll need to rebuild it with the necessary 
options enabled. 


ALAN LEVY, Lead Consultant, Embedded Systems

Plextek Consulting, The Plextek Building, London Road, Great Chesterford, 
Saffron Walden, CB10 1NY, UK
T: +44 (0) 1799 533200E: alan.l...@plextek.com  W: www.plextek.com


>-Original Message-
>Date: Tue, 26 Jun 2018 09:05:43 +
>From: Simon VII 
>To: Yocto discussion list 
>Subject: [yocto] loading FPGA bitfile with u-boot spl on ZYBO
>Message-ID:
>   
> 
>   
>Content-Type: text/plain; charset="utf-8"
>
>Goodmorning,
>
>
>I hope you can help me with the following matter.
>
>
>I am currently using the poky reference distribution to build a minimal 
>working example for the Zybo board (using the meta-xilinx layer), following 
>>this
> guide.
>
>
>After bitbaking the minimal example and putting everything on a partitioned SD 
>card, I can start u-boot and load the kernel.
>
>
>Everything seems fine up until here. My problem now is that before loading the 
>kernel, I would like to load a bitfile (xxx.bit) and program the FPGA. 
>Unfortunatelly I >haven't managed to get this to work.
>
>
>First of all, I am not getting an countdown to interrupt u-boot which I tried 
>to identify but was unable to. I am attaching the log from the boot process in 
>case it helps. I am >not sure if the u-boot spl is
>
>
>loaded (and executed).
>



>
>
>I would appreciate any suggestion or help to the right direction.
>
>
>Thanks
>
>Simon

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

Re: [yocto] loading FPGA bitfile with u-boot spl on ZYBO

[Nathan Rossi]

On 27 June 2018 at 16:58, Alan Levy  wrote:
> This is really a question for the meta-xilinx list but I'll answer it here 
> anyway.
>
> You need to add the following command (suitably edited) to uEnv.txt on the SD 
> card:
>
> fatload mmc 0   && fpga loadb 0  
> 
>
>  is a location in RAM in which the bitstream is temporarily 
> stored (e.g. 0x10 but it depends on what else you have in memory)
>  is the name of the bitstream file (e.g. fpga.bit)
>  is the size of the bitstream file.

The meta-xilinx layer has a recipe that will generate a uEnv.txt with
these commands. As long as there is a "bitstream", "*.bit" (U-Boot
fpga loadb command) or "*.bin" (U-Boot fpga load command) file in
IMAGE_BOOT_FILES.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/tree/meta-xilinx-bsp/recipes-bsp/u-boot/u-boot-zynq-uenv.bb

The "zybo-linux-bd-zynq7" machine is an example of this as it provides
a bitstream that is loaded by U-Boot.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/tree/meta-xilinx-bsp/conf/machine/zybo-linux-bd-zynq7.conf#n36

Also do keep in mind that you can load your bitstream using the FPGA
manager framework in the kernel (or the xdevcfg interface in older
xilinx kernels).

Regards,
Nathan

>
> To get to the U-boot prompt just keep hitting return rapidly during the boot 
> process. If that works then you can set the countdown to (e.g.) 3 seconds 
> using the following command:
>
> setenv bootdelay 3
> saveenv
>
> This assumes that your version of U-Boot has the FGPA load and boot delay 
> functionality built in. If not you'll need to rebuild it with the necessary 
> options enabled.
>
>
> ALAN LEVY, Lead Consultant, Embedded Systems
>
> Plextek Consulting, The Plextek Building, London Road, Great Chesterford, 
> Saffron Walden, CB10 1NY, UK
> T: +44 (0) 1799 533200E: alan.l...@plextek.com  W: www.plextek.com
>
>
>>-Original Message-
>>Date: Tue, 26 Jun 2018 09:05:43 +
>>From: Simon VII 
>>To: Yocto discussion list 
>>Subject: [yocto] loading FPGA bitfile with u-boot spl on ZYBO
>>Message-ID:
>>   
>> 
>>
>>Content-Type: text/plain; charset="utf-8"
>>
>>Goodmorning,
>>
>>
>>I hope you can help me with the following matter.
>>
>>
>>I am currently using the poky reference distribution to build a minimal 
>>working example for the Zybo board (using the meta-xilinx layer), following 
>>>this
>> guide.
>>
>>
>>After bitbaking the minimal example and putting everything on a partitioned 
>>SD card, I can start u-boot and load the kernel.
>>
>>
>>Everything seems fine up until here. My problem now is that before loading 
>>the kernel, I would like to load a bitfile (xxx.bit) and program the FPGA. 
>>Unfortunatelly I >haven't managed to get this to work.
>>
>>
>>First of all, I am not getting an countdown to interrupt u-boot which I tried 
>>to identify but was unable to. I am attaching the log from the boot process 
>>in case it helps. I am >not sure if the u-boot spl is
>>
>>
>>loaded (and executed).
>>
>
> 
>
>>
>>
>>I would appreciate any suggestion or help to the right direction.
>>
>>
>>Thanks
>>
>>Simon
>
> --
> ___
> 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] cmake toolchain file missing in SDK

[Guy Morand]

Hallo Yocto developpers!

Since my last SDK release, I cannot cross compile applications with 
cmake. I'm using yocto sumo. I get this error:


build$ cmake ../
CMake Error at 
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:100 
(message):

  Could not find toolchain file:
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/cmake/OEToolchainConfig.cmake
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


CMake Error: CMake was unable to find a build program corresponding to 
"Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to 
select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

It seems that the folder "cmake" is missing:

$ ls 
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/
X11  aclocal  aclocal-1.15  autoconf  automake-1.15 ca-certificates  
cmake-3.10  device_table-minimal.txt  gdb gnu-config  libtool  locale  
mime  opkg  qemu


However, it was working with a previous release ??!! And it seems to be 
installed in the cmake recipe:


https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/cmake/cmake_3.10.3.bb#n38

Has someone already faced this problem? What am I doing wrong?

Kind regards,

Guy

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

Re: [yocto] cmake toolchain file missing in SDK

[Guy Morand]

If I copy the missing toolchain file 
(meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake) manually 
into the extracted SDK, this fixes the issue.


But why was it not deployed automatically by yocto?

Regards,

Guy


On 06/27/18 12:31, Guy Morand wrote:

Hallo Yocto developpers!

Since my last SDK release, I cannot cross compile applications with 
cmake. I'm using yocto sumo. I get this error:


build$ cmake ../
CMake Error at 
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:100 
(message):

  Could not find toolchain file:
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/cmake/OEToolchainConfig.cmake 


Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


CMake Error: CMake was unable to find a build program corresponding to 
"Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need 
to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

It seems that the folder "cmake" is missing:

$ ls 
/opt/comet-linux/0.0.0-2018.06-last-guy/sysroots/x86_64-cometsdk-linux/usr/share/
X11  aclocal  aclocal-1.15  autoconf  automake-1.15 ca-certificates  
cmake-3.10  device_table-minimal.txt  gdb gnu-config  libtool  locale  
mime  opkg  qemu


However, it was working with a previous release ??!! And it seems to 
be installed in the cmake recipe:


https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/cmake/cmake_3.10.3.bb#n38 



Has someone already faced this problem? What am I doing wrong?

Kind regards,

Guy



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

Re: [yocto] loading FPGA bitfile with u-boot spl on ZYBO

[Philip Balister]

You might have better luck asking on the meta-xilinx list.

Philip

On 06/26/2018 08:05 PM, Simon VII wrote:
> Goodmorning,
> 
> 
> I hope you can help me with the following matter.
> 
> 
> I am currently using the poky reference distribution to build a minimal 
> working example for the Zybo board (using the meta-xilinx layer), following 
> this
>  guide.
> 
> 
> After bitbaking the minimal example and putting everything on a partitioned 
> SD card, I can start u-boot and load the kernel.
> 
> 
> Everything seems fine up until here. My problem now is that before loading 
> the kernel, I would like to load a bitfile (xxx.bit) and program the FPGA. 
> Unfortunatelly I haven't managed to get this to work.
> 
> 
> First of all, I am not getting an countdown to interrupt u-boot which I tried 
> to identify but was unable to. I am attaching the log from the boot process 
> in case it helps. I am not sure if the u-boot spl is
> 
> 
> loaded (and executed).
> 
> 
> Welcome to minicom 2.7
> 
> OPTIONS: I18n
> Compiled on Apr 25 2017, 21:09:25.
> Port /dev/ttyUSB1, 11:02:26
> 
> Press CTRL-A Z for help on special keys
> 
> 
> U-Boot SPL 2018.01 (Jun 22 2018 - 11:49:55)
> mmc boot
> Trying to boot from MMC1
> spl_load_image_fat_os: error reading image system.dtb, err - -2
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2018.01 (Jun 22 2018 - 11:49:55 +)
> 
> Model: Zynq ZYBO Development Board
> Board: Xilinx Zynq
> Silicon: v3.1
> I2C:   ready
> DRAM:  ECC disabled 512 MiB
> MMC:   sdhci@e010: 0
> SF: Detected s25fl128s_64k with page size 256 Bytes, erase size 64 KiB, total 
> 1B
> *** Warning - bad CRC, using default environment
> 
> In:serial@e0001000
> Out:   serial@e0001000
> Err:   serial@e0001000
> Net:   ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id
> I2C EEPROM MAC address read failed
> 
> Warning: ethernet@e000b000 (eth0) using random MAC address - 5e:69:c8:f8:cf:5b
> eth0: ethernet@e000b000
> reading uEnv.txt
> 451 bytes read in 10 ms (43.9 KiB/s)
> Importing environment from mmc ...
> Checking if uenvcmd is set ...
> Running uenvcmd ...
> reading uImage
> 3956792 bytes read in 228 ms (16.6 MiB/s)
> reading zynq-zybo.dtb
> 9222 bytes read in 17 ms (529.3 KiB/s)
> ## Booting kernel from Legacy Image at 0300 ...
>Image Name:   Linux-4.14.0-xilinx-v2018.1
>Image Type:   ARM Linux Kernel Image (uncompressed)
>Data Size:3956728 Bytes = 3.8 MiB
>Load Address: 8000
>Entry Point:  8000
>Verifying Checksum ... OK
> ## Flattened Device Tree blob at 0200
>Booting using the fdt blob at 0x200
>Loading Kernel Image ... OK
>Loading Device Tree to 1eb22000, end 1eb27405 ... OK
> 
> Starting kernel ...
> 
> Booting Linux on physical CPU 0x0
> Linux version 4.14.0-xilinx-v2018.1 (oe-user@oe-host) (gcc version 7.3.0 
> (GCC))8
> CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
> CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> OF: fdt: Machine model: Zynq ZYBO Development Board
> Memory policy: Data cache writealloc
> cma: Reserved 16 MiB at 0x1f00
> percpu: Embedded 16 pages/cpu @debc8000 s34764 r8192 d22580 u65536
> Built 1 zonelists, mobility grouping on.  Total pages: 130048
> Kernel command line: earlyprintk root=/dev/mmcblk0p2 rw rootwait
> PID hash table entries: 2048 (order: 1, 8192 bytes)
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Memory: 493068K/524288K available (6144K kernel code, 238K rwdata, 1560K 
> rodata)
> Virtual kernel memory layout:
> vector  : 0x - 0x1000   (   4 kB)
> fixmap  : 0xffc0 - 0xfff0   (3072 kB)
> vmalloc : 0xe080 - 0xff80   ( 496 MB)
> lowmem  : 0xc000 - 0xe000   ( 512 MB)
> pkmap   : 0xbfe0 - 0xc000   (   2 MB)
> modules : 0xbf00 - 0xbfe0   (  14 MB)
>   .text : 0xc0008000 - 0xc070   (7136 kB)
>   .init : 0xc090 - 0xc0a0   (1024 kB)
>   .data : 0xc0a0 - 0xc0a3b8c0   ( 239 kB)
>.bss : 0xc0a3b8c0 - 0xc0a61f84   ( 154 kB)
> Preemptible hierarchical RCU implementation.
> RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
> Tasks RCU enabled.
> RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
> NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
> efuse mapped to e080
> slcr mapped to e0802000
> L2C: platform modifies aux control register: 0x0206 -> 0x3246
> L2C: DT/platform modifies aux control register: 0x0206 -> 0x3246
> L2C-310 erratum 769419 enabled
> L2C-310 enabling early BRESP for Cortex-A9
> L2C-310 full line of zeros enabled for Cortex-A9
> L2C-310 dynamic clock gating enabled, standby mode enabled
> L2C-310 cache controller enabled, 8 ways, 512 kB
> L2C-310: CACHE_ID 0x41c8, AUX_CTRL 0x46460001
> zynq_clock_init: clkc starts 

Re: [yocto] Rocko: how to remove python3 from target's rootfs

[Bejar-Colonia, Carlos]

Hi Martin,

Just an update: The patch you pointed out, includes following line:
+PACKAGECONFIG[python] = 
"--with-python=${PYTHON},--without-python,,python3-core"

However, I found another patch from you: 
https://patchwork.openembedded.org/patch/147883/

which includes:
+PACKAGECONFIG[python] = 
"--with-python=${PYTHON},--without-python,python3-core,python3-core"

With that change, I was able to build core-image-minimal, and python3 is 
removed from target rootfs.

Thanks for the help
Carlos

-Original Message-
From: yocto-boun...@yoctoproject.org  On Behalf 
Of Bejar-Colonia, Carlos
Sent: Tuesday, June 26, 2018 5:27 PM
To: Martin Hundebøll ; Khem Raj 
Cc: Yocto Project 
Subject: Re: [yocto] Rocko: how to remove python3 from target's rootfs

Hi Martin,

I've downloaded bind_9.10.6.bb recipe and applied the patch you pointed, but 
do_install fails

error: invalid Python installation: unable to open 
/home/carlos/develop/allegro/build-atmel/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/bind/9.10.6-r0/recipe-sysroot/usr/lib/python3.5/config-3.5m/Makefile
 (No such file or directory)
Makefile:465: recipe for target 'install' failed
make[2]: *** [install] Error 1
make[2]: Leaving directory 
'/home/carlos/develop/allegro/build-atmel/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/bind/9.10.6-r0/build/bin/python'
Makefile:114: recipe for target 'install' failed
make[1]: *** [install] Error 1
make[1]: Leaving directory 
'/home/carlos/develop/allegro/build-atmel/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/bind/9.10.6-r0/build/bin'
Makefile:120: recipe for target 'install' failed
make: *** [install] Error 1
ERROR: oe_runmake failed

I've also tried the patch from Armin Kuster (Patch ID 151778), bind_9.12.1.bb 
builds fine, but dhcp_4.3.6.bb do_compile fails

./.libs/libomapi.so: undefined reference to `POST'
collect2: error: ld returned 1 exit status
Makefile:433: recipe for target 'svtest' failed
make[1]: *** [svtest] Error 1
make[1]: Leaving directory 
'/home/carlos/develop/allegro/build-atmel/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/dhcp/4.3.6-r0/build/omapip'
Makefile:464: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.

This error is similar to what is posted here: 
https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ferrors.yoctoproject.org%2FErrors%2FDetails%2F180628%2F&data=02%7C01%7Ccarlos.bejar-colonia%40philips.com%7C2bf072692e2e474451f508d5dbb8b70e%7C1a407a2d76754d178692b3ac285306e4%7C0%7C0%7C636656508753264238&sdata=joLMocU8wz3z5uAPMJ%2FigSK0mpbuPjkQPXUzeI0JKko%3D&reserved=0

Could you clarified if those errors were already handled, so I can fetch the 
fix?

Thanks,
Carlos

-Original Message-
From: Martin Hundebøll 
Sent: Tuesday, June 26, 2018 2:59 AM
To: Bejar-Colonia, Carlos ; Khem Raj 

Cc: Yocto Project 
Subject: Re: [yocto] Rocko: how to remove python3 from target's rootfs

Hi Bejar,

On 2018-06-25 22:02, Bejar-Colonia, Carlos wrote:
> Looks like the dhcp dependency is explicit: dhcp->bind->python3 
> recipes-connectivity/dhcp/dhcp.inc
>   DEPENDS = "openssl bind"
> recipes-connectivity/bind/bind_9.10.5-P3.bb
>   RDEPENDS_${PN} = "python3-core"
> 
> In the build area: dhcp/4.3.6-r0/packages-split/dhcp-client.shlibdeps
>   dhcp-libs (>= 4.3.6)
>   bind (>= 9.10.5-P3)
>   glibc (>= 2.26)
> 
> Does it mean that python3 cannot be removed from target rootfs?
> 
> On the other hand, I see this file in rootfs: /usr/sbin/dnssec-checkds, which 
> requires python3 (#! /usr/bin/python3).
> I believe this file gets installed from bind_9.10.5-P3.bb
> 
> do_install_append() {
>  sed -i -e '1s,#!.*python3,#! /usr/bin/python3,' 
> ${D}${sbindir}/dnssec-coverage ${D}${sbindir}/dnssec-checkds }
> 
> How can I move this file to a different package?

I had the same issue a while back, and submitted this patch:
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.openembedded.org%2Fpatch%2F148257%2F&data=02%7C01%7Ccarlos.bejar-colonia%40philips.com%7C5bf80069779142d49a9208d5db324507%7C1a407a2d76754d178692b3ac285306e4%7C0%7C0%7C636655931318995045&sdata=2QBW2XS2r7Kx3mQdTN%2BPVQpCvp%2Bh0TI7Ql6HPJymlBU%3D&reserved=0

Since then Armin incorporated my patch with his version upgrade here:
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.openembedded.org%2Fpatch%2F151778%2F&data=02%7C01%7Ccarlos.bejar-colonia%40philips.com%7C5bf80069779142d49a9208d5db324507%7C1a407a2d76754d178692b3ac285306e4%7C0%7C0%7C636655931318995045&sdata=yIMyeknuFenkNPGtG7ItvX6WzNnhhNbF1Exoca9vmNw%3D&reserved=0

If you maintain your own meta layer, you can either create a bbappend file to 
implement the package config feature, or you can simply add the updated version 
from Armin.

// Martin

> -Original Message-
> From: Khem Raj 
> Sent: Friday, June 22, 2018 11:33 AM
> To: Bejar-Colonia, Carlos 
> Cc: Yocto Project 
> Subject: Re: [yocto] Rocko: how 

[yocto] Regarding Use the Latest LTP on Latest YOCTO build

[Abhishek Kumar Rai]

Hi Team,

I am planning to use the LTP latest version on YOCTO latest vesion.
It seems that the earlier YOCTO versions are released with LTP and
latest version are not.
Found the below difficulties so far:
1. Latest LTP version(20180118) suitable for old gcc version(4.8).
2. But at the same time, latest version of YOCTO build(2.3) supporting
latest
gcc version(6.3) only.

so we want to use a latest LTP version(20180118) with latest YOCTO
build(2.3) which has latest gcc version(6.3) .

Please share your valuable inputs with me to achieve the same.

Thanks & Regards,
Abhishek Rai

-- 














The information contained in this e-mail message (including 
any 


attachments) may be confidential, proprietary, privileged, or 
otherwise


exempt from disclosure under applicable laws. It is intended to 
be 


conveyed only to the designated recipient(s). Any use, dissemination, 



distribution, printing, retaining or copying of this e-mail (including 
its 


attachments) by unintended recipient(s) is strictly prohibited and 
may 


be unlawful. If you are not an intended recipient of this e-mail, or 
believe 


that you have received this e-mail in error, please notify the 
sender 


immediately (by replying to this e-mail), delete any and all 
copies of 


this e-mail (including any attachments) from your system, and 
do not


disclose the content of this e-mail to any other person. Thank you 
for your cooperation.






-- 
_This e-mail message (including any attachments) may be confidential, 
proprietary, privileged, or otherwise exempt from disclosure under 
applicable laws. If you are not an intended recipient, please delete this 
message. Thank you.
_
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto