From: Marek Behun <marek.behun@nic.cz>
To: u-boot@lists.denx.de
Subject: latest u-boot branch for Marvell Armada 88F3720
Date: Thu, 2 Apr 2020 15:52:50 +0200 [thread overview]
Message-ID: <20200402155250.2b961996@nic.cz> (raw)
In-Reply-To: <6967c2d3-0072-fdc2-c861-2d97957243c1@denx.de>
On Thu, 2 Apr 2020 14:18:24 +0200
Stefan Roese <sr@denx.de> wrote:
> Hi Moritz,
>
> On 02.04.20 13:30, Moritz Berghof wrote:
> > it's really great that you answered so fast and helpfully, thank you!
> >
> > It's great you want get the board ported to mainline. Me too.
> >
> >
> > I build the U-boot mainline and uploaded on my espressobin. Used the ATF
> > and WTMI from Marvell.
> >
> > When I start the flashed .bin file, the U-boot crashed at this following
> > point. "Synchronous Abort" handler, esr 0x96000210
>
> Looks like an issue with SATA - not sure why. You might want to try to
> disable SATA / AHCI for testing.
>
> > Prompt is attached at this mail.
> >
> > I think there is a problem with the RAM. For example, I build the U-Boot
> > for 1 GB RAM with the Marvell U-boot and the mainline/master. Important
> > constant is DDR_TOPOLOGY=2
> >
> > make DEBUG=0 USE_COHERENT_MEM=0 LOG_LEVEL=20 SECURE=0 CLOCKSPRESET=CPU_1000_DDR_800 DDR_TOPOLOGY=2 WTP=... BOOTDEV=SPINOR PARTNUM=0 PLAT=a3700 all fip
> >
> > But when the u-boot mainline starts it promts:
> > U-Boot 2020.04-rc3-00188-g350c44dfb9 (Mar 31 2020 - 10:52:01 +0200)
> >
> > DRAM: 512 MiB
> >
> >
> > The Marvell U-boot promts DRAM: 1 GiB
> >
> >
> >
> > So my question is, where do you define the RAM Size?
>
> Take a look at arch/arm/mach-mvebu/arm64-common.c. Perhaps this code
> needs some changes for CONFIG_ARMADA_A3700 similar to what is done
> for CONFIG_ARMADA_8K ?
>
> I suggest you debug in this area a bit to see, where it goes wrong.
There is a register on A3720 which should contain information about how
much RAM the system has (0xD0000200 if the device contains only one
DDR chip). It is written by the TIM image. I am going to send a patch
which uses this register to determine RAM size for Turris Mox.
The thing is that without upgrade of TIM header some Moxes may report
1 GB RAM in this register, although they only have 512 MB. So a call to
get_ram_size will still be needed.
Marek
next prev parent reply other threads:[~2020-04-02 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 15:05 latest u-boot branch for Marvell Armada 88F3720 Moritz Berghof
2020-03-25 16:44 ` Stefan Roese
2020-03-25 17:48 ` Marek Behun
2020-03-25 17:57 ` Marek Behun
2020-04-02 11:30 ` AW: " Moritz Berghof
2020-04-02 12:18 ` Stefan Roese
2020-04-02 13:52 ` Marek Behun [this message]
[not found] <VI1PR05MB499206310103F9B5AD6713E3A6C70@VI1PR05MB4992.eurprd05.prod.outlook.com>
2020-04-03 18:43 ` Marek Behun
-- strict thread matches above, loose matches on Subject: below --
2020-04-06 9:43 AW: AW: " Moritz Berghof
2020-04-14 23:52 ` Marek Behun
2020-04-21 10:25 ` AW: " Moritz Berghof
2020-04-21 11:11 ` Marek Behun
[not found] ` <VI1PR05MB4992654399B1405165482C47A6D20@VI1PR05MB4992.eurprd05.prod.outlook.com>
2020-04-22 9:12 ` Marek Behun
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=20200402155250.2b961996@nic.cz \
--to=marek.behun@nic.cz \
--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