Re: [microblaze-uclinux] Microblaze system freeze

[Michal Simek <monstr@xxxxxxxxx>]

Hi Otto,
> Hello !
> 
> I have a multi-threaded test-application that continuously calls
> setitimer / getitimer along with calls to sem_lock and sem_release. A
> regular application freeze wouldn't surprise me a whole lot, but the
> problem is that the entire system freezes. Ping & console are both dead
> as a rock.

Do you mean you can't ping your board? or only you can't see console output?

> Nothing unusual prints. It just stops, usually in the middle,
> of a printf - printout. Its interesting to note that depending on where
> I add printf:s in the application the application can run for hours or
> minutes.
> 
> I am using the Xilinx Spartan 3E 500 Rev D development board and the
> Petalogixs Xilinx EDK 9.1 reference design. Petalinux RC0.3. Xilinx EDK
> 9.1.02i w/ "tactical" patch.
> 
> Dhrystone tests ran for hours w/o problem so I don't think its a
> hardware problem...
> 
> Anyone has any hints on where to start looking ? Can I connect to the
> CPU using the xps hardware debugger to see where it stopped ?

look at log buffer(cat System.map | grep __log_buf) - I recommend you to use
U-BOOT for it - because U-BOOT can show full memory dump - hex and characters.
You can use xmd as well - but only with hex dump. XMD provides you register
access - you can see PC and then you can find in linux dump where is the problem.

> Thanks,
> 
> /Otto
> 
> 
> Here is my proc/cpu_info

:-) /proc/cpuinfo

> CPU-Family:     MicroBlaze
> FPGA-Arch:      spartan3e
> CPU-Ver:        6.00.b
> CPU-MHz:        50.00
> BogoMips:       24.72
> HW-Div:         yes
> HW-Shift:       yes
> Icache:        8kB
> Dcache:        8kB
> HW-Debug:       yes
> 

Cheers,
Michal Simek

___________________________
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/