RE: Using Avnet Build Scripts to Build a PetaLinux BSP (2019.2 and earlier)

cthomas43 — Fri, 28 May 2021 07:41:37 GMT

I have been trying to run a script from /petalinux/scripts for one of the boards, but it fails with git tag saying that the reported hdl tag is blank and thus doesnt match the the requested tag. I am confident that it on the latest branch for both hdl and petalinux. Do you possibly know where I am going wrong?

RE: Using Avnet Build Scripts to Build a PetaLinux BSP (2019.2 and earlier)

lcaseiro — Tue, 09 Feb 2021 15:24:19 GMT

Hi,

I have been trying to use this process to get a working Ultra96-v2 petalinux project in petalinux 2017.4.

I have used pre-built bsps for several recent versions and they work great. However, I now need to create a project using module recipes provided by a third-party, which only provides them for version 2017.4 (I tried using the recipes in newer versions, with no success).

Since I could not find a pre-built BSP for the Ultra96-v2 for the 2017.4 tools, I have been trying to build one using these scripts.

I was able to generate the BSP, use it to create a Petalinux project and build that project.

The problem is... after copying everything to the SD card, the Ultra96 then fails to boot.. Using the USB-JTAG/UART adater, I get the output shown below, after which the board powers down.

I did not change anything in the Petalinux project after creating it from the BSP.

Do you have any idea why the project isn't working?

I was really hoping to get a working design for the 2017.4 tools...

Any help will be greatly appreciated!

Thank you very much,

Luis

UART BOOT LOG:

▒Xilinx Zynq MP First Stage Boot Loader

Release 2017.4 Feb 8 2021 - 19:21:34

U-Boot 2017.01 (Feb 08 2021 - 19:16:27 +0000) Xilinx ZynqMP ZCU100 RevC

I2C: ready

DRAM: 2 GiB

EL Level: EL2

Chip ID: xczu3eg

MMC: sdhci@ff160000: 0 (SD), sdhci@ff170000: 1

reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **

Using default environment

In: serial

Out: serial

Err: serial

Bootmode: SD_MODE

Net: Net Initialization Skipped

No ethernet found.

U-BOOT for ultra96v2-oob-2017-4

Hit any key to stop autoboot: 0

Device: sdhci@ff160000

Manufacturer ID: 58

OEM: 4444

Name: DDINC

Tran Speed: 50000000

Rd Block Len: 512

SD version 3.0

High Capacity: Yes

Capacity: 14.9 GiB

Bus Width: 4-bit

Erase Group Size: 512 Bytes

reading image.ub

13429872 bytes read in 968 ms (13.2 MiB/s)

## Loading kernel from FIT Image at 10000000 ...

Using 'conf@2' configuration

Trying 'kernel@0' kernel subimage

Description: Linux Kernel

Type: Kernel Image

Compression: uncompressed

Data Start: 0x100000d8

Data Size: 13378048 Bytes = 12.8 MiB

Architecture: AArch64

OS: Linux

Load Address: 0x00080000

Entry Point: 0x00080000

Hash algo: sha1

Hash value: 3ec3ac6a5c134d129b41d0c5e71c2ef0a9ed6880

Verifying Hash Integrity ... sha1+ OK

## Loading fdt from FIT Image at 10000000 ...

Using 'conf@2' configuration

Trying 'fdt@0' fdt subimage

Description: Flattened Device Tree blob

Type: Flat Device Tree

Compression: uncompressed

Data Start: 0x10cc23d0

Data Size: 50517 Bytes = 49.3 KiB

Architecture: AArch64

Hash algo: sha1

Hash value: 7b91167bd7f52e81d3a7fc8b0f7b034738f41469

Verifying Hash Integrity ... sha1+ OK

Booting using the fdt blob at 0x10cc23d0

Loading Kernel Image ... OK

Loading Device Tree to 0000000007ff0000, end 0000000007fff554 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0

[ 0.000000] Linux version 4.9.0-xilinx-v2017.4 (lse@Vbox) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Mon Feb 8 19:23:59 WET 2021

[ 0.000000] Boot CPU: AArch64 Processor [410fd034]

[ 0.000000] earlycon: cdns0 at MMIO 0x00000000ff010000 (options '115200n8')

[ 0.000000] bootconsole [cdns0] enabled

[ 0.000000] efi: Getting EFI parameters from FDT:

[ 0.000000] efi: UEFI not found.

[ 0.000000] cma: Reserved 256 MiB at 0x0000000070000000

[ 0.000000] psci: probing for conduit method from DT.

[ 0.000000] psci: PSCIv1.0 detected in firmware.

[ 0.000000] psci: Using standard PSCI v0.2 function IDs

[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.

[ 0.000000] percpu: Embedded 21 pages/cpu @ffffffc06ff6c000 s48152 r8192 d29672 u86016

[ 0.000000] Detected VIPT I-cache on CPU0

[ 0.000000] CPU features: enabling workaround for ARM erratum 845719

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517120

[ 0.000000] Kernel command line: earlycon clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait

[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)

[ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)

[ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)

[ 0.000000] Memory: 1789116K/2097152K available (9084K kernel code, 584K rwdata, 2836K rodata, 512K init, 397K bss, 45892K reserved, 262144K cma-reserved)

[ 0.000000] Virtual kernel memory layout:

[ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)

[ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000 ( 250 GB)

[ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008960000 ( 9088 KB)

[ 0.000000] .rodata : 0xffffff8008960000 - 0xffffff8008c30000 ( 2880 KB)

[ 0.000000] .init : 0xffffff8008c30000 - 0xffffff8008cb0000 ( 512 KB)

[ 0.000000] .data : 0xffffff8008cb0000 - 0xffffff8008d42200 ( 585 KB)

[ 0.000000] .bss : 0xffffff8008d42200 - 0xffffff8008da5634 ( 398 KB)

[ 0.000000] fixed : 0xffffffbefe7fd000 - 0xffffffbefec00000 ( 4108 KB)

[ 0.000000] PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000 ( 16 MB)

[ 0.000000] vmemmap : 0xffffffbf00000000 - 0xffffffc000000000 ( 4 GB maximum)

[ 0.000000] 0xffffffbf00000000 - 0xffffffbf01c00000 ( 28 MB actual)

[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc080000000 ( 2048 MB)

[ 0.000000] Hierarchical RCU implementation.

[ 0.000000] Build-time adjustment of leaf fanout to 64.

[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.

[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4

[ 0.000000] NR_IRQS:64 nr_irqs:64 0

[ 0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000

[ 0.000000] GIC: Using split EOI/Deactivate mode

[ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 100.00MHz (phys).

[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns

[ 0.000004] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns

[ 0.008374] Console: colour dummy device 80x25

[ 0.012627] console [tty0] enabled

[ 0.015993] bootconsole [cdns0] disabled

RE: Using Avnet Build Scripts to Build a PetaLinux BSP (2019.2 and earlier)

ece7498 — Tue, 09 Feb 2021 10:36:13 GMT

Hello again!

I achieved to run your instructions and produce a bsp and a linux-folder, import it on Vitis and run a vadd example. Great work by the way!
Now I want to modify the petalinux-configuration a bit, let's say I want to add the meta-ros layer (https://github.com/ros/meta-ros ).

My problem is that if I run `petalinux-config -c rootfs` after the script is run, it seems like the configuration after the build is not saved somewhere to re-use it (I can't see any of the packaged that script adds).

Am I correct? Is there a way to run the same configuration without re-running your scripts? Or I need to modify .config files in your scripts to add particular commands to add meta-ros?

I am trying to get the idea of re-use and modify based on your petalinux-configuration, as it works perfectly.

Thanks,

RE: Using Avnet Build Scripts to Build a PetaLinux BSP (2019.2 and earlier)

cmelement14 — Thu, 14 Jan 2021 02:08:20 GMT

The configs folder structure is totally different from 2020.1. Can I still follow this article from 2020.1 on wards?