1 1
paolobasile

Armbian Debian Orange pi Zero plus 2 fail

Recommended Posts

There are no problems with our images. Double checked.
 

Spoiler

INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:05:45)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000)
NOTICE:  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):aa75c8d
NOTICE:  BL3-1: Built : 08:05:40, Jan 25 2018
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9


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

CPU:   Allwinner H5 (SUN50I)
Model: OrangePi Zero Plus2
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
No controllers 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
3100 bytes read in 194 ms (14.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
192 bytes read in 155 ms (1000 Bytes/s)
29656 bytes read in 315 ms (91.8 KiB/s)
504 bytes read in 535 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
504 bytes read in 544 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo
4179 bytes read in 412 ms (9.8 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 44000000
5422766 bytes read in 533 ms (9.7 MiB/s)
12943368 bytes read in 893 ms (13.8 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    5422702 Bytes = 5.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49ad4000, end 49fffe6e ... OK
   reserving fdt memory region: addr=4fa00000 size=6d000
   Loading Device Tree to 0000000049a64000, end 0000000049ad3fff ... OK
Cannot setup simplefb: node not found

Starting kernel ...

Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 
/dev/mmcblk0p1: clean, 36030/942112 files, 366140/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 16.04.3 LTS!

[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[  OK  ] Created slice System Slice.
         Starting Restore / save the current clock...
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
[  OK  ] Reached target Slices.
         Starting Nameserver information manager...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Create list of required st... nodes for the current kernel...
         Starting Load Kernel Modules...
         Mounting Debug File System...
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Started Trigger resolvconf update for networkd DNS.
         Starting Remount Root and Kernel File Systems...
         Starting Set console keymap...
[  OK  ] Reached target Swap.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started Set console keymap.
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Mounting Configuration File System...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Reached target Local File Systems.
         Starting Armbian enhanced Log2Ram...
         Starting Set console font and keymap...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Started Armbian enhanced Log2Ram.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[  OK  ] Started Set console font and keymap.
[  OK  ] Created slice system-getty.slice.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Reached target System Time Synchronized.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting Initializes zram swaping...
         Starting LSB: Start/stop sysstat's sadc...
[  OK  ] Started Regular background program processing daemon.
         Starting System Logging Service...
         Starting LSB: Armbian gathering hardware information...
[  OK  ] Reached target Network (Pre).
         Starting Raise network interfaces...
         Starting LSB: Patch firmware for ap6212 adapter...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Daily Cleanup of Temporary Directories.
         Starting Permit User Sessions...
         Starting Login Service...
[  OK  ] Started System Logging Service.
[  OK  ] Started Initializes zram swaping.
[  OK  ] Started LSB: Patch firmware for ap6212 adapter.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
         Starting Set console scheme...
[  OK  ] Started Login Service.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started Set console scheme.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Started Raise network interfaces.
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
         Starting Hostname Service...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Hostname Service.
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Starting WPA supplicant...
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting LSB: Start NTP daemon...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting LSB: disk temperature monitoring daemon...
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
         Starting /etc/rc.local Compatibility...
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Serial Getty on ttyGS0.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04.3 LTS orangepizeroplus2 ttyS0

orangepizeroplus2 login: 

 

 


Make sure you read this and act accordingly. (throw away your PSU, cable or both)

Share this post


Link to post
Share on other sites
27 minutes ago, Igor said:

There are no problems with our images. Double checked.
 

  Reveal hidden contents


INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:05:45)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000)
NOTICE:  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):aa75c8d
NOTICE:  BL3-1: Built : 08:05:40, Jan 25 2018
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9


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

CPU:   Allwinner H5 (SUN50I)
Model: OrangePi Zero Plus2
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
No controllers 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
3100 bytes read in 194 ms (14.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
192 bytes read in 155 ms (1000 Bytes/s)
29656 bytes read in 315 ms (91.8 KiB/s)
504 bytes read in 535 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
504 bytes read in 544 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo
4179 bytes read in 412 ms (9.8 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 44000000
5422766 bytes read in 533 ms (9.7 MiB/s)
12943368 bytes read in 893 ms (13.8 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    5422702 Bytes = 5.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49ad4000, end 49fffe6e ... OK
   reserving fdt memory region: addr=4fa00000 size=6d000
   Loading Device Tree to 0000000049a64000, end 0000000049ad3fff ... OK
Cannot setup simplefb: node not found

Starting kernel ...

Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 
/dev/mmcblk0p1: clean, 36030/942112 files, 366140/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 16.04.3 LTS!

[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[  OK  ] Created slice System Slice.
         Starting Restore / save the current clock...
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
[  OK  ] Reached target Slices.
         Starting Nameserver information manager...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Create list of required st... nodes for the current kernel...
         Starting Load Kernel Modules...
         Mounting Debug File System...
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Started Trigger resolvconf update for networkd DNS.
         Starting Remount Root and Kernel File Systems...
         Starting Set console keymap...
[  OK  ] Reached target Swap.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started Set console keymap.
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Mounting Configuration File System...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Reached target Local File Systems.
         Starting Armbian enhanced Log2Ram...
         Starting Set console font and keymap...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Started Armbian enhanced Log2Ram.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[  OK  ] Started Set console font and keymap.
[  OK  ] Created slice system-getty.slice.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Reached target System Time Synchronized.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting Initializes zram swaping...
         Starting LSB: Start/stop sysstat's sadc...
[  OK  ] Started Regular background program processing daemon.
         Starting System Logging Service...
         Starting LSB: Armbian gathering hardware information...
[  OK  ] Reached target Network (Pre).
         Starting Raise network interfaces...
         Starting LSB: Patch firmware for ap6212 adapter...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Daily Cleanup of Temporary Directories.
         Starting Permit User Sessions...
         Starting Login Service...
[  OK  ] Started System Logging Service.
[  OK  ] Started Initializes zram swaping.
[  OK  ] Started LSB: Patch firmware for ap6212 adapter.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
         Starting Set console scheme...
[  OK  ] Started Login Service.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started Set console scheme.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Started Raise network interfaces.
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
         Starting Hostname Service...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Hostname Service.
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Starting WPA supplicant...
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting LSB: Start NTP daemon...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting LSB: disk temperature monitoring daemon...
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
         Starting /etc/rc.local Compatibility...
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Serial Getty on ttyGS0.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04.3 LTS orangepizeroplus2 ttyS0

orangepizeroplus2 login: 

 

 


Make sure you read this and act accordingly. (throw away your PSU, cable or both)

 

I use this adapter.

 

https://www.amazon.es/gp/product/B01DDFFOYK/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1

Share this post


Link to post
Share on other sites
5 minutes ago, paolobasile said:

I use this adapter.


Nobody can't tell you if it is good (measure voltage on the board). Just get some other one, change everything but the board. Check also Ubuntu image, which is the one I used for testing - if you haven't already.

Share this post


Link to post
Share on other sites
28 minutes ago, Igor said:


Nobody can't tell you if it is good (measure voltage on the board). Just get some other one, change everything but the board. Check also Ubuntu image, which is the one I used for testing - if you haven't already.

I have tried with 3 different cards, all of them samsung, with the versions of ubuntu and debian and with 3 chargers that work with 3 raspberrys pi 3

 

 

The problem does not seem to be voltage or intensity

Share this post


Link to post
Share on other sites

I made another test with a different image, different SD card, with a serial console attached and without. No problems. 

It could be (partially) broken board, lower quality memory chips ... in this case you need to build your own u-boot with lower dram settings. Unlikely, but possible.

Share this post


Link to post
Share on other sites
5 hours ago, Xalius said:

Does it also crash if you connect the display after booting?


Mine 1080p display doesn't cause any problems if attached when the machine is up.

[   24.075231] Console: switching to colour frame buffer device 240x67
[   24.108325] sun4i-drm display-engine: fb0:  frame buffer device

 

Share this post


Link to post
Share on other sites
23 hours ago, paolobasile said:

 

I download the image of this page, unzip the image and use rufus to burn it in a Samsung SD 32 GB evo. I use power supply of 3000 mah
https://www.armbian.com/orange-pi-zero-2-h5/
It always fails, and it starts a reboot and kernel panic cycle

What image i need use?

 

I would use one of these two images (if you like debian or ubuntu - its your decision):
https://dl.armbian.com/orangepizeroplus2-h5/archive/Armbian_5.38_Orangepizeroplus2-h5_Debian_stretch_next_4.14.14.7z

https://dl.armbian.com/orangepizeroplus2-h5/archive/Armbian_5.38_Orangepizeroplus2-h5_Ubuntu_xenial_next_4.14.14.7z

 

And for writting the image please use

- etcher ( https://etcher.io/ )

- win32diskimager ( https://sourceforge.net/projects/win32diskimager/files/latest/download )

or

- USB-IT ( http://www.alexpage.de/usb-image-tool/ )   (edited by @chwe

 

Edited by chwe
we only suggest etcher for writting images... :)

Share this post


Link to post
Share on other sites
On 1/3/2018 at 10:32 AM, guidol said:

 

I have used both versions but none works. The image message appears but stays black. It is important to say that if I do not introduce any SD card, the board starts Android (from emmc memory) How can I format that memory completely? I think it's the problem I can use an ubuntu version that works from the orange page

 

 

oNTXhI4.jpg

Share this post


Link to post
Share on other sites
6 hours ago, paolobasile said:

I have used both versions but none works. The image message appears but stays black. It is important to say that if I do not introduce any SD card, the board starts Android (from emmc memory) How can I format that memory completely? I think it's the problem I can use an ubuntu version that works from the orange page


If you can't boot our images from SD card but you can stock, then this might be the problem:
https://forum.armbian.com/topic/3945-mmc-no-card-present-error-on-allwinner-boards/


But if you can and, here above is a screen of the boot, then some other problem might be present. Can you check serial console output?

Share this post


Link to post
Share on other sites
5 hours ago, Igor said:


If you can't boot our images from SD card but you can stock, then this might be the problem:
https://forum.armbian.com/topic/3945-mmc-no-card-present-error-on-allwinner-boards/


But if you can and, here above is a screen of the boot, then some other problem might be present. Can you check serial console output?

I've only been able to start an Ubuntu distribution, of all the ones I've tried, a version manipulated and prepared by Orange pi. In it, from the command console I could see the status of the nand memory.

Share this post


Link to post
Share on other sites

Most likely yours SD card slot is slightly broken. Read posted link again. It cointains hints how to solve this problem. Worse case you need to replace SD card slot.

Wrote on mobile

Share this post


Link to post
Share on other sites

Nand (EMMC) has no role in this problem. Just insert and remove SD card 20-40 times ... this usually helps. Stock OS does not check (this sensor) if SD card is present, others do.

Wrote on mobile

Share this post


Link to post
Share on other sites
10 hours ago, Igor said:

Nand (EMMC) no tiene ningún papel en este problema. Simplemente inserte y extraiga la tarjeta SD 20-40 veces ... esto generalmente ayuda. Stock OS no verifica (este sensor) si la tarjeta SD está presente, otros sí.

Escribió en el móvil
 

I have removed and inserted the card 100 times, but it still fails.

It is a pity, but I give for lost the OPZ.

Share this post


Link to post
Share on other sites

all firmware for Orange pi Zero plus 2 (H5)  - do not start.

loading stops as b on the photo of 

On 13.03.2018 at 01:32, paolobasile said:

 

Я использовал обе версии, но никто не работает. Изображение появляется, но остается черным. Важно сказать, что если я не буду вводить какую-либо SD-карту, плата начнет Android (из памяти emmc). Как я могу полностью отформатировать эту память? Я думаю, что это проблема, я могу использовать версию ubuntu, которая работает с оранжевой страницы

 

 

oNTXhI4.jpg

after that the screen turns blue, and the download stops

 

debian , ubuntu , dietpi - are working

But they can not be transferred to EMMC

Share this post


Link to post
Share on other sites
50 minutes ago, Anatolii Kraskovskiy said:

loading stops as b on the photo of 


that is normal ... how long did you wait? do you have a serial console perhaps to see what's going on there?

Share this post


Link to post
Share on other sites
6 minutes ago, Anatolii Kraskovskiy said:

no control, waiting for up to 3 minutes


If you have some bad SD card 3 minutes might not be enough ... 

 

1 hour ago, Anatolii Kraskovskiy said:

debian , ubuntu , dietpi - are working


Under the same condition? Same SD card and power supply? Are you sure?

Share this post


Link to post
Share on other sites

All the firmware that I found on the Internet for Orange pi Zero plus 2, except Armbian, - work. Posted on the site Armbian for Orange pi Zero plus 2, neither the server nor the desktop - do not load, just start as in the photo and then the blue screen. Previously, the firmwares were laid out old, nightly, now this is not (or I do not know how to see them), this is bad

Share this post


Link to post
Share on other sites
9 minutes ago, Anatolii Kraskovskiy said:

this is bad


Images are tested and they work. All H5 images/kernels are still marked as development/testing. For a reason. Most of the other images use stock Allwinner u-boot/kernel which has it own bugs, except Dietpi, which used to use our image + their Debian cripling script on the top. Now they dropped "support" since they only create BASH scripts ... Since you don't provide any exact data and think it is all our fault, we can't help. I am out of office and can't help much anyway. 


We need serial console boot logs to debug. (or change console to tty1 and alter verbosity to 10)

Share this post


Link to post
Share on other sites

Толян, у меня такая же плата. Несколько дней назад ставил последний доступный образ, все работало и до сих пор работает. Может действительно с uart адаптером запустить и посмотреть где спотыкается?

-------------------

@Anatolii Kraskovskiy, i have same board. Few days it works with last image. May be uart adapter show more information?

Share this post


Link to post
Share on other sites
3 minutes ago, rusatch said:

Толян, у меня такая же плата. Несколько дней назад ставил последний доступный образ, все работало и до сих пор работает.

-------------------

@Анатолий Красковский, у меня такая же доска. Несколько дней он работает с последним изображением.

put the image of the card, I'll try, it can work

Share this post


Link to post
Share on other sites
18 minutes ago, Anatolii Kraskovskiy said:

Dietpi works

Dietpi is a bash script (that break Debian into something strange) on top of Armbian. It's our kernel and our u-boot but without end user support. They don't add nor change anything in this regard. That's why this is strange and I want to know why it is not working ... serial console cost 2USD shipped and saves a lot. We both could do something else at this moment.


At least edit card on some linux and change verbosity to 10 and console=display in /boot/armbianEnv.txt, save, boot and make a picture where it hangs.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1