From: Orjan Friberg <of@flatfrog.com>
To: barebox@lists.infradead.org
Subject: OMAP 3530 arch_shutdown "undefined instruction"
Date: Wed, 26 May 2010 16:48:09 +0200 [thread overview]
Message-ID: <4BFD34A9.6030008@flatfrog.com> (raw)
Hi,
I'm trying to use barebox as both the 2nd and 3rd stage bootloader (boot
ROM being the 1st) on an OMAP 3530 (BeagleBoard).
Every go <address> command in the 2nd stage, regardless of whether I
have uploaded anything to this address or not, is met with a
go 0x80e80000
## Starting application at 0x80E80000 ...
undefined instruction
pc : [<40208b00>] lr : [<40203a34>]
sp : 87bff21c ip : 00000028 fp : 87bffa4d
r10: 00000000 r9 : 00000000 r8 : 87bff64d
r7 : 87bffe44 r6 : 00000002 r5 : 4020b1e8 r4 : 80e80000
r3 : 00000000 r2 : 00000001 r1 : 0000843f r0 : 4020ae50
Flags: nZCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
which is in arch_shutdown:
40208af8 <arch_shutdown>:
40208af8: e3a03000 mov r3, #0 ; 0x0
40208afc: ee073f17 mcr 15, 0, r3, cr7, cr7, {0}
40208b00: e12fff1e bx lr
This is from the 2010.05.0 snapshot, though it seems that code hasn't
changed in the latest trunk (arch/arm/cpu/cpu.c):
/* flush I/D-cache */
i = 0;
asm ("mcr p15, 0, %0, c7, c7, 0": :"r" (i));
This is compiled with the CodeSourcery 2009q1 tool chain.
Commenting out the call to arch_shutdown makes the go command work
without any obvious deficiencies, but that doesn't seem like the right
way to do it.
(I haven't tried the latest trunk as it doesn't compile.)
Thanks for any suggestions,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2010-05-26 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:48 Orjan Friberg [this message]
2010-05-27 9:31 ` Sascha Hauer
2010-05-27 11:03 ` Orjan Friberg
2010-06-08 8:02 Luca Ceresoli
2010-06-10 12:22 ` Sascha Hauer
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=4BFD34A9.6030008@flatfrog.com \
--to=of@flatfrog.com \
--cc=barebox@lists.infradead.org \
/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