My target has an LPC2468 with 8MB external SDRAM. I'm using uVision 3.60 and RL-ARM/MDK 3.20. My application is about 250K in size. When I load my application it runs fine except for the bugs I am hunting down. However when I debug the system the following happens:
1. When I run (without break points) the target crashes. 2. Strangely the GPIO port 0 (LEDs on the target) go on. 3. Setting, clearing or changing direction on these ports using the peripheral window (fast or slow), they even stay on under a hard reset (switch). 4. When I reset and try to re-run, the application does not start. 5. When I stop the code and check its location it has crashed at a memory location which has changed to 0's. 6. When we go out and back into debugging (after very long object code loading time 1min:30sec) the application runs again without being re-loaded (code memory OK again).
This behaviour is not consistent. I have recently upgraded my system to the latest version from 3.15. Also the uLink will not communicate above 100Khz. All other things have been checked including hardware, PSU, changing uLink etc.
Does anyone have any ideas, I've been using the uVision/uLink system for 2 years and never seen this before.
Ian; It appears to be a debugger problem on my end. Tech Support can reproduce my problem with just the simulator and no uLink2. Connecting the uLink2 does not create the problem. It's when I connect to the debugger via uLink that my problem appears. I can see hardware registers change that should not be in that part of the code. Tech Support has bumped the problem up the ladder to the debugger programmers. Hope to hear something soon. Bradford
Al, Got uLink2 yesterday and on initial tests the problem has gone away but I still have to give it a full test. Will let you know.
Ian
Ok it seems that all is OK with my uLink2. So if anyone wants to debug an LPC2468 you can use a uLink. Ian