From: Xavier Drudis Ferran <xdrudis@tinet.cat>
To: Jerome Forissier <jerome.forissier@linaro.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
imon Glass <sjg@chromium.org>, Heiko Schocher <hs@denx.de>,
Aswath Govindraju <a-govindraju@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Michal Simek <michal.simek@xilinx.com>,
Nishanth Menon <nm@ti.com>
Subject: Re: [SPAM] RockPi4B: spl_load_fit_image() writing past end of buffer & MMC errors
Date: Fri, 3 Jun 2022 19:46:26 +0200 [thread overview]
Message-ID: <20220603174626.GE2817@begut> (raw)
In-Reply-To: <20220603145837.GB2817@begut>
Sorry for the noise.
El Fri, Jun 03, 2022 at 04:58:38PM +0200, Xavier Drudis Ferran deia:
>
> In my Rock Pi 4B this does not happen. It happily writes the 17 blocks.
> Or it's just that I'm not noticing the problem ? Does it hang or give you
> an error, or do you just find it out by reading the SRAM?
>
It was just that I didn't notice the problem.
> I'm using the patch I sent yesterday:
>
> [PATCH 0/3] arm: rockchip: rk3399: rock-pi-4: power domain driver to boot from MMCSD
> https://lists.denx.de/pipermail/u-boot/2022-June/485498.html
>
It doesn't matter, it seems it's just me who gets ATF1 at address 0.
> It's that the change shouldn't be needed ? Why can one only use the
> first 8K from the 64K INTMEM1 ? Did you find any reason the rest
> shouldn't be writable?
>
Because INTMEM1 is only 8K long in RK3399. 64K is just the length
of the addressing page it's in, but the SRAM is just 8Kb in size.
INTMEM0 is 192 Kb, but not INTMEM1
prev parent reply other threads:[~2022-06-03 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 13:17 RockPi4B: spl_load_fit_image() writing past end of buffer & MMC errors Jerome Forissier
2022-06-03 14:58 ` [SPAM] " Xavier Drudis Ferran
2022-06-03 16:02 ` Jerome Forissier
2022-06-03 17:46 ` Xavier Drudis Ferran [this message]
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=20220603174626.GE2817@begut \
--to=xdrudis@tinet.cat \
--cc=a-govindraju@ti.com \
--cc=hs@denx.de \
--cc=jerome.forissier@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=lokeshvutla@ti.com \
--cc=michal.simek@xilinx.com \
--cc=nm@ti.com \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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