Random execution of code after a reset.

[ArvindEdaB]

Hi All,

I think All strange problems are with me...:P:(

After the code is flashed On first power On, the code works fine...

And I start executing some part code by external USART Messages which ends up with an intentional WDGT reset..

Once reset happens...

Code starts behaving in weird manner...

The Execution directly starts executing the "DoSomething" in default without even calling the function....

This is how the Template code is

Code C - [expand]
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
void SomeFunction(void)
{
  Switch( Variable )
  {
      case 1:
           Do Something;
           break;
      case 2:
           Do Something:
           break;
      default:
            Dosomething;
            break;
    }
}

How come this could happen...

Can anyone helpme with this thing??

[betwixt]

We would have to see the full code but usually this happens because some variable isn't initialized. A hardware reset and a watchdog reset are not identical, you should refer to the data sheet to see the state of registers after each occurs.

Brian.

[Aussie Susan]

I second the call to see all of the code (or, preferably, a short but complete code example that demonstrates the problem).
What device?
Can you explain how you are determining where the code starts after a WDT reset?
As the code is 'C', I'm certain that there will be code executed as part of the C runtime that sets things up before the 'main' is called. Are you setting a breakpoint in this startup code or just somewhere in your own code?
Susan

[Easyrider83]

PIC and other 8-bit microcontrollers doesn't support core fault vectors, in case of any troubles with pointers they just getting crazy. That's why learning with arms or linux is better for begginers. You can at least understand where you doing something wrong and stop guessing.