From: Peter Korsgaard <peter@korsgaard.com>
To: Frank Hunleth <fhunleth@troodon-software.com>
Cc: Indrek Kruusa <indrek.kruusa@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] configs/nezha_defconfig: bump versions for uboot, sbi and linux kernel
Date: Mon, 12 Dec 2022 18:56:49 +0100 [thread overview]
Message-ID: <87pmcoy07y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <_Xy-l8Ny6TGT7WRiixo_CPZYHzdUIuGYexyAlFzMnPCN0loQWU_ydtPGjnGDOAPHohUUzztFqL1rbhYa5bVk7cO2NN6fK_cUPe8cL4MiTMo=@troodon-software.com> (Frank Hunleth's message of "Mon, 12 Dec 2022 15:32:40 +0000")
>>>>> "Frank" == Frank Hunleth <fhunleth@troodon-software.com> writes:
Hi,
>> >>>>> "Indrek" == Indrek Kruusa indrek.kruusa@gmail.com writes:
>>
>> > BR2_TARGET_OPENSBI=y
>>
>> > BR2_TARGET_OPENSBI_CUSTOM_TARBALL=y
>>
>> > -BR2_TARGET_OPENSBI_CUSTOM_TARBALL_LOCATION="$(call
>> > github,smaeul,opensbi,e6793dc36a71537023f078034fe795c64a9992a3)/opensbi-e6793dc36a71537023f078034fe795c64a9992a3.tar.gz"
>>
>> > +BR2_TARGET_OPENSBI_CUSTOM_TARBALL_LOCATION="$(call
>> > github,smaeul,opensbi,5307908fb651a01cc6a2f3fd9fc7b9b471bbccb3)/opensbi-5307908fb651a01cc6a2f3fd9fc7b9b471bbccb3.tar.gz"
>>
>>
>> Why still use this custom opensbi? There is D1 support in version 1.1 as
>> mentioned on https://linux-sunxi.org/Allwinner_Nezha
>>
> Just in case it helps, I've been testing both the Korsgaard and Kruusa
> patches on a MangoPI MQ Pro. This board is close, but not exactly like
> the Nezha, so I expect differences.
> Using OpenSBI 1.1 results in a non-booting Linux kernel for me. Here's the error:
Just to be sure, is this with the 5.19 based kernel we used to use
(fe178cf0153d98b71cb01a46c8cc050826a17e77) or the "new" 6.1-rc3 based
one (ca67838d84af4c9f85d06311c9e98e1adf46308f)?
> Unhandled exception: Store/AMO access fault
> EPC: 000000005ff8f838 RA: 000000005ffb6346 TVAL: 0000000040040000
> EPC: 0000000042e01838 RA: 0000000042e28346 reloc adjusted
> Code: b383 0385 be03 0405 be83 0485 bf03 0505 (e110)
Sounds like access to an invalid address to me. When does this trigger?
Early doing Linux boot?
I see the mangopi mq-pro only has 512MB RAM. 0x5xxx.xxxx is at the very
end of that (memory starts at 0x4xxx.xxxx), did you update the memory
size in the device tree passed to OpenSBI?
I just did a clean rebuild of nezha_defconfig here, and it boots without
any issues:
U-Boot SPL 2022.10 (Dec 12 2022 - 17:20:45 +0100)
sunxi_ram_probe: dram-controller@3102000: probing
DRAM only have internal ZQ!!
ddr_efuse_type: 0x0
[AUTO DEBUG] two rank and full DQ!
ddr_efuse_type: 0x0
[AUTO DEBUG] rank 0 row = 15
[AUTO DEBUG] rank 0 bank = 8
[AUTO DEBUG] rank 0 page size = 2 KB
[AUTO DEBUG] rank 1 row = 15
[AUTO DEBUG] rank 1 bank = 8
[AUTO DEBUG] rank 1 page size = 2 KB
rank1 config same as rank0
DRAM BOOT DRIVE INFO: V0.24
DRAM CLK = 792 MHz
DRAM Type = 3 (2:DDR2,3:DDR3)
DRAMC ZQ value: 0x7b7bfb
DRAM ODT value: 0x42.
ddr_efuse_type: 0x0
DRAM SIZE =1024 M
DRAM simple test OK.
mxstatus=0xc0408000 mhcr=0x00000109 mcor=0x00000003 mhint=0x00004000
Trying to boot from MMC1
PLL reg = 0xf8216300, freq = 1200000000
SPL size = 81920, sector = 160
sunxi_ram_get_info: dram-controller@3102000: getting info
OpenSBI v1.1
____ _____ ____ _____
/ __ \ / ____| _ \_ _|
| | | |_ __ ___ _ __ | (___ | |_) || |
| | | | '_ \ / _ \ '_ \ \___ \| _ < | |
| |__| | |_) | __/ | | |____) | |_) || |_
\____/| .__/ \___|_| |_|_____/|____/_____|
| |
|_|
Platform Name : Allwinner D1 Nezha
Platform Features : medeleg
Platform HART Count : 1
Platform IPI Device : ---
Platform Timer Device : --- @ 0Hz
Platform Console Device : uart8250
Platform HSM Device : sun20i-d1-ppu
Platform Reboot Device : sunxi-wdt-reset
Platform Shutdown Device : ---
Firmware Base : 0x40000000
Firmware Size : 288 KB
Runtime SBI Version : 1.0
Domain0 Name : root
Domain0 Boot HART : 0
Domain0 HARTs : 0*
Domain0 Region00 : 0x0000000040000000-0x000000004007ffff ()
Domain0 Region01 : 0x0000000000000000-0xffffffffffffffff (R,W,X)
Domain0 Next Address : 0x0000000042e00000
Domain0 Next Arg1 : 0x0000000042e8b978
Domain0 Next Mode : S-mode
Domain0 SysReset : yes
Boot HART ID : 0
Boot HART Domain : root
Boot HART Priv Version : v1.11
Boot HART Base ISA : rv64imafdcvx
Boot HART ISA Extensions : time
Boot HART PMP Count : 8
Boot HART PMP Granularity : 2048
Boot HART PMP Address Bits: 38
Boot HART MHPM Count : 0
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109
sunxi_set_gate: (CLK#24) unhandled
U-Boot 2022.10 (Dec 12 2022 - 17:20:45 +0100) Allwinner Technology
..
Starting kernel ...
[ 0.000000] Linux version 6.1.0-rc3 (peko@dell) (riscv64-buildroot-linux-gnu-gcc.br_real (Buildroot 2022.11-477-g5cb74c92f7) 11.3.0, GNU ld (GNU Binutils) 2.38) #1 PREEMPT Mon Dec 12 17:28:21 CET 2022
..
# uptime
00:07:05 up 6 min, load average: 0.00, 0.00, 0.00
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-12 17:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 20:17 [Buildroot] [PATCH 1/5] configs/nezha_defconfig: bump versions for uboot, sbi and linux kernel Indrek Kruusa
2022-12-11 20:17 ` [Buildroot] [PATCH 2/5] board/nezha/genimage.cfg: remove boot0 from genimage.cfg Indrek Kruusa
2022-12-12 7:24 ` Peter Korsgaard
2022-12-12 16:25 ` Indrek Kruusa
2022-12-11 20:17 ` [Buildroot] [PATCH 3/5] board/nezha/overlay/boot/extlinux/extlinux.conf: activate framebuffer console on HDMI Indrek Kruusa
2022-12-12 7:30 ` Peter Korsgaard
2022-12-12 16:29 ` Indrek Kruusa
2022-12-11 20:17 ` [Buildroot] [PATCH 4/5] board/nezha/patches: delete obsolete patches for uboot Indrek Kruusa
2022-12-11 20:17 ` [Buildroot] [PATCH 5/5] board/nezha/readme.txt: update readme.txt about framebuffer console on HDMI Indrek Kruusa
2022-12-11 21:47 ` [Buildroot] [PATCH 1/5] configs/nezha_defconfig: bump versions for uboot, sbi and linux kernel Thomas Petazzoni via buildroot
2022-12-12 7:22 ` Peter Korsgaard
2022-12-12 15:32 ` Frank Hunleth via buildroot
2022-12-12 16:52 ` Indrek Kruusa
2022-12-12 16:54 ` Angelo Compagnucci
2022-12-12 17:02 ` Indrek Kruusa
2022-12-12 17:56 ` Peter Korsgaard [this message]
2022-12-13 20:09 ` Indrek Kruusa
2022-12-13 20:18 ` Peter Korsgaard
2022-12-13 21:32 ` Frank Hunleth via buildroot
2022-12-13 21:35 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmcoy07y.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fhunleth@troodon-software.com \
--cc=indrek.kruusa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox