Jump to content

Orange Pi Plus 2 (e?) - upgrade to "next" - failed

piknew

By piknew
in Allwinner sunxi

 Share

Recommended Posts

piknew

piknew

Posted
Posted

I am trying to switch legacy kernel to "next". I did it successfully with armbian-config for OrangePiPC (obviously Armbian was installed on SD card). Once I attempted to do the same with Orange Pi Plus and system installed onto internal EMMC then after reboot... nothing. I am wondering also if the issue is related to platform or the fact that Armbian was installed on EMMC.

 

I have connected TTL2USB and following is the result (seems to be indefinite loop):

  

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 141 ms (25.4 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
21 bytes read in 161 ms (0 Bytes/s)
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
4578312 bytes read in 446 ms (9.8 MiB/s)
6972808 bytes read in 526 ms (12.6 MiB/s)
Found mainline kernel configuration
33781 bytes read in 473 ms (69.3 KiB/s)
401 bytes read in 137 ms (2 KiB/s)
Applying user provided DT overlay ds1307.dtbo
** File not found /boot/dtb/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4578248 Bytes = 4.4 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 49ba2000, end 49fffbc8 ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 49b31000, end 49ba1fff ... OK

Starting kernel ...

Loading, please wait...
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: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument
[   44.940355] reboot: Restarting system

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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
mmc1(part 0) is current device

 

Link to comment
Share on other sites
  • piknew changed the title to Orange Pi Plus 2 (e?) - upgrade to "next" - failed
martinayotte

martinayotte

Posted
Posted
18 minutes ago, piknew said:

ALERT! /dev/mmcblk0p1 does not exist.

This /dev/mmcblk0p1 is for SDCard. Maybe somehow, either /boot/armbianEnv.txt or /etc/fstab didn't get updated properly with good root partition UUID or /dev/mmcblk1p1 during "nand-sata-install".

 

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted
1 minute ago, martinayotte said:

This /dev/mmcblk0p1 is for SDCard. Maybe somehow, either /boot/armbianEnv.txt or /etc/fstab didn't get updated properly with good root partition UUID or /dev/mmcblk1p1 during "nand-sata-install".

 

 

On legacy it was always first device - either SD or EMMC (if SD was not present).

 

And yes - my fstab was referring directly to /dev/mmcblk0p1. I have updated it to correct UUID=... but still the same.

 

BTW. My armbianEnv.txt is basically empty. It has only one line for DT user overlay (RTC).

 

Any more suggestions? Meanwhile I will try to dump my EMMC onto SD card and try to boot from it.

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted

If I remember, because my OPi+2E is currently unplugged in a box due to house moving, the eMMC was on /dev/mmcblk2.

Try to simply boot from SDCard, then look at the result of "ls -l /dev/mmcblk*", then mount the eMMC with "mount /dev/mmcblk2p1 /mnt" and verify /mnt/etc/fstab, not the one of the SDCard.

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted

So far tried:

 

1. dd - dump emmc to SD card and boot from SD card wich was 1:1 image of emmc - OK:

  

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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 149 ms (23.4 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
21 bytes read in 171 ms (0 Bytes/s)
4578312 bytes read in 459 ms (9.5 MiB/s)
6972808 bytes read in 537 ms (12.4 MiB/s)
Found mainline kernel configuration
33781 bytes read in 491 ms (66.4 KiB/s)
401 bytes read in 146 ms (2 KiB/s)
Applying user provided DT overlay ds1307.dtbo
** File not found /boot/dtb/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4578248 Bytes = 4.4 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 49ba2000, end 49fffbc8 ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 49b31000, end 49ba1fff ... OK

Starting kernel ...

Loading, please wait...
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.25.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 81229/918720 files, 466019/3781376 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 8 (jessie)!

         Expecting device dev-ttyS0.device...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Paths.
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on udev Control Socket.

 

2. When running from SD - as below. Seems to be exactly the same as on legacy.

  

root@PKBACKUP:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   0    4M  1 disk
mmcblk1      179:8    0 14.6G  0 disk
└─mmcblk1p1  179:9    0 14.4G  0 part
mmcblk1boot1 179:24   0    4M  1 disk
mmcblk0      179:0    0 14.9G  0 disk
└─mmcblk0p1  179:1    0 14.4G  0 part /
root@PKBACKUP:~#

 

3. When running from SD move armbian to EMMC by nand-sata-install. Boot from emmc (after message saying "now poweroff ...") - FAILED as before:

  

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 134 ms (26.4 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
21 bytes read in 154 ms (0 Bytes/s)
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
4578312 bytes read in 464 ms (9.4 MiB/s)
6972808 bytes read in 559 ms (11.9 MiB/s)
Found mainline kernel configuration
33781 bytes read in 645 ms (50.8 KiB/s)
401 bytes read in 188 ms (2 KiB/s)
Applying user provided DT overlay ds1307.dtbo
** File not found /boot/dtb/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4578248 Bytes = 4.4 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 49ba2000, end 49fffbc8 ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 49b31000, end 49ba1fff ... OK

Starting kernel ...

Loading, please wait...
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: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument
[   44.940297] reboot: Restarting system

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB

 

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted

As the output of #2 say, the eMMC is on mmcblk1p1 ...

You are not showing what is the content of /etc/fstab located in the eMMC !

As I've said, mount the eMMC with "mount /dev/mmcblk1p1 /mnt" and verify /mnt/etc/fstab, not the one of the SDCard.

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted
9 hours ago, martinayotte said:

As the output of #2 say, the eMMC is on mmcblk1p1 ...

You are not showing what is the content of /etc/fstab located in the eMMC !

As I've said, mount the eMMC with "mount /dev/mmcblk1p1 /mnt" and verify /mnt/etc/fstab, not the one of the SDCard.

 

How to say... when I am booting from SD then SD is mmcblk0 and EMMC is mmcblk1. When I am booting from EMMC then EMMC is mmcblk0 and SD is mmcblk1. In other words - booting device is always "0", the other one is "1". My lsblk command is an result when I booted from SD.

 

Contend of my fstab is:

 

root@PKSERVER:~# cat /etc/fstab
/dev/mmcblk0p1 / ext4 defaults,noatime,data=ordered,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
/var/swap none swap sw 0 0

 

And this fstab is working if i put the same image on SD or EMMC - because of the >> booting device is always "0" << rule. I mean... It was working for legacy, for mainline it is working only from SD.

 

In log file above this line is confirming that emmc is visible during boot - at this moment in device there is no SD card:

 

Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 134 ms (26.4 KiB/s) ## Executing script at 43100000

 

 

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
3 hours ago, piknew said:

When I am booting from EMMC then EMMC is mmcblk0 and SD is mmcblk1

How can you come to that conclusion ?

Well, I've found the box from my moving where the OPi+2E was stored...

Booting it was pretty old :

Linux orangepiplus2e 4.13.1-sunxi #11 SMP Mon Sep 11 18:50:26 EDT 2017 armv7l GNU/Linux

But I doubt the mmc* behavior changed since the. I will do a fresh build tomorrow and post it back ...

In the mean time, as I said twice, change your root to /dev/mmcblk1p1 ...

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted
8 hours ago, martinayotte said:

How can you come to that conclusion ?

 

On legacy when booted from EMMC (100% sure as SD card slot is emty) - either lsblk or mount or any command shows that rootfs is on /dev/mmcblk0p1 which emmc. In the same moment there is

 

I will do two things:

1. I will restore my legacy image to emmc to OPIPLus2, boot and show lsblk

2. I will restore the same image to SD and boot from it and show lsblk as well

3. I will restore my mainline image to emmc to OPIPLus2, boot - which will fail... I will mount emmc, change fstab/armbianEnv to point to mmcblk1. Try to boot.

4. I will restore my mainline image to SD, boot - this works. I will show lsblk.

 

I will gather as much data as possible.

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
2 hours ago, piknew said:

On legacy when booted from EMMC (100% sure as SD card slot is emty) - either lsblk or mount or any command shows that rootfs is on /dev/mmcblk0p1 which emmc.

This is NOT true anymore on Mainline ...

Link to comment
Share on other sites
chwe

chwe

Posted
Posted

as far as I understand look here: 

# get PARTUUID of first partition on SD/eMMC it was loaded from
# mmc 0 is always mapped to device u-boot (2016.09+) was loaded from
if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi

mmc 0 (mmcblk0p1) for u-boot depend from where your u-boot comes from.

 

On 5/25/2018 at 9:52 PM, piknew said:

CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment

if you have a valid bootloader on SD-Card things get messed up due to bootorder of the H3 SoC (SD-->eMMC and I think in the end SPI).  So, having a valid u-boot on SD-Card during boot might mess-up things...  Remove the SD-Card with a valid u-boot as soon as you run nand-sata-install and you should be fine. 

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted

First part of results as below. I have used the same image which was copied to SD and EMMC - in both cases I am able to boot the device.

 

1. SD_Legacy 

Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i
System load:   0.00 0.14 0.11   Up time:       6 min
Memory usage:  2 % of 2014MB    IP:            192.168.10.250
CPU temp:      45°C
Usage of /:    79% of 1.8G


root@PKTOOL:~# uname -a
Linux PKTOOL 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l GNU/Linux
root@PKTOOL:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:32   0    4M  1 disk
mmcblk1boot1 179:48   0    4M  1 disk
mmcblk0      179:0    0  1.9G  0 disk
└─mmcblk0p1  179:1    0  1.8G  0 part /
mmcblk1      179:16   0 14.6G  0 disk
└─mmcblk1p1  179:17   0  1.8G  0 part
root@PKTOOL:~# ll /dev/mmc*
brw-rw---- 1 root disk 179,  0 Jan  1  1970 /dev/mmcblk0
brw-rw---- 1 root disk 179,  1 Jan  1  1970 /dev/mmcblk0p1
brw-rw---- 1 root disk 179, 16 Jan  1  1970 /dev/mmcblk1
brw-rw---- 1 root disk 179, 48 Jan  1  1970 /dev/mmcblk1boot1
brw-rw---- 1 root disk 179, 32 Jan  1  1970 /dev/mmcblk1boot0
brw-rw---- 1 root disk 179, 17 Jan  1  1970 /dev/mmcblk1p1
root@PKTOOL:~# blkid /dev/mmcblk0
/dev/mmcblk0: PTUUID="278946fa" PTTYPE="dos"
root@PKTOOL:~# blkid /dev/mmcblk1
/dev/mmcblk1: PTUUID="278946fa" PTTYPE="dos"
root@PKTOOL:~# blkid /dev/mmcblk0p1
/dev/mmcblk0p1: UUID="f8301761-6756-4f97-aa80-12c05ea037cf" TYPE="ext4" PARTUUID="278946fa-01"
root@PKTOOL:~# blkid /dev/mmcblk1p1
/dev/mmcblk1p1: UUID="f8301761-6756-4f97-aa80-12c05ea037cf" TYPE="ext4" PARTUUID="278946fa-01"
root@PKTOOL:~#

 

2. EMMC_Legacy

  

Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i
System load:   0.84 0.19 0.06   Up time:       0 min
Memory usage:  3 % of 2014MB    IP:            192.168.10.250
CPU temp:      48°C
Usage of /:    79% of 1.8G


root@PKTOOL:~# uname -a
Linux PKTOOL 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l GNU/Linux
root@PKTOOL:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:16   0    4M  1 disk
mmcblk0boot1 179:32   0    4M  1 disk
mmcblk0      179:0    0 14.6G  0 disk
└─mmcblk0p1  179:1    0  1.8G  0 part /
root@PKTOOL:~# ll /dev/mmc*
brw-rw---- 1 root disk 179,  0 Jan  1  1970 /dev/mmcblk0
brw-rw---- 1 root disk 179,  1 Jan  1  1970 /dev/mmcblk0p1
brw-rw---- 1 root disk 179, 16 Jan  1  1970 /dev/mmcblk0boot0
brw-rw---- 1 root disk 179, 32 Jan  1  1970 /dev/mmcblk0boot1
root@PKTOOL:~# blkid /dev/mmcblk0
/dev/mmcblk0: PTUUID="278946fa" PTTYPE="dos"
root@PKTOOL:~#  blkid /dev/mmcblk1
root@PKTOOL:~# blkid /dev/mmcblk0p1
/dev/mmcblk0p1: UUID="f8301761-6756-4f97-aa80-12c05ea037cf" TYPE="ext4" PARTUUID="278946fa-01"
root@PKTOOL:~# blkid /dev/mmcblk1p1
root@PKTOOL:~#

 

Now I will boot by EMMC (I decided to use EMMC test first to avoid any impact from "upgrade of SD"), upgrade to mainline "next" (by armbian-config). Then boot and see results.

 

 

 

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted

3.1 EMMC_Mainline (with no armbianEnv.txt at all)

  


U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 149 ms (23.4 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
4578490 bytes read in 467 ms (9.3 MiB/s)
6972808 bytes read in 543 ms (12.2 MiB/s)
Found mainline kernel configuration
33781 bytes read in 491 ms (66.4 KiB/s)
** File not found /boot/dtb/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4578426 Bytes = 4.4 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 49ba2000, end 49fffc7a ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 49b31000, end 49ba1fff ... OK

Starting kernel ...

Loading, please wait...
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: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument

 

3.2 EMMC_Mainline (with mmcblk1) - SUCCESS!

 

U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 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
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 159 ms (22.5 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
85 bytes read in 225 ms (0 Bytes/s)
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
4578490 bytes read in 484 ms (9 MiB/s)
6972808 bytes read in 557 ms (11.9 MiB/s)
Found mainline kernel configuration
33781 bytes read in 523 ms (62.5 KiB/s)
** File not found /boot/overlay-user/ds1307.dtbo **
** File not found /boot/dtb/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4578426 Bytes = 4.4 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 49ba2000, end 49fffc7a ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 49b31000, end 49ba1fff ... OK

Starting kernel ...

Loading, please wait...
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.25.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1
/dev/mmcblk1p1: clean, 80126/118800 files, 403135/476928 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 8 (jessie)!

         Expecting device dev-ttyS0.device...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Paths.
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on Delayed Shutdown Socket.

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted

Conclusion and many thanks especially to martinayotte:

 

I must have explicit line in armbianEnv.txt:

 

root@PKTOOL:~# cat /boot/armbianEnv.txt
verbosity=0
rootdev=/dev/mmcblk1p1
user_overlays=ds1307
extraargs=pty.legacy_count=2
root@PKTOOL:~#

 

EDIT:

Both /etc/fstab and /boot/armbianEnv.txt was migrated to UUID, so my images are compatible again with both SD and EMMC.

 

Additionally there is suggestion - as I have upgraded from legacy I didn't have armbianEnv.txt file at all. armbian-config hasn't created any... So, content was only my "guessing". Maybe it will be worth to add ceration of such a file automatically? I guess it may be an issue with correct detection of boot device when still under "old kernel". This would be "would" prediction. So, maybe warning at the end...

 

EDIT: with UUID approach it would not be so difficult.

 

 

Many thanks to everybody. I have solved my problem :)

Link to comment
Share on other sites
piknew

piknew

Posted
  • Author
Posted

Just FYI - I have reverted to 3.4.113-sun8i on all my SBCs:

  • Orange Pi+ 2E
  • Orange Pi+ 2
  • Orange Pi PC
  • Orange Pi Zero (H2+/512)

The reason is here:

Thread in A20, but for me seems to happen on H2+/H3).

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept