I tried this release and it worked GREAT on the SD card! So I decided to flash it to the eMMC. It flashed fine but failed to boot. I disabled the splash image so I could see what was happening - see attached. It couldn't find the boot device, even though it's there. I'm currently using tow-boot flashed to SPI (also works great). I know it gets to the eMMC (I changed the armbianEnv.txt file to point to /dev/mmcblk2p1 and it complained about that too, so I know it's reading the /boot directory
).
I used dd to flash the device, and the contents look fine. Same dd command I used for the SD card I've been testing with.
The UUID it says it can't find is the correct one set for the partition. And even though it says it's dropping to the shell, I can't type anything (no, I don't have a serial UART cable). Don't know anything about hardware initialization process. Anyone have any idea where to look?
03-31-2022, 04:19 PM
(This post was last modified: 03-31-2022, 04:21 PM by mspohr.)
I just did apt-get update/upgrade on my Armbian and now won't boot... just get spinning circle... forever.
I just did apt-get update/upgrade on my Armbian and now won't boot... just get spinning circle... forever.
04-01-2022, 03:25 PM
(This post was last modified: 04-01-2022, 03:29 PM by TRS-80.)
(03-03-2022, 07:47 PM)rleasle Wrote: So I decided to flash it to the eMMC. It flashed fine but failed to boot. I disabled the splash image so I could see what was happening - see attached. It couldn't find the boot device, even though it's there. I'm currently using tow-boot flashed to SPI (also works great). I know it gets to the eMMC (I changed the armbianEnv.txt file to point to /dev/mmcblk2p1 and it complained about that too, so I know it's reading the /boot directory).
I am not so sure about using tow-boot in concert with Armbian. The canonical way (in Armbian) would have been to use the nand-sata-install tool[0], either directly, or from armbian-config, in order to install to eMMC from sd card. As this process may (often does) differ between hardware.
But now, with tow-boot on SPI, this may complicate things.
[0] An unfortunate historical name which has now stuck, but it does flash to many different media, including eMMC.
(03-31-2022, 04:19 PM)mspohr Wrote: I just did apt-get update/upgrade on my Armbian and now won't boot... just get spinning circle... forever.
Did you upgrade release (e.g., Buster -> Bullseye)? If so, that has never actually been supported.
(04-01-2022, 03:25 PM)TRS-80 Wrote: (03-03-2022, 07:47 PM)rleasle Wrote: So I decided to flash it to the eMMC. It flashed fine but failed to boot. I disabled the splash image so I could see what was happening - see attached. It couldn't find the boot device, even though it's there. I'm currently using tow-boot flashed to SPI (also works great). I know it gets to the eMMC (I changed the armbianEnv.txt file to point to /dev/mmcblk2p1 and it complained about that too, so I know it's reading the /boot directory).
I am not so sure about using tow-boot in concert with Armbian. The canonical way (in Armbian) would have been to use the nand-sata-install tool[0], either directly, or from armbian-config, in order to install to eMMC from sd card. As this process may (often does) differ between hardware.
But now, with tow-boot on SPI, this may complicate things.
[0] An unfortunate historical name which has now stuck, but it does flash to many different media, including eMMC.
Thanks for the reply. Tried using Armbian's install script as suggested. Same error. I even tried erasing the SPI, but apparently there wasn't a usable u-boot on the eMMC, so now I can't boot anything - I'll have to open up the machine and disable the eMMC ...
04-05-2022, 07:12 PM
(This post was last modified: 04-05-2022, 07:16 PM by Timpanogos Slim.)
After booting this Armbian on my PBP, i used dd to write the image to the mmc.
It no longer boots. I see the screen power up. It does not boot from SD either.
I flipped the switch and connected a serial cable. Here's the output i get:
Quote:U-Boot TPL 2021.07-armbian (Feb 27 2022 - 08:51:28)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256Bstride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2021.07-armbian (Feb 27 2022 - 08:51:28 +0000)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c1588782-dirty
NOTICE: BL31: Built : 08:51:19, Feb 27 2022
U-Boot 2021.07-armbian (Feb 27 2022 - 08:51:28 +0000)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
Net: No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
Device 0: unknown device
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 20 ms (155.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
157 bytes read in 15 ms (9.8 KiB/s)
14235892 bytes read in 637 ms (21.3 MiB/s)
30083584 bytes read in 1311 ms (21.9 MiB/s)
82621 bytes read in 38 ms (2.1 MiB/s)
2698 bytes read in 32 ms (82 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3f50000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 14235828 Bytes = 13.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
And that's it.
Any clues for where to go from here? How to get it to boot from SD again maybe?
I have the sd card adapter for the emmc, and was able to write a working manjaro image to the emmc.
It's apparent that the uboot build included in Armbian_22.02.1_Pinebook-pro_focal_current_5.15.25_xfce_desktop.img has a change that makes it not try to boot sd first.
So, my suggestion, as an SQA guy, is: Maybe don't do that. Maybe make sure it behaves the way the user expects.
But for sure post another announcement when both that and the general not booting at all from emmc issues are resolved.
So, I gotta ask: has anyone successfully got this build of Armbian to run installed on the eMMC? If so, what did you do?
I should note that when i flipped the switch that disables the emmc, it still wouldn't boot from sd?
OK you have a serial connection to uboot
With flipped emmc switch it should NOT find mmc0, however it should find mmc1
But, this is not likely the problem, since it loads data (boot.scr) and kernel and dtb
likely the problem is video display is wrong
|
