mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: RK3568 fail with 2023.11.0
Date: Thu, 30 Nov 2023 15:59:00 +0100	[thread overview]
Message-ID: <8b300282-86fb-40bd-adfa-4ee0fd60045e@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvSUuHY0RGQ0hSOOKPPHHzaRJfnHR4c2hJ2JznqA2t-H9A@mail.gmail.com>

On 30.11.23 15:28, Alexander Shiyan wrote:
> Hello All.
> 
> The latest version of the barebox does not work on a RK3568 with 4G memory.
> With a similar board with 2G memory, everything works fine.
> ...
> NOTICE:  BL31: v2.3():v2.3-607-gbf602aff1:cl
> NOTICE:  BL31: Built : 10:16:03, Jun  5 2023
> INFO:    GICv3 without legacy support detected.
> INFO:    ARM GICv3 driver initialized in EL3
> INFO:    pmu v1 is valid 220114
> INFO:    Using opteed sec cpu_context!
> INFO:    boot cpu mask: 0
> 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 = 0xb00000
> INFO:    SPSR = 0x3c9
>> rockchip-dmc: rockchip_sdram_size(reg2=1000eaf1, reg3=30000001)
> rockchip-dmc: rank 2 cs0_col 10 cs1_col 10 bk 3 cs0_row 16 cs1_row 16
> bw 2 row_3_4 0
> rockchip-dmc: rk3568_ram0_size() = 4026531840
> uncompress.c: memory at 0x00a00000, size 0xef600000
> mmu: enabling MMU, ttb @ 0xeffe0000
> ===STALL HERE===
> 
> Through various manipulations, I identified the faulty patch: "ARM:
> mmu64: mark barebox text section executable during early init".
> After its rollback everything works as it should.

Can you print the output of the iomem command after reverting my patch?

Thanks,
Ahmad

> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2023-11-30 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 14:28 Alexander Shiyan
2023-11-30 14:59 ` Ahmad Fatoum [this message]
2023-11-30 15:07   ` Alexander Shiyan
2023-12-01  7:24     ` Alexander Shiyan
2023-12-01 15:14 ` Sascha Hauer
2023-12-03 17:41   ` Alexander Shiyan
2023-12-05  9:46     ` Sascha Hauer

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=8b300282-86fb-40bd-adfa-4ee0fd60045e@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@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