# PYNQ-Z2 boards won't boot **URL:** \ **Category:** Support\ **Created:** [March 1, 2024, 6:51pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702 "2024-03-01T18:51:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ucd](https://avatars.discourse-cdn.com/v4/letter/u/97f17d/32.png) [@ucd](https://discuss.pynq.io/u/ucd)\ **Post date:** [March 1, 2024, 6:51pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702/1 "2024-03-01T18:51:34Z")
I have two Pynq-Z2 boards. Neither will boot. One gives no message at all when booted and the other gives a normal boot log until it suddenly resets: > U-Boot 2022.01 (Apr 04 2022 - 07:53:54 +0000) > > CPU: Zynq 7z020 > Silicon: v3.1 > DRAM: ECC disabled 512 MiB > Flash: 0 Bytes > NAND: 0 MiB > MMC: mmc@e0100000: 0 > Loading Environment from FAT… \*\*\* Error - No Valid Environment Area found > \*\*\* Warning - bad env area, using default environment > > In: serial@e0000000 > Out: serial@e0000000 > Err: serial@e0000000 > Net: > ZYNQ GEM: e000b000, mdio bus e000b000, phyaddr -1, interface rgmii-id > SF: Detected s25fl128s with page size 256 Bytes, erase size 64 KiB, total 16 MiB > eth0: ethernet@e000b000 > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:1… > Found U-Boot script /boot.scr > 2776 bytes read in 10 ms (270.5 KiB/s) > > ## Executing script at 03000000 > > Trying to load boot images from mmc0 > 6464328 bytes read in 366 ms (16.8 MiB/s) > > ## Loading kernel from FIT Image at 10000000 … > > Using ‘conf-1’ configuration > Verifying Hash Integrity … OK > Trying ‘kernel-0’ kernel subimage > Description: Linux Kernel > Type: Kernel Image > Compression: uncompressed > Data Start: 0x100000d4 > Data Size: 6442720 Bytes = 6.1 MiB > Architecture: ARM > OS: Linux > Load Address: 0x00080000 > Entry Point: 0x00080000 > Hash algo: sha1 > Hash value: b056acb229d05b806f975396dacae4ad04002e0c > Verifying Hash Integrity … sha1+ OK > > ## Loading fdt from FIT Image at 10000000 … > > Using ‘conf-1’ configuration > Verifying Hash Integrity … OK > Trying ‘fdt-0’ fdt subimage > Description: Flattened Device Tree blob > Type: Flat Device Tree > Compression: uncompressed > Data Start: 0x106250a8 > Data Size: 19792 Bytes = 19.3 KiB > Architecture: ARM > Hash algo: sha1 > Hash value: c20e513daf724f7b1b134fa9af089b026612751e > Verifying Hash Integrity … sha1+ OK > Booting using the fdt blob at 0x106250a8 > Loading Kernel Image > Loading Device Tree to 1ead4000, end 1eadbd4f … OK > > Starting kernel … > > Booting Linux on physical CPU 0x0 > Linux version 5.15.19-xilinx-v2022.1 (oe-user@oe-host) (arm-xilinx-linux-gnueabi-gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37.20210721) #1 SMP PREEMPT Mon Apr 11 17:52:14 UTC 2022 > CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d > CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > OF: fdt: Machine model: xlnx,zynq-7000 > Memory policy: Data cache writealloc > cma: Reserved 128 MiB at 0x16800000 > Zone ranges: > Normal [mem 0x0000000000000000-0x000000001fffffff] > HighMem empty > Movable zone start for each node > Early memory node ranges > node 0: [mem 0x0000000000000000-0x000000001fffffff] > Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff] > percpu: Embedded 12 pages/cpu s18828 r8192 d22132 u49152 > Built 1 zonelists, mobility grouping on. Total pages: 129920 > Kernel command line: root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait devtmpfs.mount=1 uio\_pdrv\_genirq.of\_id=“generic-uio” clk\_ignore\_unused > Unknown kernel command line parameters “earlyprintk”, will be passed to user space. > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) > mem auto-init: stack:off, heap alloc:off, heap free:off > Memory: 373332K/524288K available (9216K kernel code, 324K rwdata, 2512K rodata, 1024K init, 296K bss, 19884K reserved, 131072K cma-reserved, 0K highmem) > rcu: Preemptible hierarchical RCU implementation. > rcu: RCU event tracing is enabled. > rcu: RCU restricting CPUs from NR\_CPUS=4 to nr\_cpu\_ids=2. > Trampoline variant of Tasks RCU enabled. > Tracing variant of Tasks RCU enabled. > rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. > rcu: Adjusting geometry for rcu\_fanout\_leaf=16, nr\_cpu\_ids=2 > NR\_IRQS: 16, nr\_irqs: 16, preallocated irqs: 16 > efuse mapped to (ptrval) > slcr mapped to (ptrval) > GIC physical location is 0xf8f01000 > L2C: platform modifies aux control register: 0x72360000 → 0x72760000 > L2C: DT/platform modifies aux control register: 0x72360000 → 0x72760000 > 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 ID prefetch enabled, offset 1 lines > L2C-310 dynamic clock gating enabled, standby mode enabled > L2C-310 cache controller enabled, 8 ways, 512 kB > L2C-310: CACHE\_ID 0x410000c8, AUX\_CTRL 0x76760001 > random: get\_random\_bytes called from start\_kernel+0x364/0x5f8 with crng\_init=0 > zynq\_clock\_init: clkc starts at (ptrval) > Zynq clock init > sched\_clock: 64 bits at 162MHz, resolution 6ns, wraps every 4398046511101ns > clocksource: arm\_global\_timer: mask: 0xffffffffffffffff max\_cycles: 0x257a3bfb55, max\_idle\_ns: 440795207830 ns > Switching to timer-based delay loop, resolution 6ns > Console: colour dummy device 80x30 > printk: console [tty0] enabled > Calibrating delay loop (skipped), value calculated using timer frequency… 325.00 BogoMIPS (lpj=1625000) > pid\_max: default: 32768 minimum: 301 > Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) > Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) > CPU: Testing write buffer coherency: ok > CPU0: Spectre v2: using BPIALL workaround > CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 > Setting up static identity map for 0x100000 - 0x100060 > rcu: Hierarchical SRCU implementation. > smp: Bringing up secondary CPUs … > CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 > CPU1: Spectre v2: using BPIALL workaround > smp: Brought up 1 node, 2 CPUs > SMP: Total of 2 processors activated (650.00 BogoMIPS). > CPU: All CPU(s) started in SVC mode. > devtmpfs: initialized > VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 > clocksource: jiffies: mask: 0xffffffff max\_cycles: 0xffffffff, max\_idle\_ns: 19112604462750000 ns > futex hash table entries: 512 (order: 3, 32768 bytes, linear) > pinctrl core: initialized pinctrl subsystem > NET: Registered PF\_NETLINK/PF\_ROUTE protocol family > DMA: preallocated 256 KiB pool for atomic coherent allocations > thermal\_sys: Registered thermal governor ‘step\_wise’ > cpuidle: using governor menu > amba f8801000.etb: Fixing up cyclic dependency with replicator > amba f8803000.tpiu: Fixing up cyclic dependency with replicator > amba f8804000.funnel: Fixing up cyclic dependency with replicator > amba f889c000.ptm: Fixing up cyclic dependency with f8804000.funnel > amba f889d000.ptm: Fixing up cyclic dependency with f8804000.funnel > hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. > hw-breakpoint: maximum watchpoint size is 4 bytes. > zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x(ptrval) > e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 34, base\_baud = 6250000) is a xuartps > printk: console [ttyPS0] enabled > raid6: int32x8 gen() 117 MB/s > raid6: int32x8 xor() 78 MB/s > raid6: int32x4 gen() 125 MB/s > raid6: int32x4 xor() 87 MB/s > raid6: int32x2 gen() 200 MB/s > raid6: int32x2 xor() 125 MB/s > raid6: int32x1 gen() 180 MB/s > raid6: int32x1 xor() 100 MB/s > raid6: using algorithm int32x2 gen() 200 MB/s > raid6: … xor() 125 MB/s, rmw enabled > raid6: using intx1 recovery algorithm > vgaarb: loaded > SCSI subsystem initialized > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > mc: Linux media interface: v0.10 > videodev: Linux video capture interface: v2.00 > pps\_core: LinuxPPS API ver. 1 registered > pps\_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [giometti@linux.it](mailto:giometti@linux.it) > PTP clock support registered > EDAC MC: Ver: 3.0.0 > FPGA manager framework > Advanced Linux Sound Architecture Driver Initialized. > clocksource: Switched to clocksource arm\_global\_timer > NET: Registered PF\_INET protocol family > IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear) > tcp\_listen\_portaddr\_hash hash table entries: 512 (order: 0, 6144 bytes, linear) > TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear) > TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear) > TCP: Hash tables configured (established 4096 bind 4096) > UDP hash table entries: 256 (order: 1, 8192 bytes, linear) > UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear) > NET: Registered PF\_UNIX/PF\_LOCAL protocol family > RPC: Registered named UNIX socket transport module. > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > RPC: Registered tcp NFSv4.1 backchannel transport module. > PCI: CLS 0 bytes, default 64 > armv7-pmu f8891000.pmu: hw perfevents: no interrupt-affinity property, guessing. > hw perfevents: enabled with armv7\_cortex\_a9 PMU driver, 7 counters available > Initialise system trusted keyrings > workingset: timestamp\_bits=14 max\_order=17 bucket\_order=3 > squashfs: version 4.0 (2009/01/31) Phillip Lougher > jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. > xor: measuring software checksum speed > arm4regs : 1045 MB/sec > 8regs : 805 MB/sec > 32regs : 836 MB/sec > xor: using function: arm4regs (1045 MB/sec) > Key type asymmetric registered > Asymmetric key parser ‘x509’ registered > io scheduler mq-deadline registered > io scheduler kyber registered > zynq-pinctrl 700.pinctrl: zynq pinctrl initialized > dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330 > dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num\_Chans-8 Num\_Peri-4 Num\_Events-16 > brd: module loaded > loop: module loaded > spi\_master spi0: cannot find modalias for /axi/spi@e000d000/flash@0 > spi\_master spi0: Failed to create SPI device for /axi/spi@e000d000/flash@0 > tun: Universal TUN/TAP device driver, 1.6 > CAN device driver interface > macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 36 (00:00:05:6b:03:a8) > e1000e: Intel(R) PRO/1000 Network Driver > e1000e: Copyright(c) 1999 - 2015 Intel Corporation. > ehci\_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver > ehci-pci: EHCI PCI platform driver > usbcore: registered new interface driver cdc\_acm > cdc\_acm: USB Abstract Control Model driver for USB modems and ISDN adapters > usbcore: registered new interface driver cdc\_wdm > usbcore: registered new interface driver usb-storage > usbcore: registered new interface driver usbserial\_generic > usbserial: USB Serial support registered for generic > usbcore: registered new interface driver usb\_serial\_simple > usbserial: USB Serial support registered for carelink > usbserial: USB Serial support registered for zio > usbserial: USB Serial support registered for funsoft > usbserial: USB Serial support registered for flashloader > usbserial: USB Serial support registered for google > usbserial: USB Serial support registered for libtransistor > usbserial: USB Serial support registered for vivopay > usbserial: USB Serial support registered for moto\_modem > usbserial: USB Serial support registered for motorola\_tetra > usbserial: USB Serial support registered for novatel\_gps > usbserial: USB Serial support registered for hp4x > usbserial: USB Serial support registered for suunto > usbserial: USB Serial support registered for siemens\_mpi > ULPI transceiver vendor/product ID 0x0451/0x1507 > Found TI TUSB1210 ULPI transceiver. > ULPI integrity check: passed. > ci\_hdrc ci\_hdrc.0: EHCI Host Controller > ci\_hdrc ci\_hdrc.0: new USB bus registered, assigned bus number 1 > ci\_hdrc ci\_hdrc.0: USB 2.0 started, EHCI 1.00 > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 1 port detected Then, rather than the next line (“i2c\_dev: i2c /dev entries driver” on a good device), the boot process starts over again. I’ve tried swapping the SD cards between a good device and the bad devices and all three SD cards work on the good device and not on the bad devices. I suspect this is a hardware issue, but I wanted to see if anyone has any other debugging ideas. ---
**Author:** ![cathalmccabe](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/cathalmccabe/32/3348_2.png) [@cathalmccabe](https://discuss.pynq.io/u/cathalmccabe)\ **Post date:** [March 5, 2024, 4:28pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702/2 "2024-03-05T16:28:32Z")
I’m not sure about the board that is not booting at all. It does sound like a hardware issue. Do you see any LEDS? You could try to conenct to Vivado and see if you can connect to the board at all. Mainly for the second board where the boot fails; Does it consistently fail at exactly the same point? The partial boot process indicates the board is mostly functional. Are you powering the board from a USB port on your PC or laptop? Some USB ports can’t provide sufficient power (especially laptop ports in a low power mode) Try connect the it to a USB plug. This will prevent you from seeing the UART output but it should indicate if the board boots. Do you have more boards that are working properly? Cathal ---
**Author:** ![ucd](https://avatars.discourse-cdn.com/v4/letter/u/97f17d/32.png) [@ucd](https://discuss.pynq.io/u/ucd)\ **Post date:** [March 5, 2024, 9:03pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702/3 "2024-03-05T21:03:41Z")
The CR8 led lights up (in both cases). The second board consistently fails at the same place. I have several boards that are working properly, with the same SD card and plugged into the same USB port. ---
**Author:** ![canalta](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@canalta](https://discuss.pynq.io/u/canalta)\ **Post date:** [March 15, 2024, 3:34pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702/4 "2024-03-15T15:34:08Z")
I’ve recently encountered two boards that can’t seem to boot from the SD card either. The SD cards work in other boards that boot fine, but these two boards don’t even show anything when connecting to them via UART. Any tips on how to further diagnose the board? ---
**Author:** ![cathalmccabe](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/cathalmccabe/32/3348_2.png) [@cathalmccabe](https://discuss.pynq.io/u/cathalmccabe)\ **Post date:** [March 15, 2024, 4:28pm UTC](https://discuss.pynq.io/t/pynq-z2-boards-wont-boot/6702/5 "2024-03-15T16:28:32Z")
I’d suggest you try to contact the vendor. Cathal