public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem with sf write on Arria 5.
Date: Wed, 30 Mar 2016 21:57:11 +0800	[thread overview]
Message-ID: <1459346231.1960.7.camel@altera.com> (raw)
In-Reply-To: <BFEE4BD273371E48B6EB70F96CEC5B54040F0BF5@DEMUMBX007.nsn-intra.net>

On Wed, 2016-03-30 at 13:46 +0000, Bakhvalov, Denis (Nokia -
PL/Wroclaw) wrote:
> Hi Marek,
> 
> > Do "dcache off" and then update the flash again, it will work.
> > That's
> > the cache issue which we cannot track down.
> 
> Thank you for you quick support!
> 
> Maybe it's worth to invent a temporary solution?
> Because in other way users will face problems which are hard to find
> (I've been chasing this problem for 2 days).
> For example execute "dcache off" internally when sf write is called?
> 

I believe we can turn of the dcache as default for socfpga while effort
in progress to figure out the issue.

FYI, I was experimenting with L2 cache PL-310 registers but not
successful. I am trying to understand any issue between L2 cache and
the SDRAM. There is l2 cache sync after a flush but seems its not
working fine. Adding delay works but that not deemed a correct solution
(for USB case). Probably doing a virtual memory aliasing might
understand where the data was stuck.

Thanks
Chin Liang


> Best regards,
> Denis Bakhvalov

  reply	other threads:[~2016-03-30 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 11:14 [U-Boot] Problem with sf write on Arria 5 Bakhvalov, Denis
2016-03-30 12:46 ` Marek Vasut
2016-03-30 13:46   ` Bakhvalov, Denis
2016-03-30 13:57     ` Chin Liang See [this message]
2016-03-30 13:58     ` Marek Vasut
2016-04-05 22:04     ` Marek Vasut
2016-04-07  7:32       ` Bakhvalov, Denis
2016-04-07 10:57         ` Marek Vasut
2016-04-07 12:05           ` Bakhvalov, Denis
2016-04-07 12:21             ` Marek Vasut
2016-04-08 23:07               ` Bakhvalov, Denis
2016-04-08 23:13                 ` Marek Vasut

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=1459346231.1960.7.camel@altera.com \
    --to=clsee@altera.com \
    --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