[Solved] 2x Orange Pi 4Bs - one can boot armbian one can't

patrix · Published in 2020-7-11 19:35:05

Edited by patrix at 2020-7-12 11:24

Solved: I ended up dumping the image of the working unit's emmc with dd, and dd'ing that to the other unit's emmc, now I can boot Armbian again!

I have 2 Orange Pi 4B, and they are not behaving the same. Now I'm pretty sure that is my fault, however I am seeking some pointers in order to help solve this. Unit A is the problematic one, Unit B is the normal one.

Unit A:
- When I first got it, eMMC came with Android. I tried various Orange Pi Ubuntu and Armbian images, booting from sdcard, also Orange Pi's Android image booting from SD
- At some point I installed Armbian to the eMMC using nand_sata_install, and that was working fine as well
- Not sure what I did after that, I think I booted from SD and used dd to flash an image to the eMMC, and since that time:

- I can boot Orange Pi's Ubuntu Bionic image v 1.2 or v1.3 from the micro SD card

- I can install Orange Pi Ubuntu Bionic Image to the eMMC using install_to_emmc script, and boot successfully from eMMC
- However when micro SD card is inserted, it boots from SD instead of eMMC

eMMC appears as: /dev/mmcblk1
sdcard appears as: /dev/mmcblk0

Unit B:
- boots any image from sdcard, Armbian, Android or Orange Pi's images

eMMC appears as: /dev/mmcblk2
sdcard apepars as: /dev/mmcblk1

I would like to be able to boot Armbian or Android once more on Unit A.. Any pointers appreciated.

Pat.

patrix · Published in 2020-7-12 11:23:56

What I ended up doing:

- dd the emmc of Unit B to an image file
- dd that image file to the emmc of Unit A

Now I can boot Armbian!

patrix · Published in 2020-7-11 20:27:48

Below are serial outputs when (1) booting OPi Ubuntu, (2) trying to boot Armbian.

Based on errors, I tried the solution here:

https://forum.armbian.com/topic/ ... t&comment=94140

dd if=/dev/zero of=/dev/mmcblk1 bs=1M seek=14900

To no avail.. Troubleshooting continues

Serial output when booting the Orange Pi Ubuntu:

DDR Version 1.22 20190506
In
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 0, cs 1, advanced training done
channel 1, cs 0, advanced training done
channel 1, cs 1, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67892
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part: 0, name: uboot, start:0x6000, size:0x2000
GPT part: 1, name: trust, start:0x8000, size:0x2000
GPT part: 2, name: boot, start:0xc000, size:0x10000
GPT part: 3, name: rootfs, start:0x5c000, size:0x1cc2fdf
find part:uboot OK. first_lba:0x6000.
find part:trust OK. first_lba:0x8000.
LoadTrust Addr:0x8000
No find bl30.bin
Load uboot, ReadLba = 6000
Load OK, addr=0x200000, size=0xe025c
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):51f2096
NOTICE: BL31: Built : 16:24:31, May 6 2019
NOTICE: BL31: Rockchip release version: v1.1
INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: plat_rockchip_pmu_init(1181): pd status 3e
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-221-gda2bcfdc #139 Mon Jun 17 03:14:33 UTC 2019 aarch64)
INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2
INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09-g17808ce (Mar 24 2020 - 14:47:01 +0800)
Model: Rockchip RK3399 Evaluation Board
PreSerial: 2
DRAM: 3.8 GiB
Sysmem: init
Relocation Offset is: f5be5000
Using default environment
dwmmc@fe320000: 1, sdhci@fe330000: 0
Bootdev(atags): mmc 0
MMC0: HS400, 150Mhz
PartType: EFI
get part misc fail -1
boot mode: None
Load FDT from boot part
DTB: rk-kernel.dtb
Android header version 0
I2c speed: 400000Hz
PMIC: RK808
vdd_center 900000 uV
vdd_cpu_l 900000 uV
LDO_REG4 init 3000000 uV
vdd_log 1000000 uV
Model: OrangePi 4
Rockchip UBOOT DRM driver version: v1.0.1
CLK: (uboot. arml: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
CLK: (uboot. armb: enter 24000 KHz, init 24000 KHz, kernel 0N/A)
aplll 816000 KHz
apllb 24000 KHz
dpll 856000 KHz
cpll 24000 KHz
gpll 800000 KHz
npll 600000 KHz
vpll 24000 KHz
aclk_perihp 133333 KHz
hclk_perihp 66666 KHz
pclk_perihp 33333 KHz
aclk_perilp0 266666 KHz
hclk_perilp0 88888 KHz
pclk_perilp0 44444 KHz
hclk_perilp1 100000 KHz
pclk_perilp1 50000 KHz
Net: eth0: ethernet@fe300000
Hit key to stop autoboot('CTRL+C'): 0
Could not find misc partition
ANDROID: reboot reason: "(none)"
Not AVB images, AVB skip
Fdt Ramdisk skip relocation
Booting IMAGE kernel at 0x00280000 with fdt at 0x8300000...

Copy code

Serial output with the Armbian image:

DDR Version 1.22 20190506
In
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 0, cs 1, advanced training done
channel 1, cs 0, advanced training done
channel 1, cs 1, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=29544MB
FwPartOffset=2000 , 0
StorageInit ok = 122713
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part: 0, name: uboot, start:0x6000, size:0x2000
GPT part: 1, name: trust, start:0x8000, size:0x2000
GPT part: 2, name: boot, start:0xc000, size:0x10000
GPT part: 3, name: rootfs, start:0x5c000, size:0x3957fdf
find part:uboot OK. first_lba:0x6000.
find part:trust OK. first_lba:0x8000.
LoadTrust Addr:0x8000
LoadTrust Addr:0x8400
LoadTrust Addr:0x8800
LoadTrust Addr:0x8c00
LoadTrust Addr:0x9000
LoadTrust Addr:0x9400
LoadTrust Addr:0x9800
LoadTrust Addr:0x9c00
Addr:0x8000 No find trust.img!
LoadTrustBL error:-3
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = -2, SecureMode = 0

Copy code

patrix · Published in 2020-7-11 21:10:03

Pretty sure that when I had flashed Armbian to the eMMC, the option was "boot from SPI, system on emmc/sdcard" or something along those lines, which means that probably the SPI boot got flashes with whatever is now causing this issue...

patrix · Published in 2020-7-12 12:08:46

BTW I end up in the same situation when I use Orange Pi's "install_to_emmc" script, can only boot opi images and not Armbian anymore.

I can tentatively conclude that:

1) some special structure needs to be preserved on the eMMC, and both Orange Pi's and Armbian's scripts mess that up
2) the Orange Pi sdcard images do have what is needed to allow them to boot even when the eMMC isn't setup correctly, while Armbian doesn't have that (not surprising as they are more standard images for a multitude of boards)
3) I need to safeguard my working emmc.img file forever in case I ever need it (and I will)

patrix · Published in 2020-7-13 08:41:00

Hi Narly9999, definitely need to upload it somewhere.

My findings so far is that the "Default" emmc image shows no partitions in fdisk or parted, and yet if I boot while pressing the recovery button I do end up in some Android recovery shell (through the serial).

Nothing happens when something else (Armbian or Orange Pi Ubuntu) is flashed to the emmc.

I've read somewhere (can't find the port, somewhere on Armbian) that there's some hidden image at the end of the emmc, which of course is what ends up being overwritten by Armbian or by install_to_emmc. I haven't hunted further to see if I find anything on the emmc image, but I'm curious about it and if I can make both that and the OS on emmc coexist...

fabiorcosta · Published in 2023-2-6 23:18:25

Can you help me ? I flashed a sd and could not make the OPi boot from it. I did armbian, Ubuntu, Debian. Whatever I use on the sd it boots from internal memory.

luckywin · Published in 2023-2-22 11:18:12

Spend some time playing. I'm interested in finding out more because I have strong views about it. Would you please provide more details to your blog post? We will all actually gain from it. nytimes crossword

lililala · Published in 2023-2-25 10:33:40

刻意去找的东西,往往是找不到的。天下万物的来和去,都有它的时间。

幸运飞艇走势图、福彩双色球走势图、幸运时时彩走势图

CharlesService · Published in 2023-9-18 14:26:21

Many educational institutions have strict policies against using essay writing services as they can constitute academic dishonesty. It's crucial to check your school's code of conduct and adhere to their guidelines but also you can find more info to have quality task. As you progress in your academic or professional career, you may face situations where you must write essays independently. Developing strong writing skills early on can be invaluable.