[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [microblaze-uclinux] kernel won't boot



I did a mb-objdump on my kernel and the data on the address after 30000058
is not the same that is actually being written into the sdram.
For instance 
At 30000054 I have a561e000 which is what I have in the sdram
At 30000058 I have b000300a but I have b000300d in the sdram
After that it looks like every thing is moved to the left by 2 spaces for
instance at 30000068  it should be b0003009 but I get in the sdram f0b00030.

I have no idea why the sdram is getting different data after 30000058.  Any
clues anyone?

-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Paul Hartke
Sent: Friday, February 03, 2006 3:02 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx; Hurni Daniel
Cc: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] kernel won't boot

That doesn't look right.  Next thing I would try is to load the kernel into
memory via xmd and then single step to see where things go awry.

mb-objdump the kernel in uClinux-dist/images/image.elf for a listing of the
assembly.

Paul

Quoting Hurni Daniel <hurnd@xxxxxx>:
> After waiting 10 seconds the program counter is at 000000c0.
> It seems like it stays there forever.
>
> Paul Hartke wrote:
>
> >That is the correct value.  An mb-objdump of image.elf lists the
> following:
> >Disassembly of section .text:
> >
> >30000000 <start>:
> >30000000:       94208001        mfs     r1, rmsr
> >30000004:       a421fffd        andi    r1, r1, -3
> >30000008:       9401c001        mts     rmsr, r1
> >3000000c:       b0003014        imm     12308
> >30000010:       31a02020        addik   r13, r0, 8224   // 30142020
> ><_KERNEL_SDA_BASE_>
> >30000014:       b0003013        imm     12307
> >..
> >
> >After waiting 10 seconds or so, do a register read ("rrd") in xmd.  What
> is
> >the program counter value?
> >
> >Paul
> >
> >Quoting Eric Lynum <elynum@xxxxxxx>:
> >
> >
> >>Daniel, I have the exact same problem except my memory contents are at
> >>0x30000000 and I can also read the memory contents and it is also
> >>94208001
> >>but my kernel won't boot.
> >>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/