Freescale 52259, SW Reboot problem

[svl]

Hi
I am struggling with a strange problem, which I hope some of you can help me with. 
I have an old version of uTasker running 1.4 and have been using it for 2-3 years now.
My problem is that now and then I get reports from my customer that the system is not working as expected.
If the problem not is related to setup problem, the solutions are often to cycle the power on the system.
When our customer is uploading a new configuration to our system we always end this with a SW reboot.
And I have several cases where SW rebooting the system many time had no effect.

I have not been able to recreate the problem on my desk, and have no idea of how to do this.
But it looks like the system reboots, but forgets to do not reset memory or its register…
The error that our customer se are:
HTTP server do not working stable.
I/O setting has not change.

Have any of your see something like this? 

Regards
 -Steen

[mark]

Hi Steen

I don't know whether there is any relation but I had a strange effect recently in a project with the M5225x using CodeWarrior V7.1.1. I use this version of CW because it has never shown problems before (whereby some newer ones had some quite nasty compiler problems).

The project that was being worked on/tested seemed fine until once I realised that it was not starting correctly. It was missing a part of the SW initialisation which was being controlled by a SW timer event. When the board was in this state I could reset it and it would always behave the same (missing the part of initialisation in question and so not operate correctly). After a power cycle it would sometimes start working again (usually after removing power for a few seconds).

When in this state I could connect the debugger and see that the SW timer was correctly firing and causing the code that should react to it to be called but this code was not correctly recognising the timer event number - it was using a switch() statement and the case in question was never matched, although the value was OK. I reported this here but, since it is an older CW version, is is more "just for the record": https://community.freescale.com/message/307158#307158

After replacing the switch with a row of if - elses it looked OK. The next day however I had the effect again and saw that also the if statment was not recognising the event number for the same reason. Rather than doing a compare with a fixed value I put the compare value into a variable and compared with that instead and it was finally solved. In this case it became also clear that the compiler was comparing the value with the content of d5 - this register was being set with the correct compare value in assembler but the code leading up to the compare was not actually executing the register load - the code was jumping in 2 lines after the assembler location where the register was loaded and so the result was in fact quite random since the compare was with whatever value the register happend to have in it at the time.

Could it be that your code also suffers from a similar compiler problem that causes an initialisation routine to be missed in some cases?

Regards

Mark

[svl]

Hi Mark

Thanks for your reply.
Your description does to some extend match my problem.
What I also have seen is that GPIO setting is not setup as expectede.
But I have been doing some test and can see that if I upgrade from a special version to the newest version I have made, the system ends up in unexpected error.
For now I have now idea of what to look for, but it is nice to know that there can be something and not just me;-)

Have a nice weekend

-Steen