Jump to content

[HELP] Stuck in U-boot after overlay.dts attempt


yuri.vivaldi

Recommended Posts

Hi, everyone

 

I have 2 rockpi s based boards, and I tried to apply an overlay to one.

It actually compiled, I rebooted and the nothing more.

I connected serial, e it was on U-boot, spitting this:

 

Spoiler
DDR Version V2.06 20211109
CHIP ID = 0x00003308
REG2C: 0x00000034, 0x00000034
In
589MHz
DDR3
Col=10 Bank=3 Row=15 Size=512MB
OUT: sdram_init finish.
Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36
ROM VER:0x56323030, 19
chip_id:330800,0
ChipType = 0x13, 512
DPLL = 1300 MHz
...nandc_flash_init enter...
No.1 FLASH ID:ff ff ff ff ff ff
DPLL = 1300 MHz
sfc nor id: ff ff ff
DPLL = 1300 MHz
sfc_nand id: ff ff ff
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc2:cmd8,20
mmc2:cmd5,20
mmc2:cmd55,20
DPLL = 1300 MHz
NeedKHz=18000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=48000KHz,clock=650000KHz
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc0:cmd5,20
DPLL = 1300 MHz
NeedKHz=24000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=40000KHz,clock=650000KHz
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7624MB
FwPartOffset=2000 , 0
StorageInit ok = 168518
SecureMode = 0
Secure read PBA: 0x4
Secure read PBA: 0x404
Secure read PBA: 0x804
Secure read PBA: 0xc04
Secure read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3306530 signature is wrong
recovery gpt...
GPT 0x3306530 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x600000, size=0x994f8
RunBL31 0x40000 @ 253233 us
INFO:    Preloader serial: 0
NOTICE:  BL31: v1.3(release):30f1405
NOTICE:  BL31: Built : 17:08:28, Sep 23 2019
INFO:    Lastlog: last=0x100000, realtime=0x102000, size=0x2000
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe b
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE init          ialization. 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 = 0x600000
INFO:    SPSR = 0x3c9


U-Boot 2022.04-armbian (Dec 23 2022 - 09:36:07 +0000)

Model: Radxa ROCK Pi S
DRAM:  510 MiB
Core:  276 devices, 20 uclasses, devicetree: separate
MMC:   dwmmc@ff480000: 1, dwmmc@ff490000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Model: Radxa ROCK Pi S
rockchip_dnl_key_pressed read board id failed
Net:   eth0: ethernet@ff4e0000
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
3045 bytes read in 4 ms (743.2 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
17 bytes read in 3 ms (4.9 KiB/s)
13956325 bytes read in 594 ms (22.4 MiB/s)
31273472 bytes read in 1325 ms (22.5 MiB/s)
Failed to load '/boot/dtb/'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x680000 to 0x800000, end=2670000
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13956261 Bytes = 13.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
Speed: 10, half duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
CPU not owner of tx frame

Retry time exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-72-e8-9e-60-82-ef
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-rk3308-evb_rk3308
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-rk3308
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
Speed: 10, half duplex
*** ERROR: `serverip' not set
Config file not found
starting USB...
No working controllers found
Speed: 10, half duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
CPU not owner of tx frame

Retry time exceeded; starting again
=>

 

 

U-boot seems unable to load the device tree, but to my knowledge, a broken overlay shouldn't break anything

Any help is welcome

 

Thx

Link to comment
Share on other sites

Armbian & Khadas are rewarding contributors

I managed to restore armbian to the board that couldn't boot.

The boards are this model.

 

The situation is this, now:

  1. board 1:
    • Booting in Armbian, now clean, no overlay installed  with armbianEnv.txt:
      • Spoiler

        verbosity=1
        extraargs=swiotlb=1024
        overlay_prefix=rk3308
        fdtfile=rockchip/rk3308-rock-pi-s.dtb
        rootdev=UUID=9be2d77f-b3b8-4e7c-aeb3-e12ffd896c77
        rootfstype=ext4
        console=serial
        usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

    • This board seems to be working, but eth0 seems to be on a different physical device from before all this trouble, meaning now the eth0 is on a different  real ethernet port
  2. board 2:
    • Booting Armbian,  with armbianEnv.txt:
      • Spoiler

        verbosity=1
        extraargs=swiotlb=1024
        overlay_prefix=rk3308
        fdtfile=rockchip/rk3308-rock-pi-s.dtb
        rootdev=UUID=042ab219-dbd2-40b0-b9f5-b88bf10b12f3
        rootfstype=ext4
        console=serial
        user_overlays=
        usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

         

    • Same problem with the eth0

 

On both boards I have problems with detecting SD card via U-boot, while no problems from Armbian

 

I hope this clarifies the situation 

 

[UPDATE]

 

I managed to get the SDs working, Uboot doesn't like when booted with the SD inserted, seem like....

Also, I physically disabled the 2nd ethernet port, now eth0 is where it should be, but still no connection...

 

[UPDATE 2]

 

I'm trying to get the ethernet to work, any of the two

This is the IP A printout:

$ ip a
>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 72:e8:9e:60:82:ef brd ff:ff:ff:ff:ff:ff
    inet 169.254.14.193/16 brd 169.254.255.255 scope link eth0:avahi
       valid_lft forever preferred_lft forever
    inet6 fe80::70e8:9eff:fe60:82ef/64 scope link
       valid_lft forever preferred_lft forever
 3: wlx8812ac17702d: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 88:12:ac:17:70:2d brd ff:ff:ff:ff:ff:ff

 

 

 

Edited by yuri.vivaldi
Developments 2
Link to comment
Share on other sites

Hello small question.

In Armbian 22.11 there is info about improved support for rockpi s .

What it means ? past few monhts the image of armbian with kernel newer that 4.4 was unable boot on older board with RK3308 .

On RK3308B-S it was ok.

after 22.11 is there support for older RK3308 or not ?

Github radxa dont say anything about it ... 

radxa github releases

Link to comment
Share on other sites

I resolved the issue, on my case at least:
The Uboot instance doesn't like the SD to be inserted while booting, so it couldn't detect it.

Simply leave the SD out, boot to uboot, insert the SD then boot to mmc1(SD)

 

For the double IP problem,the error was on my part. I assumed that the eth0 interface from linux was the physical Ethernet labled Eth1 and eth1 in linux was Eth2 physical. That's wrong:

  • linux eth0 => Physical Ethernet2
  • linux eth1 => Physical Ethernet1

With this, the problems are resolved

Link to comment
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...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines