NetBurner Community Forum

Hi,

Thanks for your input. The problem was with the printf() function. Just not to reproduce the issue we commented out some of the prints we suspected on and it turned out to be correct. Also we checked that the stack was corrupted for the running task.

Thanks,
Chandan

Tod,
Thanks for your reply. I think you are right that, the memory has got corrupted before the crash.
Do you know any command to check free space on RAM ?

Did you change the default Ticks per second?

Do you have any user written interrupts that are watching timers?

Some thing in your code overflowing at 2560000 seconds?

The default value of Ticks per second is not altered. #define TICKS_PER_SECOND (20)
I will check and let you know if we have ...

What's the history? Is this a new app and it just hit its first 40 days and crashed. Is it an existing app that just started showing this behavior? If so did you make any changes recently? Are you using printf/sprintf or cout/ostringstream? In my experience, most traps trace back to a memory ...

No there are no user written interrupts.

This issue happens if the hardware is running continuously for around 40 days. Hence to check this out, initialized the TimeTick value to 39 days and after 14 hours the same issue happened.

But initializing the TimeTick to 39 days, 14 Hours did not cause ...

The system reboots when UCOS_ENTER_CRITICAL section is called by OSTimeTick() function, which is periodically called by BIOS.

Paul,
As mentioned above, the hardware reboots and according to the Trap information, the last successful instruction executed is UCOS_ENTER_CRITICAL() [OSTimeTick].
Also ...

Upon trying to execute UCOS_ENTER_CRITICAL() the hardware reboots with the following trap information.

------Trap information-----------------------------
Exception Frame/A7 =021A8AC4
Trap Vector =Access Error (2)
Format =03
Status register SR =2504
Fault Status =0C
Faulted PC =020ED4B4 ...