Re: [microblaze-uclinux] Odd Microblaze behavior

[Yasushi SHOJI <yashi@xxxxxxxxxxxxxxxxx>]

Hi Rich,

At Tue, 19 Oct 2004 23:51:40 -0700,
Richard Klosinski wrote:
[...]
> Problem.
> Stopping at the first 'a=33', the debugger indicates a = 765. I checked its
> address, and yeap, 765. Stepping to the next 'a=33', a finally = 33. This
> behavior happens all through the code. 

disassemble generated binary, step through one inst. at a time, and
see what's going on.  post dissassembled code to ml if you don't mind,
together with memory status checked with jtag or whatever you used to
check.

btw, stopping _at_ the first 'a=33' means that `a' is not yet
initialized. because you haven't execute store inst. yet. so memory
location for `a' has _some_ data you don't know, which might be 763 at
the time.

hope this helps,
--
          yashi

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