Hi,
Thanks for valuable inputs.. memset_io() issue got resolved after I invalidated
the L1
data and Instruction cache before calling early_init(was mentioned in some
mailing list
). The code execution resumed and somewhere during MMU_init it again got
struck.This
time its due to a DataTLBError. I am now trying to trace the function causing
TLB miss
using ICE Trace32. Any pointers for reason behind generation of DataTLBError
during MMU_init
Thanks
Deepak Gaur
On Mon, 7 Apr 2008 13:50:04 -0600, David Baird wrote
On Mon, Apr 7, 2008 at 10:04 AM, Scott Wood [EMAIL PROTECTED] wrote:
BTW, it's generally bad form to post the same question repeatedly. If you
have new information regarding your problem, just post a followup in the
same thread containing the new information.
Agreed! I was about to respond to your new post, and then I
discovered this nearly identical slightly older post.
On Mon, Apr 7, 2008 at 12:37 AM, Deepak Gaur [EMAIL PROTECTED] wrote:
While booting MVL linux on MPC8560 based board the kernel goes into a
infinite loop in setup.c
Someone please correct me if I am wrong, but those symbols inside the
BSS should only be variables (not functions) which are initialized
to zero. The whole reason for BSS is to initialize variables to a
0/null value.
Now, about the infinite loop. Can you check to see if perhaps you are
getting an exception?
I have no experience with the MPC8560, but I've seen a couple problems
that occur involving memset_io. What happens is that a TLB miss
exception occurs when the CPU gets inside of memset_io. Do you have
the ability to check that with a debugger (by setting breakpoints at
exceptions, such as the data and instruction TLB miss exceptions) to
see if you are getting exceptions?
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Deepak Gaur
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
