All of lore.kernel.org
 help / color / mirror / Atom feed
From: ba_f <ba_f@rbg.informatik.tu-darmstadt.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot version issue
Date: Mon, 12 Oct 2015 15:52:28 +0200	[thread overview]
Message-ID: <5167cf5319666ef3c0df793c9d1db0ea@rbg.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <CAPnjgZ1VENyQ4Osj81BqTQgWS72MihRgk6hNZMzb_0RGR_m+Rw@mail.gmail.com>

Am 2015-10-09 15:02, schrieb Simon Glass:
> +Marcel who is the maintainer
> 
> Hi,
> 
> On 8 October 2015 at 14:56, ba_f <ba_f@rbg.informatik.tu-darmstadt.de> 
> wrote:
>> 
>> Hello,
>> 
>> 
>> i have an issue with different U-Boot versions, and i have no clue 
>> what's
>> the problem.
>> Maybe someone's got an idea?
>> 
>> Working on Xilinx' ARM Platform i use U-Boot version
>> u-boot-xlnx-xilinx-v14.6.01, and it's all good with that one and even 
>> lower
>> versions.
>> But, using u-boot-xlnx-xilinx-v14.7 or higher results in serious CPU 
>> errors:
>> 
>> uboot> fatload mmc 0 0x00ffffc0 bootstrap.uimage
>> reading bootstrap.uimage
>> 6139968 bytes read in 528 ms (11.1 MiB/s)
>> uboot> go 0x01000000
> 
> What is that bootstrap program? Maybe you need to turn off the cache
> before starting it with the 'dcache off' command?
> 

Indeed DCache is the problem.

The old u-boot had CONFIG_SYS_DCACHE_OFF=y.



Thanks,
ba_f

      parent reply	other threads:[~2015-10-12 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 16:22 [U-Boot] ## Application terminated, rc = 0x1 ba_f
2015-09-23 23:23 ` Nable
2015-09-24  5:55 ` Wolfgang Denk
2015-09-29 13:49   ` ba_f
2015-09-29 16:13     ` Wolfgang Denk
2015-09-29 16:15     ` [U-Boot] "go" does not work for uImage - was: " Wolfgang Denk
2015-10-08 13:56       ` [U-Boot] U-Boot version issue ba_f
2015-10-09 13:02         ` Simon Glass
2015-10-09 13:22           ` Michal Simek
2015-10-12 13:52           ` ba_f [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=5167cf5319666ef3c0df793c9d1db0ea@rbg.informatik.tu-darmstadt.de \
    --to=ba_f@rbg.informatik.tu-darmstadt.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.