Hello.

 

I'v recently tried to update by old orange pi zero to latest armbian and it does not boot. Serial console is dead silent. 

I'v tried different armbian releases, sdcards, but result is the same.

However card with old boots perfectly fine. Image orangepizerolts also works, but it has huge overheating problem.

 

I'v tried to flash uboot to spi, but it does not boot either. Sadly old uboot did not worked with latest armbian.

 

Any idea?

 

Which exact image are you trying to boot?

Tried 22.05 Bullseye and Jammy and few older images: 20.05, 20.11 and Armbian 4.90 with kernel 4.19. On all images result is same, console is totaly silent.

Cannot reproduce. Armbian_22.05.4_Orangepizero_bullseye_current_5.15.48.img booting perfectly fine on my OPi0 v1.1 w/ 32GB Sandisk Extreme U3 A1

Same situation here. Updated to jammy => Orange Pi zero 1 does not boot anymore.

The serial port definitely gives an echo (local echo is deactivated) and runs at 115200 - but

nothing else happens.

 

 

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:04:30)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2017.11-armbian (Jan 25 2018 - 08:04:30 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 197 ms (17.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
278 bytes read in 149 ms (1000 Bytes/s)
9290667 bytes read in 1014 ms (8.7 MiB/s)
6972808 bytes read in 788 ms (8.4 MiB/s)
Found mainline kernel configuration
31935 bytes read in 787 ms (39.1 KiB/s)
339 bytes read in 862 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-analog-codec.dtbo
382 bytes read in 286 ms (1000 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-cir.dtbo
374 bytes read in 620 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-i2c0.dtbo
374 bytes read in 869 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-i2c1.dtbo
374 bytes read in 720 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-i2c2.dtbo
780 bytes read in 784 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo
506 bytes read in 745 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-uart1.dtbo
506 bytes read in 427 ms (1000 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-uart2.dtbo
506 bytes read in 277 ms (1000 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-uart3.dtbo
504 bytes read in 389 ms (1000 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo
504 bytes read in 496 ms (1000 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo
504 bytes read in 703 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 796 ms (0 Bytes/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
799 bytes read in 325 ms (2 KiB/s)
Applying kernel provided DT overlay sun8i-h3-w1-gpio.dtbo
4179 bytes read in 810 ms (4.9 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9290603 Bytes = 8.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49723000, end 49fff36b ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 496b2000, end 49722fff ... OK

Starting kernel ...

 

7 hours ago, ckahlo said:

Same situation here. Updated to jammy

Does fresh image from download section works for you?