Having Xilinx toolset already setup in version 2018.1 I'd like to create custom image with petalinux. Will updated BSP files be available in foreseeable future or I'd be better off falling back to 2017.4 or even 2017.2 version?
Best regards
MKu

Is it possible to get the schematic files and PCB files?

I recently ordered Ultra Zed  EV Starter Kit. It will still be a few weeks before I receive it.
I'm trying to get a jump start by learning vivado and would like to start with the sample design, but the link on zedboard.org shows no files:
http://www.zedboard.org/support/design/21811/
Can someone point me to the design?
Thanks.

Hi,
We would like to use the same power ic - Infineon IRPS5401MTRPBF PMIC on our own carrier board for the UltraZed-EG SOM. Could you please provide the PowIRCenter configuration file to us? Thank you very much!
Best,
Pei

I have a black SOM and carrier card of Ultrazed from which I assume that I have the production SOM. This meant that I did not have to add an init.tcl file in the scripts folder for adding the board definition files. But the ultrazed board option became available in Vivado only after I added the tcl file in the scripts folder.
I have followed the UltraZed-EG Starter Kit Tutorial for vivado 2016.4 but I am working with 2017.4. I am unable to run a hello world application from Xilinx SDK on the Ultrazed board. If gives the following error:

Error while launching program: 

Could not find ARM device on the board for connection 'Local'.

How do I solve this problem?

I am look to find the 3D models for the PCIE CC for the Ultrascale EV module.  please help direct me to the right file.  it does not look to be avialable online.
 
thank you,
Frank Handal

What has happened to Avnet's support? I have been trying for well over a month to get an RMA for a defective UltraZed starter kit only to be completely stonewalled!

I put a case in, got the standard "welcome to Microslop CRM" email with a case number. No human response for a week. Multiple follow-up emails yielded nothing. I finally called and they assured me the case would be responded to within 24 hours.

Three days later, I called again. The woman I talked to was rather rude and just told me she forwarded it again and I would hear back in 24 hours.

I finally called a sales number and the next day they asked what were my issues. I described it (AGAIN) even though it was all in the CRM case. I received an email stating that they agreed it was defective and I should recieve RMA instructions shortly. Three days later, I emailed him again, only find out my email has now been blocked!

I used my employer's email to contact him again, only to find out he's on vacation until after July 4th and to email the support address. When I did that (last week), all it did was generate a new CRM case and told me I would receive a reply within 72 hours. That was a week ago.

What has happened to Avnet support? Why are they so rude, incompetent and completely unresponsive?

Hello All,

If you are experiencing power supply failures with your UltraZed 3EG please read this post.

We have seen some cases of failure when using some LTE power supplies inconjunction with the UltraZed 3EG. In some cases they go into foldback when the FPD is entered, this depends on the PL load.

To help accomidate for this underperforming wall power adapter we have designed in a low pass filter on the EG IOCC and PCIe Carrier Cards. However this is not ideal as a reference, we suggest the use of the ITE marked power supplies as no failures have been seen with this model.

Thanks,

Josh

Hi,
We have several UltraZed SoM. Two with iocc and a few purchased separately.
There appears to be a different revision between our boards.
Some have US1SOM-1-01-06 and the rest have US1SOM-1-02-00.
Is there any difference between the two revisions?
Thanks,
Richard.

Hello All,

If you have recieved one of the first 18 shipped UltraZed EV Starter Kits the PCIe Clocks on the Carrier Card were not programmed. This only affects those whom need the PCIe interface for their desired application.

To program the PCIe interface is simple. Travel to the following link which takes you to the documentation page for the UltraZed EV http://zedboard.org/support/documentation/22581 and download the file labeled UltraZed EV Carrier Card FAT. 

This will provide you with a file labeled Avnet_UltraZed-7EV_Carrier_2017_3_FAT_Release_RC1.zip. Unzip the contents (Boot.bin, image.ub) to an SD Card, set the UltraZedEV Starter kit to SD card boot. Plug in the SD Card to the Started Kit and power on to boot from SD Card.

At the end of the test your PCIe clocks will be programmed correctly.

Note: Do no worry if you see failure in the terminal window for any of the Carrier Cards interfaces. This is due to not having the correct Hardware plugged in to pass the tests.

Feel free to PM me with questions.

--Josh

I tried UltraZed Board with the off-the-shelf SD Card and it's booting correctly.

But I have a problem with the Ethernet, I cannot find eth0

I attached the linux booting log file.

I have in trace:

[    3.423519] macb ff0e0000.ethernet eth0: Could not attach to PHY

Do you have an idea how to solve this problem?

<!--break-->

---------- Log -------------

Avnet modifying SDHCI0 and SDHCI1 registers for UltraZed SOM

Xilinx Zynq MP First Stage Boot Loader

Release 2016.2   Dec  2 2016  -  00:38:48

Platform: Silicon, Cluster ID 0x80000000

Running on A53-0 (64-bit) Processor

Processor Initialization Done

================= In Stage 2 ============

SD1 Boot Mode

SD: rc= 0

File name is 1:/BOOT.BIN

Multiboot Reg : 0x0

Image Header Table Offset 0x8C0

*****Image Header Table Details********

Boot Gen Ver: 0x1020000

No of Partitions: 0x4

Partition Header Address: 0x280

Partition Present Device: 0x0

Initialization Success

======= In Stage 3, Partition No:1 =======

UnEncrypted data Length: 0x153E27

Data word offset: 0x153E27

Total Data word length: 0x153E27

Destination Load Address: 0xFFFFFFFF

Execution Address: 0x0

Data word offset: 0x72F0

Partition Attributes: 0x20

Destination Device is PL, changing LoadAddress

Bitstream download to start now

DMA transfer done

PL Configuration done successfully

Partition 1 Load Success

======= In Stage 3, Partition No:2 =======

UnEncrypted data Length: 0x1810

Data word offset: 0x1810

Total Data word length: 0x1810

Destination Load Address: 0xFFFE5000

Execution Address: 0xFFFE5000

Data word offset: 0x15B120

Partition Attributes: 0x100

Partition 2 Load Success

======= In Stage 3, Partition No:3 =======

UnEncrypted data Length: 0x17CE4

Data word offset: 0x17CE4

Total Data word length: 0x17CE4

Destination Load Address: 0x8000000

Execution Address: 0x8000000

Data word offset: 0x15C930

Partition Attributes: 0x100

Partition 3 Load Success

All Partitions Loaded

================= In Stage 4 ============

Running +II=I▒   Incorrect XILINX IDCODE 0x14710093, maskid 0x4600093

NOTICE:  ATF running on XCZUUNKN/silicon v4/RTL5.1 at 0xfffe5000

NOTICE:  BL31: Secure code at 0x60000000

NOTICE:  BL31: Non secure code at 0x8000000

NOTICE:  BL31: v1.2(release):f9b7cd8

NOTICE:  BL31: Built : 00:38:53, Dec  2 2016

U-Boot 2016.01 (Dec 02 2016 - 00:40:10 -0700)

DRAM:  2 GiB

Enabling Caches...

EL Level:       EL2

MMC:   sdhci@ff160000: 0, sdhci@ff170000: 1

Invalid bus 0 (err=-19)

*** Warning - spi_flash_probe() failed, using default environment

## Error: flags type check failure for "serverip"<= "AUTO" (type: i)

himport_r: can't insert "serverip=AUTO" into hash table

In:    serial

Out:   serial

Err:   serial

Bootmode: SD_MODE1

Net:   ZYNQ GEM: ff0e0000, phyaddr 5, interface rgmii-id

eth0: ethernet@ff0e0000

U-BOOT for uz3eg-2016-2

Hit any key to stop autoboot:  0

Device: sdhci@ff160000

Manufacturer ID: 13

OEM: 14e

Name: Q2J55

Tran Speed: 52000000

Rd Block Len: 512

MMC version 5.0

High Capacity: Yes

Capacity: 7.1 GiB

Bus Width: 8-bit

Erase Group Size: 512 KiB

HC WP Group Size: 8 MiB

User Capacity: 7.1 GiB WRREL

Boot Capacity: 16 MiB ENH

RPMB Capacity: 4 MiB ENH

reading image.ub

21897092 bytes read in 1420 ms (14.7 MiB/s)

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

   Using 'conf@1' configuration

   Trying 'kernel@1' kernel subimage

     Description:  PetaLinux Kernel

     Type:         Kernel Image

     Compression:  gzip compressed

     Data Start:   0x100000f4

     Data Size:    21868258 Bytes = 20.9 MiB

     Architecture: AArch64

     OS:           Linux

     Load Address: 0x00080000

     Entry Point:  0x00080000

     Hash algo:    crc32

     Hash value:   515e2759

   Verifying Hash Integrity ... crc32+ OK

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

   Using 'conf@1' configuration

   Trying 'fdt@1' fdt subimage

     Description:  Flattened Device Tree blob

     Type:         Flat Device Tree

     Compression:  uncompressed

     Data Start:   0x114db0c0

     Data Size:    27524 Bytes = 26.9 KiB

     Architecture: AArch64

     Hash algo:    crc32

     Hash value:   15a0a06b

   Verifying Hash Integrity ... crc32+ OK

   Booting using the fdt blob at 0x114db0c0

   Uncompressing Kernel Image ... OK

   Loading Device Tree to 0000000007ff6000, end 0000000007fffb83 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.4.0 (training@localhost.localdomain) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #2 SMP Fri Dec 2 00:42:01 MST 2016

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

[    0.000000] earlycon: Early serial console at MMIO 0xff000000 (options '115200n8')

[    0.000000] bootconsole [uart0] enabled

[    0.000000] cma: Reserved 128 MiB at 0x0000000078000000

[    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 16 pages/cpu @ffffffc077f8e000 s24704 r8192 d32640 u65536

[    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=cdns,mmio,0xFF000000,115200n8

[    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] software IO TLB [mem 0x71e00000-0x75e00000] (64MB) mapped at [ffffffc071e00000-ffffffc075dfffff]

[    0.000000] Memory: 1840360K/2097152K available (7198K kernel code, 520K rwdata, 2736K rodata, 16596K init, 356K bss, 125720K reserved, 131072K cma-reserved)

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000   (   247 GB)

[    0.000000]     vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000   (     7 GB maximum)

[    0.000000]               0xffffffbe00000000 - 0xffffffbe01c00000   (    28 MB actual)

[    0.000000]     fixed   : 0xffffffbffa7fd000 - 0xffffffbffac00000   (  4108 KB)

[    0.000000]     PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000   (    16 MB)

[    0.000000]     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 MB)

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

[    0.000000]       .init : 0xffffffc000a35000 - 0xffffffc001a6a000   ( 16596 KB)

[    0.000000]       .text : 0xffffffc000080000 - 0xffffffc000a34044   (  9937 KB)

[    0.000000]       .data : 0xffffffc001a7c000 - 0xffffffc001afe160   (   521 KB)

[    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] 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.008361] Console: colour dummy device 80x25

[    0.012619] console [tty0] enabled

[    0.015984] bootconsole [uart0] disabled

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.4.0 (training@localhost.localdomain) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #2 SMP Fri Dec 2 00:42:01 MST 2016

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

[    0.000000] earlycon: Early serial console at MMIO 0xff000000 (options '115200n8')

[    0.000000] bootconsole [uart0] enabled

[    0.000000] cma: Reserved 128 MiB at 0x0000000078000000

[    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 16 pages/cpu @ffffffc077f8e000 s24704 r8192 d32640 u65536

[    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=cdns,mmio,0xFF000000,115200n8

[    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] software IO TLB [mem 0x71e00000-0x75e00000] (64MB) mapped at [ffffffc071e00000-ffffffc075dfffff]

[    0.000000] Memory: 1840360K/2097152K available (7198K kernel code, 520K rwdata, 2736K rodata, 16596K init, 356K bss, 125720K reserved, 131072K cma-reserved)

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000   (   247 GB)

[    0.000000]     vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000   (     7 GB maximum)

[    0.000000]               0xffffffbe00000000 - 0xffffffbe01c00000   (    28 MB actual)

[    0.000000]     fixed   : 0xffffffbffa7fd000 - 0xffffffbffac00000   (  4108 KB)

[    0.000000]     PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000   (    16 MB)

[    0.000000]     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 MB)

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

[    0.000000]       .init : 0xffffffc000a35000 - 0xffffffc001a6a000   ( 16596 KB)

[    0.000000]       .text : 0xffffffc000080000 - 0xffffffc000a34044   (  9937 KB)

[    0.000000]       .data : 0xffffffc001a7c000 - 0xffffffc001afe160   (   521 KB)

[    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] 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.008361] Console: colour dummy device 80x25

[    0.012619] console [tty0] enabled

[    0.015984] bootconsole [uart0] disabled

[    0.019892] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=400000)

[    0.019907] pid_max: default: 32768 minimum: 301

[    0.020041] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)

[    0.020052] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)

[    0.020755] ASID allocator initialised with 65536 entries

[    0.021614] Detected VIPT I-cache on CPU1

[    0.021639] CPU1: Booted secondary processor [410fd034]

[    0.021861] Detected VIPT I-cache on CPU2

[    0.021877] CPU2: Booted secondary processor [410fd034]

[    0.022087] Detected VIPT I-cache on CPU3

[    0.022103] CPU3: Booted secondary processor [410fd034]

[    0.022132] Brought up 4 CPUs

[    0.022168] SMP: Total of 4 processors activated.

[    0.022178] CPU: All CPU(s) started at EL2

[    0.022196] alternatives: patching kernel code

[    0.022486] devtmpfs: initialized

[    0.026191] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

[    0.029160] xor: measuring software checksum speed

[    0.067983]    8regs     :  2178.000 MB/sec

[    0.108012]    8regs_prefetch:  1990.000 MB/sec

[    0.148041]    32regs    :  2413.000 MB/sec

[    0.188071]    32regs_prefetch:  2254.000 MB/sec

[    0.188085] xor: using function: 32regs (2413.000 MB/sec)

[    0.188598] NET: Registered protocol family 16

[    0.200094] cpuidle: using governor ladder

[    0.212101] cpuidle: using governor menu

[    0.212146] vdso: 2 pages (1 code @ ffffffc001a81000, 1 data @ ffffffc001a80000)

[    0.212184] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.

[    0.212801] DMA: preallocated 256 KiB pool for atomic allocations

[    0.213713] ARM CCI_400_r1 PMU driver probed

[    0.300317] raid6: int64x1  gen()   393 MB/s

[    0.368320] raid6: int64x1  xor()   355 MB/s

[    0.436475] raid6: int64x2  gen()   607 MB/s

[    0.504467] raid6: int64x2  xor()   496 MB/s

[    0.572533] raid6: int64x4  gen()   903 MB/s

[    0.640610] raid6: int64x4  xor()   652 MB/s

[    0.708717] raid6: int64x8  gen()   935 MB/s

[    0.776746] raid6: int64x8  xor()   661 MB/s

[    0.844812] raid6: neonx1   gen()   653 MB/s

[    0.912869] raid6: neonx1   xor()   600 MB/s

[    0.980986] raid6: neonx2   gen()  1031 MB/s

[    1.049022] raid6: neonx2   xor()   891 MB/s

[    1.117089] raid6: neonx4   gen()  1395 MB/s

[    1.185149] raid6: neonx4   xor()  1074 MB/s

[    1.253233] raid6: neonx8   gen()  1418 MB/s

[    1.321291] raid6: neonx8   xor()  1088 MB/s

[    1.321304] raid6: using algorithm neonx8 gen() 1418 MB/s

[    1.321317] raid6: .... xor() 1088 MB/s, rmw enabled

[    1.321329] raid6: using intx1 recovery algorithm

[    1.321562] ACPI: Interpreter disabled.

[    1.322036] arm-smmu fd800000.smmu: probing hardware configuration...

[    1.322053] arm-smmu fd800000.smmu: SMMUv2 with:

[    1.322067] arm-smmu fd800000.smmu:  stage 1 translation

[    1.322082] arm-smmu fd800000.smmu:  stage 2 translation

[    1.322095] arm-smmu fd800000.smmu:  nested translation

[    1.322114] arm-smmu fd800000.smmu:  stream matching with 48 register groups, mask 0x7fff

[    1.322136] arm-smmu fd800000.smmu:  16 context banks (0 stage-2 only)

[    1.322153] arm-smmu fd800000.smmu:  Supported page sizes: 0x60211000

[    1.322169] arm-smmu fd800000.smmu:  Stage-1: 48-bit VA -> 48-bit IPA

[    1.322184] arm-smmu fd800000.smmu:  Stage-2: 48-bit IPA -> 48-bit PA

[    1.323024] arm-smmu fd800000.smmu: registered 26 master devices

[    1.323273] iommu: Adding device fd500000.dma to group 0

[    1.323303] iommu: Adding device fd510000.dma to group 1

[    1.323331] iommu: Adding device fd520000.dma to group 2

[    1.323359] iommu: Adding device fd530000.dma to group 3

[    1.323386] iommu: Adding device fd540000.dma to group 4

[    1.323417] iommu: Adding device fd550000.dma to group 5

[    1.323445] iommu: Adding device fd560000.dma to group 6

[    1.323473] iommu: Adding device fd570000.dma to group 7

[    1.323512] iommu: Adding device ffa80000.dma to group 8

[    1.323540] iommu: Adding device ffa90000.dma to group 9

[    1.323569] iommu: Adding device ffaa0000.dma to group 10

[    1.323597] iommu: Adding device ffab0000.dma to group 11

[    1.323625] iommu: Adding device ffac0000.dma to group 12

[    1.323656] iommu: Adding device ffad0000.dma to group 13

[    1.323685] iommu: Adding device ffae0000.dma to group 14

[    1.323713] iommu: Adding device ffaf0000.dma to group 15

[    1.323752] iommu: Adding device ff0e0000.ethernet to group 16

[    1.323812] iommu: Adding device ff0f0000.spi to group 17

[    1.323871] iommu: Adding device ff160000.sdhci to group 18

[    1.323900] iommu: Adding device ff170000.sdhci to group 19

[    1.323966] iommu: Adding device amba:usb@fe200000 to group 20

[    1.324319] SCSI subsystem initialized

[    1.324547] usbcore: registered new interface driver usbfs

[    1.324595] usbcore: registered new interface driver hub

[    1.324642] usbcore: registered new device driver usb

[    1.324749] media: Linux media interface: v0.10

[    1.324795] Linux video capture interface: v2.00

[    1.324838] pps_core: LinuxPPS API ver. 1 registered

[    1.324851] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>

[    1.324890] PTP clock support registered

[    1.324939] EDAC MC: Ver: 3.0.0

[    1.325214] Advanced Linux Sound Architecture Driver Initialized.

[    1.325683] clocksource: Switched to clocksource arch_sys_counter

[    1.325967] pnp: PnP ACPI: disabled

[    1.331416] NET: Registered protocol family 2

[    1.331840] TCP established hash table entries: 16384 (order: 5, 131072 bytes)

[    1.332003] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)

[    1.332291] TCP: Hash tables configured (established 16384 bind 16384)

[    1.332363] UDP hash table entries: 1024 (order: 3, 32768 bytes)

[    1.332420] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)

[    1.332588] NET: Registered protocol family 1

[    1.332836] RPC: Registered named UNIX socket transport module.

[    1.332851] RPC: Registered udp transport module.

[    1.332863] RPC: Registered tcp transport module.

[    1.332875] RPC: Registered tcp NFSv4.1 backchannel transport module.

[    2.058861] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available

[    2.059589] futex hash table entries: 1024 (order: 5, 131072 bytes)

[    2.059695] audit: initializing netlink subsys (disabled)

[    2.059743] audit: type=2000 audit(2.048:1): initialized

[    2.060227] HugeTLB registered 2 MB page size, pre-allocated 0 pages

[    2.060601] VFS: Disk quotas dquot_6.6.0

[    2.060650] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

[    2.061192] NFS: Registering the id_resolver key type

[    2.061230] Key type id_resolver registered

[    2.061243] Key type id_legacy registered

[    2.061266] nfs4filelayout_init: NFSv4 File Layout Driver Registering...

[    2.061315] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.

[    2.062331] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)

[    2.062358] io scheduler noop registered

[    2.062373] io scheduler deadline registered

[    2.062403] io scheduler cfq registered (default)

[    2.063300] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed

[    2.063547] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success

[    2.063676] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success

[    2.063805] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success

[    2.063932] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success

[    2.064061] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success

[    2.064194] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success

[    2.064331] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success

[    2.064460] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success

[    2.064532] xilinx-zynqmp-dma ffa80000.dma: main clock not found.

[    2.064548] xilinx-zynqmp-dma ffa80000.dma: Probing channel failed

[    2.064582] xilinx-zynqmp-dma: probe of ffa80000.dma failed with error -2

[    2.064647] xilinx-zynqmp-dma ffa90000.dma: main clock not found.

[    2.064662] xilinx-zynqmp-dma ffa90000.dma: Probing channel failed

[    2.064684] xilinx-zynqmp-dma: probe of ffa90000.dma failed with error -2

[    2.064751] xilinx-zynqmp-dma ffaa0000.dma: main clock not found.

[    2.064766] xilinx-zynqmp-dma ffaa0000.dma: Probing channel failed

[    2.064788] xilinx-zynqmp-dma: probe of ffaa0000.dma failed with error -2

[    2.064852] xilinx-zynqmp-dma ffab0000.dma: main clock not found.

[    2.064867] xilinx-zynqmp-dma ffab0000.dma: Probing channel failed

[    2.064889] xilinx-zynqmp-dma: probe of ffab0000.dma failed with error -2

[    2.064953] xilinx-zynqmp-dma ffac0000.dma: main clock not found.

[    2.064969] xilinx-zynqmp-dma ffac0000.dma: Probing channel failed

[    2.064990] xilinx-zynqmp-dma: probe of ffac0000.dma failed with error -2

[    2.065053] xilinx-zynqmp-dma ffad0000.dma: main clock not found.

[    2.065069] xilinx-zynqmp-dma ffad0000.dma: Probing channel failed

[    2.065090] xilinx-zynqmp-dma: probe of ffad0000.dma failed with error -2

[    2.065154] xilinx-zynqmp-dma ffae0000.dma: main clock not found.

[    2.065169] xilinx-zynqmp-dma ffae0000.dma: Probing channel failed

[    2.065190] xilinx-zynqmp-dma: probe of ffae0000.dma failed with error -2

[    2.065255] xilinx-zynqmp-dma ffaf0000.dma: main clock not found.

[    2.065271] xilinx-zynqmp-dma ffaf0000.dma: Probing channel failed

[    2.065292] xilinx-zynqmp-dma: probe of ffaf0000.dma failed with error -2

[    2.065376] zynqmp_pm_probe power management API version error. Expected: v0.2 - Found: v0.0

[    2.065400] zynqmp_pm: probe of firmware failed with error -5

[    2.065490] xenfs: not registering filesystem on non-xen platform

[    2.089753] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled

[    2.090961] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 214, base_baud = 6250000) is a xuartps

[    3.272631] console [ttyPS0] enabled

[    3.276405] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 215, base_baud = 6250000) is a xuartps

[    3.286669] [drm] Initialized drm 1.1.0 20060810

[    3.291611] Unable to detect cache hierarchy from DT for CPU 0

[    3.302136] brd: module loaded

[    3.308047] loop: module loaded

[    3.311838] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode

[    3.320746] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst

[    3.331119] scsi host0: ahci-ceva

[    3.334694] scsi host1: ahci-ceva

[    3.338123] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 210

[    3.346068] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 210

[    3.354226] mtdoops: mtd device (mtddev=name/number) must be supplied

[    3.361337] m25p80 spi32766.0: Controller not in SPI_TX_QUAD mode, just use extended SPI mode

[    3.369845] m25p80 spi32766.0: n25q256a (65536 Kbytes)

[    3.374932] 3 ofpart partitions found on MTD device spi32766.0

[    3.380720] Creating 3 MTD partitions on "spi32766.0":

[    3.385842] 0x000000000000-0x000000780000 : "qspi-boot"

[    3.391556] 0x000000780000-0x000000800000 : "qspi-bootenv"

[    3.397416] 0x000000800000-0x000004000000 : "qspi-linux"

[    3.404781] libphy: Fixed MDIO Bus: probed

[    3.409314] CAN device driver interface

[    3.413939] libphy: MACB_mii_bus: probed

[    3.423519] macb ff0e0000.ethernet eth0: Could not attach to PHY

[    3.651038] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    3.657496] ehci-pci: EHCI PCI platform driver

[    3.662122] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller

[    3.667545] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1

[    3.673693] ata2: SATA link down (SStatus 0 SControl 330)

[    3.673720] ata1: SATA link down (SStatus 0 SControl 330)

[    3.686162] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x00010010

[    3.694814] xhci-hcd xhci-hcd.0.auto: irq 219, io mem 0xfe200000

[    3.700868] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

[    3.707591] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    3.714795] usb usb1: Product: xHCI Host Controller

[    3.719647] usb usb1: Manufacturer: Linux 4.4.0 xhci-hcd

[    3.724942] usb usb1: SerialNumber: xhci-hcd.0.auto

[    3.730090] hub 1-0:1.0: USB hub found

[    3.733787] hub 1-0:1.0: 1 port detected

[    3.737796] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller

[    3.743211] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2

[    3.750888] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.

[    3.758991] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003

[    3.765708] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    3.772915] usb usb2: Product: xHCI Host Controller

[    3.777768] usb usb2: Manufacturer: Linux 4.4.0 xhci-hcd

[    3.783063] usb usb2: SerialNumber: xhci-hcd.0.auto

[    3.788164] hub 2-0:1.0: USB hub found

[    3.791857] hub 2-0:1.0: 1 port detected

[    3.795918] usbcore: registered new interface driver uas

[    3.801224] usbcore: registered new interface driver usb-storage

[    3.807362] mousedev: PS/2 mouse device common for all mice

[    3.813230] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0

[    3.820428] i2c /dev entries driver

[    3.824159] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 205

[    3.830623] at24 1-0052: 1024 byte 24c08 EEPROM, writable, 1 bytes/write

[    3.837260] i2c i2c-0: Added multiplexed i2c bus 1

[    3.842151] i2c i2c-0: Added multiplexed i2c bus 2

[    3.846866] pca954x 0-0070: registered 2 multiplexed busses for I2C mux pca9542

[    3.855115] EDAC MC: ECC not enabled

[    3.858701] sdhci: Secure Digital Host Controller Interface driver

[    3.864802] sdhci: Copyright(c) Pierre Ossman

[    3.869145] sdhci-pltfm: SDHCI platform and OF driver helper

[    3.876017] sdhci-arasan ff160000.sdhci: No vmmc regulator found

[    3.881948] sdhci-arasan ff160000.sdhci: No vqmmc regulator found

[    3.929689] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit

[    3.942006] sdhci-arasan ff170000.sdhci: No vmmc regulator found

[    3.947949] sdhci-arasan ff170000.sdhci: No vqmmc regulator found

[    4.001688] mmc1: SDHCI controller on ff170000.sdhci [ff170000.sdhci] using ADMA 64-bit

[    4.009803] usbcore: registered new interface driver usbhid

[    4.015301] usbhid: USB HID core driver

[    4.019727] Mali: Mali device driver loaded

[    4.024561] pktgen: Packet Generator for packet performance testing. Version: 2.75

[    4.032347] Initializing XFRM netlink socket

[    4.036564] mmc0: MAN_BKOPS_EN bit is not set

[    4.040919] NET: Registered protocol family 10

[    4.045760] sit: IPv6 over IPv4 tunneling driver

[    4.050686] NET: Registered protocol family 17

[    4.055071] NET: Registered protocol family 15

[    4.059484] can: controller area network core (rev 20120528 abi 9)

[    4.065681] NET: Registered protocol family 29

[    4.070076] can: raw protocol (rev 20120528)

[    4.074327] can: broadcast manager protocol (rev 20120528 t)

[    4.079972] can: netlink gateway (rev 20130117) max_hops=1

[    4.087505] Key type dns_resolver registered

[    4.092023] registered taskstats version 1

[    4.097141] Btrfs loaded

[    4.097265] mmc0: new HS200 MMC card at address 0001

[    4.097494] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB

[    4.097593] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB

[    4.097707] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB

[    4.097801] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB

[    4.098627]  mmcblk0: p1

[    4.129610] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01 00:00:08 UTC (8)

[    4.137825] ALSA device list:

[    4.140706]   No soundcards found.

[    4.150964] Freeing unused kernel memory: 16596K (ffffffc000a35000 - ffffffc001a6a000)

[    4.158836] Freeing alternatives memory: 52K (ffffffc001a6a000 - ffffffc001a77000)

[    4.163330] mmc1: new high speed SDHC card at address 0007

[    4.163572] mmcblk1: mmc1:0007 SD16G 14.4 GiB (ro)

[    4.165393]  mmcblk1: p1

INIT: version 2.88 booting

[    4.389458] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

[    4.436217] EXT4-fs (mmcblk0rpmb): unable to read superblock

[    4.442062] EXT4-fs (mmcblk0rpmb): unable to read superblock

[    4.447835] EXT2-fs (mmcblk0rpmb): error: unable to read superblock

[    4.454178] FAT-fs (mmcblk0rpmb): unable to read boot sector

[    4.463810] EXT4-fs (mmcblk0rpmb): unable to read superblock

[    4.469543] EXT4-fs (mmcblk0rpmb): unable to read superblock

[    4.475284] EXT2-fs (mmcblk0rpmb): error: unable to read superblock

[    4.481844] FAT-fs (mmcblk0rpmb): unable to read boot sector

[    4.487569] FAT-fs (mmcblk0rpmb): unable to read boot sector

mount: mounting /dev/mmcblk0rpmb on /run/media/mmcblk0rpmb failed: Invalid argument

mount: mounting /dev/mmcblk0boot0 on /run/media/mmcblk0boot0 failed: Invalid argument

mount: mounting /dev/mmcblk0boot1 on /run/media/mmcblk0boot1 failed: Invalid argument

sh: /sys/block/mmcblk0/mmcblk0p1: unknown operand

mount: mounting /dev/mmcblk0 on /run/media/mmcblk0 failed: Device or resource busy

Creating /dev/flash/* device nodes

[    4.616322] random: dd urandom read with 4 bits of entropy available

Starting internet superserver: inetd.

INIT: Entering runlevel: 5

Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device

Starting Dropbear SSH server: Generating key, this may take a while...

Public key portion is:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCVAF1Mj3mH3sP04ecCB4kye5DtDNkpEfUHD0qoLCWTEqs6cfSO5CwX5tfjYCDEAT/+EfH7dKHQtLZ3eEEUSeDY3QOBRC1ZqIhwzgfQaNAqmBbVTdWp4GrLSVJWGR7dVvHIV6M6MQ+AmbEHt2anZl50JyFP1T8cU5g2V6a5H2xFyz0dwl2X60ZuVQmKApzOD14/zhfsvjDRUXuRO/RtpOJJr7qibEVy8mxasJY6TBwvJJDwswwClwjWiMv+UPkrdKNMvT+gb4T1W94Y9BxHtVWj0H1wfPSR1UaQAmQot5f83FBtdKOmXytgZu/DQsCz/F0quq0MxEG2khFI7W13xlyJ root@uz3eg-2016-2

Fingerprint: md5 8b:4c:9c:2d:2a:3c:50:35:20:3a:ce:f3:f8:74:97:d6

dropbear.

starting Busybox HTTP Daemon: httpd... done.

*********************************************************************

***                                                               ***

***   Avnet UltraZed Out Of Box PetaLinux Build V1.0              ***

***                                                               ***

***   Based Upon the UZ3EG 2016.2 PetaLinux BSP from Avnet        ***

***                                                               ***

***   More information available on UltraZed.org community site   ***

***                                                               ***

*********************************************************************

uz3eg-2016-2 login: root

Password:

login[1865]: root login on 'ttyPS0'

root@uz3eg-2016-2:~#

root@uz3eg-2016-2:~# ipconfig -a

-sh: ipconfig: not found

root@uz3eg-2016-2:~# ifconfig -a

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4

          NOARP  MTU:1480  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@uz3eg-2016-2:~#

I am interested in spinning a custom carrier board with the TI ADS54J40 dual channel 14 bit ADC chip operating at 1GSPS. The interface standard for the ADC chip is JESD204B. Would I be able to use the Ultrazed SOM to read data off it by designing the custom board to mate with the ADC carrier card? 

Hi all!

I wanted to let everyone know that we have published the Baremetal SDSoC 2018.2 UltraZed-EV platform file.

You can find this in the downloads for reference designs on the dot org site.

Install instructions are located within.

You can get this by heading to the UltraZed-EV reference designs page:

http://ultra96.org/support/design/24166/156

Then search for "SDSoC" and locate:

SDSoC Platform Support Packages

From there, download, extract, follow the install instructions and have fun!

--Dan

Hello all,

I wanted to make this post to inform everyone that we have had an issue with our manufacturing of the UltraZed-EV Starter Kit.  We are still investigating where the miscommunication happened, but if you received your UltraZed-EV Starter Kit and it appears that the power is not coming up, and thus the board is NOT booting, there is a SIMPLE solution!

The kits are leaving manufacturing with JP3 populated.  This is the power disable.  We use this feature to slowly bring boards up in order to prevent damage during initial setup and programming.  With this jumper populated the power supplies will never release and will not ramp up to their programmed levels.

To correct this, you will need to REMOVE the jumper from JP3.

Another note regarding jumpers and power supplies.  JP1 and JP2 might not be connected either.  It is not stricktly necessary that they be connected.  These pins should be connected in order to allow the Programmable Logic (PL) pins access to the PMBUS SCL and SDA.  They are not necessary as the power regulators come pre-programmed from the factory and the PMBUS header is still connected to the power supply PMBUS pins.  If you DO need the PL pins to access this bus, feel free to connect both JP1 and JP2.

--Dan