NanoPi NEO2 Black fresh install fails to boot properly


chippey5
 Share

0

Recommended Posts

I had a NanoPi NEO2 Black lying around with an old (but working) Armbian image on which I decided to wipe and re-flash. As per usual I check my DHCP server to see which IP it is assigned, but it never showed up. At this point I hooked up one of my UART adapters to it after re-flashing the image (Armbian_21.02.1_Nanopineo2black_buster_current_5.10.12.img): 

 

INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 23:47:50 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO Core 2
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 26 ms (8.5 MiB/s)
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
scanning bus usb@1c1b000 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
3173 bytes read in 4 ms (774.4 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
183 bytes read in 3 ms (59.6 KiB/s)
31278 bytes read in 10 ms (3 MiB/s)
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 7 ms (584 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10046824 bytes read in 488 ms (19.6 MiB/s)
21700616 bytes read in 1038 ms (19.9 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41710000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10046760 Bytes = 9.6 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 4966b000, end 49fffd28 ... OK
   Loading Device Tree to 00000000495fb000, end 000000004966afff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 43321/105664 files, 361761/421888 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 21.02.1 Buster!

[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on Journal Audit Socket.
         Starting Load Kernel Modules...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Reached target Swap.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Nameserver information manager...
         Mounting Huge Pages File System...
         Starting Create list of re&odes for the current kernel...
         Starting Restore / save the current clock...
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
         Mounting POSIX Message Queue File System...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Set up automount Arbitrary&s File System Automount Point.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on udev Control Socket.
         Mounting Kernel Debug File System...
[  OK  ] Started Forward Password R&uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
         Starting Set the console keyboard layout...
[  OK  ] Reached target Remote File Systems.
         Starting udev Coldplug all Devices...
[  OK  ] Started Load Kernel Modules.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Create list of req& nodes for the current kernel.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Nameserver information manager.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started Create System Users.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Armbian ZRAM config...
         Starting Set console font and keymap...
         Starting Mark the need to relabel after reboot...
         Starting Raise network interfaces...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Mark the need to relabel after reboot.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Found device /dev/ttyS1.

 

And then it just freezes. I reflashed it onto a new SD Card (SanDisk Ultra 16GB A1) and booted with the same behaviour as above:

 

NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 23:47:50 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO Core 2
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 13 ms (16.9 MiB/s)
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
scanning bus usb@1c1b000 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
3173 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
183 bytes read in 1 ms (178.7 KiB/s)
31278 bytes read in 6 ms (5 MiB/s)
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 4 ms (1022.5 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10046824 bytes read in 483 ms (19.8 MiB/s)
21700616 bytes read in 1035 ms (20 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41710000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10046760 Bytes = 9.6 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 4966b000, end 49fffd28 ... OK
   Loading Device Tree to 00000000495fb000, end 000000004966afff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: clean, 43327/105664 files, 361765/421888 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 21.02.1 Buster!

[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Set up automount Arbitrary&s File System Automount Point.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket.
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Starting Restore / save the current clock...
[  OK  ] Reached target Remote File Systems.
         Starting Set the console keyboard layout...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on udev Kernel Socket.
         Starting udev Coldplug all Devices...
         Starting Nameserver information manager...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
[  OK  ] Reached target Swap.
         Mounting Huge Pages File System...
[  OK  ] Started Forward Password R&uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
         Starting Create list of re&odes for the current kernel...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Create list of req& nodes for the current kernel.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Nameserver information manager.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Mounting Kernel Configuration File System...
         Starting Apply Kernel Variables...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Create System Users.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Set console font and keymap...
         Starting Mark the need to relabel after reboot...
         Starting Armbian ZRAM config...
         Starting Raise network interfaces...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Mark the need to relabel after reboot.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Found device /dev/ttyS1.

 

I'd be grateful for any help.

 

 

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

I'm using an identical 5V 2A adapter which is powering a secondary NanoPi NEO2 Black of mine (which is required according to the specs). I will try to swap out the cable and reply with the results. It's one I had lying around for a device whose charging input didn't exceed 500mA, but I do want to remember I used this one to set my boards up more than a year ago. 

 

Also just out of curiosity, are the logs at http://ix.io/2R3e generated through an actual NanoPi NEO2 Black?

Link to post
Share on other sites

7 minutes ago, chippey5 said:

Also just out of curiosity, are the logs at http://ix.io/2R3e generated through an actual NanoPi NEO2 Black?


Yes. Neo2 black is a part of a setup that is actively monitored on software upgrades. Test report looks like this https://users.armbian.com/igorp/2021-02-16_14.18.11.html But this testing facility is not near to the proffesional grade. To be sure, we would need much larger SBC farm ...

Link to post
Share on other sites

Just now, Igor said:


Yes. Neo2 black is a part of this setup and is actively monitored on software upgrades. Test report looks like this https://users.armbian.com/igorp/2021-02-16_14.18.11.html 

 

Impressive, thanks for this. I will check back with a reply once I have got a hold on a new micro usb cable and tested (which I currently don't have more of because luckily it's almost fully replaced by USB C nowadays :thumbup: ).

Link to post
Share on other sites

That didn't take long: I ripped out one of my Raspberry Pi 3 power supplies, connected it to the board and now it finally shows up in the network (and the heartbeat didn't stop). The funny thing is that the reason I wanted to reflash the board was because it was incredibly slow, probably caused by the quite extreme throttling that was happening at the time. Thanks for the stellar help! :D

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

0