• 0

Pinebook Pro install instructions?


ej0rge
 Share

1 1

Question

I know for sure that booting from an sd card and then using dd to write the uncompressed image to the emmc device isn't what works. I'm talking about Armbian_22.02.1_Pinebook-pro_focal_current_5.15.25_xfce_desktop.img here. 

 

Because that essentially bricked my PBP. I have the little adapter to connect the emmc to a usd slot, and using balena etcher to write to that isn't it either. 

 

the uboot in that image prevents booting from sd automatically as well, and i didn't find any uboot documentation that made it clear how to manually boot from sd, though i did hook up a serial console. This is what it said. The LED never turned green, the display flashes once but displays no images or text. 

 

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

 

 

Link to post
Share on other sites

14 answers to this question

Recommended Posts

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

  • 0
Am 6.4.2022 um 07:19 schrieb ej0rge:

I know for sure that booting from an sd card and then using dd to write the uncompressed image to the emmc device isn't what works. I'm talking about Armbian_22.02.1_Pinebook-pro_focal_current_5.15.25_xfce_desktop.img here. 

Well, well. same problem here. As far as I remember I did not have the problem with the buster image and a dd to the emmc wasn' a problem ether.

Link to post
Share on other sites

  • 0
vor 58 Minuten schrieb Werner:

Maybe @seclorum can do some tests here.

Also maybe @NicoD finds some time to do so.

Tried all possibilities:

formatted emmc to one ext4 partition - dead

removed emmc - dead

inserted new Armbian_22.02.1_Pinebook-pro_focal_current_5.15.25_xfce_desktop.img with an 16GB SD-Card - dead!

OK... will insert emmc again and awaiting solutions.. I do not have an idea by now.

Link to post
Share on other sites

  • 0
9 hours ago, Wilhelm Moser said:

Soo. the pinebook ist dead as dead can be... and now?

 

I have the microsd emmc adapter, so i used that and another computer to write a manjaro image to the emmc.

Link to post
Share on other sites

  • 0
8 hours ago, umiddelb said:

µSD should have highest boot priority.

Should, yes, but doesn't. RK3399 has an internal fixed boot priority which is something like SPI - eMMC - microSD - NVMe. This cannot be altered.

Armbian works around this by installing a boot loader to eMMC which points back to microSD and if that fails continue to boot from whatever is available instead.

If there is a boot loader on the eMMC that does not do that you have a hard time. That is why pbp installed an internal switch to disconnect eMMC from power to allow microSD to boot.

Link to post
Share on other sites

  • 0
On 4/25/2022 at 11:13 PM, Werner said:

Should, yes, but doesn't. RK3399 has an internal fixed boot priority which is something like SPI - eMMC - microSD - NVMe. This cannot be altered.

Armbian works around this by installing a boot loader to eMMC which points back to microSD and if that fails continue to boot from whatever is available instead.

If there is a boot loader on the eMMC that does not do that you have a hard time. That is why pbp installed an internal switch to disconnect eMMC from power to allow microSD to boot.

 

Interestingly, throwing that switch didn't allow me to boot from my sd card. I don't remember at this point what image was on the SD at the time. 

Link to post
Share on other sites

  • 0

I recently tried this as well. And ran into the same issues. I did eventually manage to resolve this by flashing a manjaro build to an sdcard. Opening up the pinebook pro. Toggling the eMMC off using the little switch. Starting the laptop. Pressing any key while it was in uboot so it would just pause (I am really not sure if all the manjaro images have this, in either case it was Manjaro-ARM-sway-22.04.img). Toggling the eMMC back on, which would now be detected uboot and later on Linux itself.

After this I continued on to install Manjaro because I was just really annoyed at that moment, but I would assume that manually flashing a working uboot at this point would work. Hope this is useful to anyone. And hope this is getting fixed at some point.

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
Answer this question...

×   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

1 1