From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH 00/19] arm: add full relocation / cache support
Date: Thu, 05 Aug 2010 11:23:13 +0200 [thread overview]
Message-ID: <4C5A8301.4020204@arcor.de> (raw)
In-Reply-To: <4C5A580E.7060207@denx.de>
Hello Heiko
Am 05.08.2010 08:19, schrieb Heiko Schocher:
>> The board runs through my low level init (so DDR RAM is up) and later on
>> crashes in the first call to memset. I could not further debug this as I
>
> Where is this memset()? The first after low level init is in:
> arch/arm/lib/board.c board_init_f(), do you mean this?
Yes. That was the point it crashed.
> If so, then something must be wrong with your memory setup.
It was at more then one point :-)
> Hmmm... from where did your board boot? I tried it on the tx25
> board, which boots from nand. Do you boot from a NOR flash?
Yes. My board boots from NOR.
> If so you *must* change TEXT_BASE in config.mk (see:
> doc/README.arm-relocation line 45) in your board directory
> to where u-boot starts in flash!
I think I missed that point.
> Ah, yep, this seems to me the reason why it don;t work for you:
>
> found in the patchseries you pointed to
> http://lists.denx.de/pipermail/u-boot/2010-August/074688.html
>
> board/syteco/jadecpu/config.mk
> [...]
> +TEXT_BASE = 0x46000000
>
> change this to
>
> (as in include/configs/jadecpu.h is defined the following:
>
> +/*
> + * FLASH and environment organization
> + */
> +#define CONFIG_SYS_FLASH_BASE 0x10000000
> +#define CONFIG_SYS_MAX_FLASH_BANKS 1
> +#define CONFIG_SYS_MAX_FLASH_SECT 256
> +#define CONFIG_SYS_MONITOR_BASE CONFIG_SYS_FLASH_BASE
> )
>
> +TEXT_BASE = 0x10000000
>
> and try it again.
I did that but the board still failed to boot and crashed at the first
call to memset. So I had a "nice" debug session single stepping through
the code with a lss file in parallel.
The reason it crashed so early was my setup of CONFIG_SYS_INIT_SP_ADDR
which I set to the *beginning* of some 32k internal SRAM. And as the
stack grows downwards it crashed right at the first push instruction.
So, I now have a running system with your patches and greatly improved
uncompressing times of my boot images. We are now able to use compressed
images which was not possible due to boot time restrictions in older
versions. So it would be great if this stuff could go mainline.
Thanks,
Matthias
next prev parent reply other threads:[~2010-08-05 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 10:44 [U-Boot] [RFC][PATCH 00/19] arm: add full relocation / cache support Heiko Schocher
2010-07-29 11:33 ` Detlev Zundel
2010-07-29 11:57 ` Heiko Schocher
2010-08-04 12:17 ` Matthias Weißer
2010-08-05 6:19 ` Heiko Schocher
2010-08-05 9:23 ` Matthias Weißer [this message]
2010-08-05 9:32 ` Heiko Schocher
2010-08-05 12:15 ` Matthias Weißer
2010-08-07 21:41 ` Wolfgang Denk
2010-08-06 8:56 ` Heiko Schocher
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=4C5A8301.4020204@arcor.de \
--to=weisserm@arcor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox