From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot for SPEAr1310
Date: Thu, 23 Feb 2012 16:22:27 +0100 [thread overview]
Message-ID: <201202231622.28128.sr@denx.de> (raw)
In-Reply-To: <201202231549.02184.marek.vasut@gmail.com>
On Thursday 23 February 2012 15:49:02 Marek Vasut wrote:
> > My experience is mostly SPEAr600 only right now. Not sure if there are
> > bigger differences between those SoC's in the BootROM.
>
> I believe the spear600 is totally different from 1300. But, simple:
>
> reset halt ; load ... ; go ...
>
> combo should work I believe. In case you're loading some U-Boot SPL, it's
> very good idea to put an "asm volatile("x : b x");" line into the SPL to
> make the CPU loop instead of try loading uboot. Since if the CPU is
> looping, you can break it with BDI, if it isn't looping and jumps to some
> garbage, it usually ends in undefined state and bootrom might further
> tamper with the CPU configuration.
Yes, good point. But a "STARTUP RESET ;no code is executed after reset" seems
to solve this problem as well. At least for me on SPEAr600. I know. Since I
broke my SPL from time to time. ;)
Best regards,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2012-02-23 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 14:17 [U-Boot] u-boot for SPEAr1310 Pavel Machek
2012-02-23 14:42 ` Stefan Roese
2012-02-23 14:49 ` Marek Vasut
2012-02-23 15:22 ` Stefan Roese [this message]
2012-02-23 15:24 ` Marek Vasut
2012-02-24 18:16 ` Pavel Machek
2012-02-24 18:36 ` Stefan Roese
2012-02-27 2:34 ` Vipin Kumar
2012-02-24 18:37 ` Marek Vasut
2012-02-24 18:46 ` Stefan Roese
2012-03-15 11:46 ` Pavel Machek
2012-02-24 2:11 ` Vipin Kumar
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=201202231622.28128.sr@denx.de \
--to=sr@denx.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.