From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can't boot DaVinci EVM with Green Hills' Integrity OS
Date: Tue, 31 Mar 2015 09:03:22 +0200 [thread overview]
Message-ID: <551A46BA.60902@myspectrum.nl> (raw)
In-Reply-To: <CAHaVubr+O+ZSrhOAbn-idHghjxm9ruoUKd+wi7E9jsxkWMcOow@mail.gmail.com>
Hello Idan,
On 31-03-15 06:02, Idan Noti wrote:
> Why do you think caches have something to do with the problem?
By booting the image with the bootelf command you jump to it with some
caches
still enabled / not flushed (which is likely not what your debug
interface does and
your kernel might not really like that). A FreeBSD kernel doesn't /
didn't at least and
wouldn't boot.
I never checked, but I guess Linux doesn't like it either, but since it
is typically booted
by a bootm / bootz command it goes through e.g. arch/arm/lib/bootm.c,
which calls
cleanup_before_linux in arch/arm/cpu/arm926ejs/cpu.c, all caches are
disables and
flushes before jumping into it.
Of course I don't know if this is related to your problem, but it cannot
do any harm to
keep caches off until you have the board properly booting.
> Also, how do I config the compilation to disable caches? The only
> configuration I'm aware about it modifying the header file:
> $(uboot_folder)/include/configs/davinci_dvevm.h
Yup, see README and doc/README.arm-caches. At least below knobs are
documented.
You can simply define these in mentioned file.
CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
Regards,
Jeroen
next prev parent reply other threads:[~2015-03-31 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 18:44 [U-Boot] Can't boot DaVinci EVM with Green Hills' Integrity OS noti1234
2015-03-30 21:09 ` Jeroen Hofstee
2015-03-31 4:02 ` Idan Noti
2015-03-31 7:03 ` Jeroen Hofstee [this message]
2015-04-02 4:21 ` Idan Noti
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=551A46BA.60902@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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