mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Bringup Barebox on imx8mm
Date: Tue, 25 Jun 2019 09:12:44 +0000	[thread overview]
Message-ID: <c5d05019-b85c-fef8-0097-448da9ebe5bb@data-modul.com> (raw)
In-Reply-To: <CAHQ1cqHAz=ZAbUvThUOo8WcB74CgnoWdSgAEOTy_94TE81zwfQ@mail.gmail.com>

Hello,

The issue is resolved. It was related to the DDR clock init. It was necessary to
initialize the DDR clock before starting ddr_init():


/* DDR clock init*/
writel( 0x3, 0x30384058);
writel(0x11000000, 0x3038a000);
writel(0x11000000,0x3038a080);
writel(0x3, 0x30384054);

Best,
Reyhaneh

On 6/14/19 9:11 AM, Andrey Smirnov wrote:
> On Thu, Jun 13, 2019 at 8:14 AM Yazdani, Reyhaneh
> <RYazdani@data-modul.com> wrote:
>>
>> Hello Everyone,
>>
>> I am trying to bringup Barebox on i.MX8MM-evk.
>>
>> I have followed all the commits related to the i.MX8MQ and added proper files
>> and changes for i.MX8MM-evk board.
>>
>> The problem is Barebox stops at "ddrc_phy_wait_training_complete" function,
>> exactly at sub-function "ddrc_phy_get_message". The read-value from the
>>
>> phy + DDRC_PHY_REG(0xd0004) is not correct, and it remains in while loop.
>>
>> I used the ddr_init and ddrphy_train files produced from mscale_ddr_tool of NXP,
>> and even compared with the value from U-boot. All are similar.
>>
>> Does any body have an idea what would be the problem?
>>
>
> What about DDR PHY firmware? Is it the same as in working U-boot
> image? From what you describe it sounds that DDR PHY is not
> responding, so I am wondering if DDR firmware is running. Also, did
> you check that various memory offsets in, say
> arch/arm/mach-imx/include/mach/imx8-ddrc.h are valid for i.MX8MM and
> are not values that MQ specific? Another thing to debug this would be
> to trace all of the register reads/writes in working U-Boot vs Barebox
> and see what the difference is.
>
> Anyway, just my 2 cents.
>
> Thanks,
> Andrey Smirnov
>

--
Reyhaneh Yazdani
Data Modul AG                            TEL:    +49-89-56017-154
Embedded development                 FAX:    +49-89-56017-119
Linux - Development                      RG: HR-Muenchen B-85591
Landsberger Str. 322 D-80687 Muenchen - http://www.data-modul.com

Vertrauliche E-Mail von / Confidential e-mail from: DATA MODUL AG
Vorstand / CEO: Dr. Florian Pesahl
Vorsitzende des Aufsichtsrates / Chairwoman of the Supervisory Board: Kristin D. Russell
Sitz der Gesellschaft / Registered Office: München
Registergericht / Registration Court: München Handelsregister B 85 591



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2019-06-25  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 15:14 Yazdani, Reyhaneh
2019-06-14  7:11 ` Andrey Smirnov
2019-06-17  8:17   ` Yazdani, Reyhaneh
2019-06-25  9:12   ` Yazdani, Reyhaneh [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=c5d05019-b85c-fef8-0097-448da9ebe5bb@data-modul.com \
    --to=ryazdani@data-modul.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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