0
Marko Buršič

kernel 5.4.43 Rock PI 4B not starting

Recommended Posts

Hi,

 

I don't have an idea why it stucks.  Armbian_20.05.0-trunk_Rockpi-4b_buster_current_5.4.43

 

EDIT:

 

I have downloaded the pre-build image Armbian_20.05.1_Rockpi-4b_buster_current_5.4.43 and it works. It boots at an astonishing speed, only 18 sec which is a miracle. How can I build the same kernel? Is sufficient to copy just a .config file? 

 

T T DDR Version 1.13 20180801
In
Channel 0: LPDDR4,50MHz
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,50MHz
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x82
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT
U-Boot SPL board init

U-Boot SPL 2017.09-armbian (Jun 01 2020 - 06:46:11)
Trying to boot from MMC2
Card did not respond to voltage select!
mmc_init: -95, time 10
spl: mmc init failed with error: -95
Trying to boot from MMC1
NOTICE:  BL31: v1.3(debug):65aa5ce
NOTICE:  BL31: Built : 10:47:37, Jun 19 2018
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1151): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-armbian (Jun 01 2020 - 06:46:11 +0000)

Model: Radxa ROCK Pi 4
DRAM:  3.9 GiB
DCDC_REG1@vdd_center: ; enabling
DCDC_REG2@vdd_cpu_l: ; enabling
DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
LDO_REG4@vcc_sd: set 3300000 uV; enabling
LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
LDO_REG6@vcc_1v5: set 1500000 uV; enabling
LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
LDO_REG8@vcc_3v0: set 3000000 uV; enabling
SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
vdd-log@vdd_log: ; enabling (ret: -38)
MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
SF: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Radxa ROCK Pi 4
boot mode 0.
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
USB3:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
ethernet@fe300000 Waiting for PHY auto negotiation to complete.... done
Speed: 1000, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.134 (257 ms)
*** Warning: no boot file name; using 'C0A80186.img'
Using ethernet@fe300000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.134
Filename 'C0A80186.img'.
Load address: 0x800800
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-36-bb-f1-14-ce-8a
Speed: 1000, full duplex


 

 

 

Share this post


Link to post
Share on other sites
37 minutes ago, Marko Buršič said:

I don't have an idea why it stucks.  Armbian_20.05.0-trunk_Rockpi-4b_buster_current_5.4.43

u-boot does not recognise the storage and tries to boot from network.

I see that you have built yourself an image yesterday but it is probably using some old Armbian build repository revision as it still uses v2017.09 u-boot which is switched to mainline for RockPi 4 in current sources.

 

Did you also try to use the ready made v20.05.1 images from https://dl.armbian.com/rockpi-4b/archive/? Does it also get stuck with them?

 

Please use Spoiler next time for boot log ;-)

Share this post


Link to post
Share on other sites

@piter75 Maybe you have answered meanwhile I did edit my question, so yes the ready made image works great. I am still figuring out such enormous step forward, I am installing Armbian from scratch, I hope I will make a trunk with my patches that it will work as good as ready made.

Share this post


Link to post
Share on other sites
8 minutes ago, Marko Buršič said:

Maybe you have answered meanwhile I did edit my question, so yes the ready made image works great.

I did not see you edited your post in the meantime indeed ;-)

 

12 hours ago, Marko Buršič said:

How can I build the same kernel? Is sufficient to copy just a .config file?

The fix is actually in the u-boot but it is patched for mainline u-boot only. RockPi 4 did get it as part of the u-boot switch to mainline.

IMHO the easiest way for you to get it in local build would be to rebase your build repository on top of master.

Share this post


Link to post
Share on other sites
27 minutes ago, Marko Buršič said:

Armbian version is 20.08

The version is actually 20.08.0-trunk which means it is a work in progress that will become v20.08.1 one day just as v20.05.1 that was released last weekend ;-)

If you would like to use the stable release branch you can checkout v20.05 branch.

Share this post


Link to post
Share on other sites

Ok, but how should I install it? I did 

git clone https://github.com/armbian/build

Should I use 

git clone https://github.com/armbian/build/tree/v20.05

instead?

 

Share this post


Link to post
Share on other sites

@Marko Buršič if you have already cloned then in "build" directory:

 

git checkout v20.05

To go back to master you can checkout master branch.

 

Of course you can also clone again into new "build" directory with v20.05 checked out:

git clone -b v20.05 https://github.com/armbian/build

 

Share this post


Link to post
Share on other sites

Thank you. I was struggling to find the solution by myself (before your post), so I ended with this (if I remember correctly):

 

git clone  https://github.com/armbian/build --branch v20.05

The version v20.05.2 was installed. I hope it is the same as your way (still learning). A strange thing now is that I wanted to remove lots of useless drivers, then I did a kernel configuration, deselected many options, what I got is that almost every driver is now compiled and loaded. I will try again tomorrow, ...never ending story.

 

 

 

Share this post


Link to post
Share on other sites

No luck. I have tried to customise the kernel build with KERNEL_CONFIGURE=yes. It simply builds as default, no matter what I do unselect or changed it is going to be compiled/built.  Maybe @Igor knows the answer?

Share this post


Link to post
Share on other sites
5 minutes ago, Marko Buršič said:

no matter what I do unselect or changed it is going to be compiled/built.


You mean changes does not affect on the build resoult?

Share this post


Link to post
Share on other sites
10 hours ago, Igor said:


You mean changes does not affect on the build resoult?

 

Yes. I can change the configuration, uncheck media drivers, uncheck feildbus drivers, ....an so many drivers, but I got everything built. For now, I do think I will leave as it is, since the new armbian+ new kernel boots only in 15s compared to previous armbian version it took more than 200s. 

Share this post


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
Reply to this topic...

×   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...
0