GiyoMoon / mangopi-mq-quad-alpine

Configs and script to build Alpine for the MangoPi MQ-Quad
3 stars 1 forks source link

WIP :sparkles: Reduce Image size by using tinyconfig #1

Open GiyoMoon opened 1 year ago

GiyoMoon commented 1 year ago

I'm trying to use tinyconfig as the base linux kernel config instead of defconfig to reduce the image size.

Currently, the image builds successfully but I'm not able to boot. It's stuck at Starting Kernel ....

Here is the log from UART:

U-Boot SPL 2023.07-rc1-g50f64026-dirty (May 02 2023 - 17:30:45 +0200)
pmic id is 0x4b
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.8(debug):d5f19c4
NOTICE:  BL31: Built : 17:30:03, May  2 2023
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a086d10, model: OrangePi Zero2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
ERROR:   RSB: set run-time address: 0x10003
INFO:    Could not init RSB: -65539
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.

U-Boot 2023.07-rc1-g50f64026-dirty (May 02 2023 - 17:30:45 +0200) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: OrangePi Zero2
DRAM:  1 GiB
Core:  45 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
352 bytes read in 1 ms (343.8 KiB/s)
## Executing script at 4fc00000
3975176 bytes read in 162 ms (23.4 MiB/s)
15817 bytes read in 2 ms (7.5 MiB/s)
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Device Tree to 0000000049ff9000, end 0000000049fffdc8 ... OK
Working FDT set to 49ff9000

Starting kernel ...