Jump to content

Recommended Posts

Posted

The xenial img from dl.armbian.com works fine, but doesn't have SCTP support, so I wanted to compile my own image. Did a "show kernel config" and built an img. When I boot:

 

In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 128
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=29820MB
FwPartOffset=2000 , 2000
SdmmcInit=0 2
StorageInit ok = 267624
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x97af0
RunBL31 0x10000
␁NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 11:37:09, May  4 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using rkfiq sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2018.01-rc2-armbian (May 04 2018 - 13:03:35 -0400)

Model: Pine64 Rock64
DRAM:  4 GiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
Card did not respond to voltage select!
mmc_init: -95, time 9
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2923 bytes read in 29 ms (97.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
215 bytes read in 23 ms (8.8 KiB/s)
## Error: Can't overwrite "ethaddr"
himport_r: can't insert "ethaddr=02:38:a0:82:2d:c0" into hash table
## Error: Can't overwrite "eth1addr"
himport_r: can't insert "eth1addr=02:38:a0:82:2e:c1" into hash table
5420341 bytes read in 707 ms (7.3 MiB/s)
11837952 bytes read in 1491 ms (7.6 MiB/s)
33587 bytes read in 41 ms (799.8 KiB/s)
** File not found /boot/dtb/rockchip/overlay/rk3328-fixup.scr **
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    5420277 Bytes = 5.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to fc9e4000, end fcf0f4f5 ... OK
   reserving fdt memory region: addr=1f00000 size=6e000
   Loading Device Tree to 00000000fc973000, end 00000000fc9e3fff ... OK

Starting kernel ...

 

Posted

For reference, this is the log from the dl.armbian img. How can I build this img from source??

 

In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 127
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=29820MB
FwPartOffset=2000 , 2000
SdmmcInit=0 2
StorageInit ok = 208352
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa4cf8
RunBL31 0x10000
␁NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 18:38:03, Mar 12 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using rkfiq sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-armbian (Mar 28 2018 - 17:14:43 +0200)

Model: Pine64 Rock64
DRAM:  4 GiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
Card did not respond to voltage select!
mmc_init: -95, time 9
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930343200000000032004
serial=2a26ac9f6f42c2f
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2960 bytes read in 29 ms (99.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
112 bytes read in 23 ms (3.9 KiB/s)
4428328 bytes read in 586 ms (7.2 MiB/s)
19019784 bytes read in 2376 ms (7.6 MiB/s)
58088 bytes read in 54 ms (1 MiB/s)
** File not found /boot/dtb/rockchip/overlay/-fixup.scr **
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    4428264 Bytes = 4.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to fcac7000, end fcf001e8 ... OK
   reserving fdt memory region: addr=1f00000 size=74000
   Loading Device Tree to 00000000fca50000, end 00000000fcac6fff ... OK

Starting kernel ...

ERROR:   rockchip_plat_sip_handler: unhandled SMC (0x82000003)
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 
/dev/mmcblk0p1: clean, 33416/66384 files, 208263/265216 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to ␛[1mUbuntu 16.04.4 LTS␛[0m!

 

Posted

Armbian depends on upstream, when sources changes the build can break. My (noobs) approach to figure out whats wrong is often first build an image without any changes to see if that one boots (to see if buildscript and current patches are okay) and than make my changes to test when it breaks. In case your changes break from booting a diff of the two configs might help that somebody can help you. 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines