Re: [microblaze-uclinux] More details on my problem

[David McCullough <davidm@xxxxxxxxxxxx>]

Jivin Roberto Farina lays it down ...
> No.
> The "DBG: 1" message don't appear and nothing happens after...
> I've tried using both minicom and hyperterminal (to see if there were some 
> stupid configuration error) but both gave the same results.
> I'm following John's advices but 'till now I haven't discovered nothing... :(

Ok,  here are some ideas that you may have already looked at.

1) It doesn't return from the previous printk.  Printk is a nasty
   variable arg function,  quite possibly it corrupted stack of memory
   and crashed on return.

2) The serial driver (in polled console mode) has a bug and is stuck
   waiting for a character to drain or something similar.

3) It crashes in the small bit of code after the first printk,  but that
   seems unlikely as the code is fairly simple.

4) Some nasty memory/HW issue :-)

If you can,  use a debugger to single step it,  otherwise you will
just have to steadily chip away at it.

Cheers,
Davidm

-- 
David McCullough, davidm@snapgear.com  Ph:+61 7 34352815 http://www.SnapGear.com
Custom Embedded Solutions + Security   Fx:+61 7 38913630 http://www.uCdot.org
___________________________
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/