public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Hobi <daniel.hobi@schmid-telecom.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] kirkwood: CONFIG_SYS_INIT_SP_ADDR wrong?
Date: Wed, 10 Nov 2010 14:57:08 +0100	[thread overview]
Message-ID: <4CDAA4B4.6070703@schmid-telecom.ch> (raw)

Hi Prafulla,

In commit 0b20ed76 (Kirkwood: Changes specific to ARM relocation
support), you set CONFIG_SYS_INIT_SP_ADDR to 0xC8012000 which is
supposed to lie within the internal Security SRAM.

However, the Kirkwood Functional Specification (chapter 2.13 Default
Address Map) and arch/arm/include/asm/arch-kirkwood/cpu.h suggest that
the Security SRAM is mapped to 0xC8010000. Given the size of 2 KiB, the
upper end would be 0xC8010800.

So I am wondering whether the value 0xC8012000 works at all.

In addition, "CONFIG_SYS_INIT_SP_ADDR should point to RAM with enough
space for global data above and enough stack space below", as Reinhard
Meyer points out in:

http://article.gmane.org/gmane.comp.boot-loaders.u-boot/87490

Since you use quite a large print buffer (CONFIG_SYS_PBSIZE > 1 KiB), I
assume something like 0xC8010700 might work.

@Heiko: include/configs/km_arm.h may have the same problem.

Best regards,
Daniel

             reply	other threads:[~2010-11-10 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 13:57 Daniel Hobi [this message]
2010-11-10 14:15 ` [U-Boot] kirkwood: CONFIG_SYS_INIT_SP_ADDR wrong? Heiko Schocher
2010-11-10 14:37   ` Daniel Hobi
2010-11-10 15:02     ` Heiko Schocher
2010-11-10 15:13       ` Daniel Hobi
2010-11-10 15:40         ` Heiko Schocher
2010-11-10 15:46           ` Daniel Hobi
2010-11-10 16:29             ` Albert ARIBAUD
2010-11-10 16:46             ` Heiko Schocher
2010-11-10 17:53               ` Daniel Hobi
2010-11-10 20:13               ` Wolfgang Denk
2010-11-10 20:11           ` Wolfgang Denk

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=4CDAA4B4.6070703@schmid-telecom.ch \
    --to=daniel.hobi@schmid-telecom.ch \
    --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