Its very bad programming style to solve not the old problem.

Then naturally it is absolutely clear, that you immediately step into the next problem.

Seems you want no success.

At first you must look on the map file, how many memory was used. Then also watch on the stack on the simulation.

It seems for me, you have tons of global variables and thus the memory explode.

Also a good debugging method was to set a pin (LED) before and another pin after a certain piece of code. So you can exactly isolate if this code was executed or not..

But at first solve any problem, which you see, before you continue the code developing !!!



Peter


P.S.:
Another reason can be, you selected the large memory modell, but there is no external memory connected or enabled.
Then naturally the simulation works fine, because the external memory was simulated.