Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Armbian_19.11.6_Nanopi-r1_buster_current_5.4.8.imgdoes not boot

Featured Replies

Hi, 

I am trying to boot image Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img, without success ...

First, i am using following line to create SD ...

ansible@solo:/mnt/backup$ sudo dd if=./Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img of=/dev/mmcblk0 bs=1M status=progress ;sudo sync

After connected my tty on internal pins on PCB, it is possible to connect to this tty and look at the first u-boot log ...

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on May  6 2018, 08:02:47.
Port /dev/tty-target-srv-nanopir1-170-position-1.2.4.1, 20:34:41

Press CTRL-A Z for help on special keys


U-Boot SPL 2019.10-armbian (Feb 17 2020 - 06:18:08 +0100)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2019.10-armbian (Feb 17 2020 - 06:18:08 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi R1
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7

Error: ethernet@1c30000 address not set.
eth-1: ethernet@1c30000
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
3789 bytes read in 3 ms (1.2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
236 bytes read in 3 ms (76.2 KiB/s)
7342788 bytes read in 557 ms (12.6 MiB/s)
7744344 bytes read in 587 ms (12.6 MiB/s)
Found mainline kernel configuration
29509 bytes read in 10 ms (2.8 MiB/s)
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo
502 bytes read in 7 ms (69.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-uart1.dtbo
4155 bytes read in 7 ms (579.1 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:    7342724 Bytes = 7 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 498ff000, end 49fffa84 ... OK
   Loading Device Tree to 4988f000, end 498fefff ... OK
Starting kernel ...

Uncompressing Linux... done, booting the kernel.


  
  

 

 

But not possible to have the login (!).

As a result, after umounting SD and modifying code in in /boot/armbianEnv.txt (verbosity=7), then following booting is always the same...

 

Regards

 

  • Author

Hi, 

Please find log file on nanopir1 and Armbian. Not possible for me to  boot the target with a tty connected on internal chip.

 

U-Boot SPL 2019.10-armbian (Jan 05 2020 - 01:28:29 +0100)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2019.10-armbian (Jan 05 2020 - 01:28:29 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi R1
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7

Error: ethernet@1c30000 address not set.
eth-1: ethernet@1c30000
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
3789 bytes read in 4 ms (924.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
236 bytes read in 3 ms (76.2 KiB/s)
7341915 bytes read in 552 ms (12.7 MiB/s)
7741936 bytes read in 582 ms (12.7 MiB/s)
Found mainline kernel configuration
29509 bytes read in 11 ms (2.6 MiB/s)
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo
502 bytes read in 10 ms (48.8 KiB/s)
Applying kernel provided DT overlay sun8i-h3-uart1.dtbo
4155 bytes read in 10 ms (405.3 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:    7341851 Bytes = 7 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 498ff000, end 49fff71b ... OK
   Loading Device Tree to 4988f000, end 498fefff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


  

Thanks in advance for your help ....

Best regards

  • Author

Igor, 

Thanks for your reply.

I have tested many releases from Armbian, always with the same CLASS 10 from SANDISK ultra. It seems there is no issue for this point of view.

 

Regards

  • Author
Quote

How long do you wait? There is also more recent image on the download. Did you try that too?

About 10 minutes (!)

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.