Linux Build Help: Stuck at "Starting kernel ..."
#3
Update:

I moved the boot.scr to another name so U-Boot won't use it to boot automatically. I wanted to see if my bootargs were correct with a working system. They were not.

I have changed the armbianEnv.txt to contain all the correct parameters:
Code:
verbosity=1
overlay_prefix=rockchip
rootdev=UUID=c45ee5d-2da6-41af-b87d-48b048c48c5e
conargs=ttyS2,1500000
bootargs=${conargs} root=${rootdev} rootwait rootfstype=ext4 consoleblank=0 loglevel=1 ubootpart=${partuuid} init=/sbin/init
load_kernel=ext4load mmc 1 ${kernel_addr_r} boot/Image
load_fdt=ext4load mmc 1 ${fdt_addr_r} boot/dtb-4.4.182-rockchip64/rockchip/rk3399-rockpro64.dtb
load_ramdisk=ext4load mmc 1 ${ramdisk_addr_r} boot/uInitrd

I am then running the U-Boot commands to get the UUID part for MMC 1.
This boots correctly from the Armbian image with my linux image and DTB. I also got early printing of the boot messages as well as shutdown messages the I was not receiving before.
I then went and dd'ed my u-boot.itb and idbloader image to the memory locations specified by Rockchip. I can load my parameters and use them but I am still stuck at "Starting kernel..."
The only differences in the messages before the starting kernel message between the prebuilt image and upstream U-Boot is an error reserving fdt memory:
Code:
#### AYUFAN PREBUILT IMAGE:
===========================
## Loading init Ramdisk from Legacy Image at 04000000 ...
  Image Name:    uInitrd
  Image Type:    AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:     4460484 Bytes = 4.3 MiB
  Load Address:  00000000
  Entry Point:   00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 0x1f00000
   Booting using the fdt blob at 0x1f00000
  Loading Ramdisk to f5ac1000, end f5f01fc4 ... OK
  Loading Device Tree to 00000000f5aa6000, end 00000000f5ac0c8b ... OK


#### UPSTREAM U-BOOT 2019:
==========================
## Loading init Ramdisk from Legacy Image at 04000000 ...
  Image Name: uInitrd
  Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 4460484 Bytes = 4.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 0x1f00000
  Booting using the fdt blob at 0x1f00000
Loading Ramdisk to 7dae5000, end 7df25fc4 ... OK
ERROR: reserving fdt memory region failed (addr=0 size=0)
Loading Device Tree to 000000007dacb000, end 000000007dae4bb0 ... OK

I think this might be causing the kernel to crash but not sure yet. Again, if anyone has any advice it'd be greatly appreciated. Thanks.
  Reply


Messages In This Thread
RE: Linux Build Help: Stuck at "Starting kernel ..." - by ihamilton - 10-10-2019, 12:51 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Kernel Update from 4.4 (Ayufan) on Ubuntu 20.04 db579 3 350 10-22-2020, 01:12 PM
Last Post: dukla2000
Thumbs Up First Manjaro Mainline build! Luke 10 2,943 10-20-2020, 04:29 AM
Last Post: vfr400racer
  Xen EFI with Alpine Linux dom0 sir.lami 0 285 08-26-2020, 12:25 PM
Last Post: sir.lami
  Linux Host - QEMU Android Guest? rik-shaw 0 302 07-09-2020, 08:02 PM
Last Post: rik-shaw
  RETRO GAMING BATOCERA LINUX + ROSHAMBO CASE - Tutoriel Fr TheMiniCakeTV 0 1,063 07-02-2020, 12:45 PM
Last Post: TheMiniCakeTV
  Arch Linux on RockPro64 mmatyas 30 15,722 05-30-2020, 12:08 PM
Last Post: mmatyas
  RockPro64 Linux Manjaro HDMI 4K mkne 12 1,841 05-03-2020, 07:23 AM
Last Post: PakoSt
  Mainline U-Boot with Arch Linux PKGBUILD mmatyas 0 452 04-17-2020, 03:49 AM
Last Post: mmatyas
  Slow/dead ethernet on (non-Ayufan) Linux Mainline (fixed) mmatyas 1 506 04-17-2020, 02:53 AM
Last Post: Thra11
  Rockpro64 and stock arch linux TaborFife 6 1,858 01-15-2020, 05:17 PM
Last Post: dragop

Forum Jump:


Users browsing this thread: 1 Guest(s)