linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Rutsch <orutsch@sympatec.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: TQM8349 and ARCH = powerpc
Date: Fri, 12 Sep 2008 10:11:41 +0200	[thread overview]
Message-ID: <48CA243D.8020701@sympatec.com> (raw)
In-Reply-To: <20080910092631.07d5c1cc.kim.phillips@freescale.com>

Hi,

> On Wed, 10 Sep 2008 16:12:22 +0200
> Oliver Rutsch <orutsch@sympatec.com> wrote:
> 
>>    model = "tqc,tqm834x";
>>    compatible = "tqc,tqm834x";
> 
> you need a arch/powerpc/platforms/83xx/tqm834x.c file that matches this.
> 
> Kim

O.K. I read "booting-without-of.txt" the third (or fourth?) time and
so I made the entries for this board in the KConfig and the Makefile
and I created tqm834x.c, which is essentially a copy of mpc834x_itx.c.
As I did not found any board specific details, the most significant
change is the of_device_id:

static struct of_device_id tqm834x_ids[] = {
	{ .type = "soc", },
	{ .compatible = "soc", },
	{ .compatible = "simple-bus", },
	{},
};

I hope that this is correct.
And so I selected the board and the kernel just compiled fine. But the
result was always the same. So I warmed up my BDI2000 and debugged
the kernel. I can stop the kernel in the "start_here" function but
it seems to run wild after line 1012. As the kernel dies at a
very early stage, I don't think that it is device tree related.
Here's my gdb session:

-----------------------------------------------------
start_here () at arch/powerpc/kernel/head_32.S:1011
1011            lis     r1,init_thread_union@ha
(gdb)
start_here () at arch/powerpc/kernel/head_32.S:1012
1012            addi    r1,r1,init_thread_union@l
(gdb)

Program received signal SIGSTOP, Stopped (signal).
0x000006fc in ?? ()
(gdb) bt
#0  0x000006fc in ?? ()
#1  0x000003e0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) si

Program received signal SIGSTOP, Stopped (signal).
0x000012fc in ?? ()
(gdb)

Program received signal SIGSTOP, Stopped (signal).
0x000006fc in ?? ()
-----------------------------------------------------

Then it toggles between 0x6fc and 0x12fc. These addresses
look totally wrong.

As always, all ideas are welcome.

Thanks for all suggestions so far!


Bye,
-- 
Dipl. Ing. Oliver Rutsch
EMail: orutsch@sympatec.com

  reply	other threads:[~2008-09-12  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 14:25 TQM8349 and ARCH = powerpc Oliver Rutsch
2008-09-09 16:22 ` Kim Phillips
2008-09-10  6:06   ` Oliver Rutsch
2008-09-10 14:12   ` Oliver Rutsch
2008-09-10 14:26     ` Kim Phillips
2008-09-12  8:11       ` Oliver Rutsch [this message]
2008-09-12  0:36     ` David Gibson
2008-09-09 18:31 ` 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=48CA243D.8020701@sympatec.com \
    --to=orutsch@sympatec.com \
    --cc=Linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).