AnsweredAssumed Answered

bf537 lockup

Question asked by devel on Dec 11, 2014
Latest reply on Dec 19, 2014 by devel



The problem is that after around 10-15 hours, it just hangs:

when I arrive in the morning, there is no ping, no crash log on the UART console. When I reboot into u-boot and recover the syslog buffer - it is some random trash.



This is a custom bf537 board on 2014R1 with my kernel module that uses I2C and sport and application that does some TCP/UDP and logging to NAND flash.


I don't know exactly how that kernel module works, but it was ok on uClinux 2008 (yes, I am still porting this this board from 2008 to 2014). I'll try to disable the module completely and test just the TCP/UDP part.


Kernel options are set to panic on oops and lockups. And reboot on panic.

Board does not allow JTAG.


It looks exactly like 2008-09-01 02:11:10     uClinux is dead



The questions is: how do you normally debug such things? How I can get some crash logs?