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; I have no real suggestions at this time. I'm having a few similar problems on my MCB2300 board with the LPC2378. My program is much smaller than yours. I stripped my code to the bare minimum and fired it off to tech support. We are still reviewing the problems. Mine appeared as I was attempting to debug an interrupt routine while connected to the uLink2. No interrupts. After much thrashing around, I disconnected the uLink2 and reset. Code worked perfectly. Attempted to simulate small amount of code but I was unable to create the interrupt. Attempted to run my target board via debugger. No joy there. I'm running the same toolset that you listed. I can function with the uLink connected. I just can't use the debugger with uLink. I can download with uLink2 up to 500KHz. I have dropped to 100KHz but no change in the symptoms. My debug efforts at this time consists adding in LED blinks at portions of my code and just using the uLink to download. I will get my USART up soon and use printfs to give me additional debugging. I'm hoping that tech support will find some error in my code. As I said, I can offer no advice, just let you know that someone else is having Debugger problems with V3.20. Bradford
Al, thanks for your posting. Since my first post Keil have suggested that it could be the speed I'm communicating with the uLink at, the slow speed could be a problem. Also they don't seem to happy with my uLink and have suggested uLink2 which I should have tommorow. Its always the way with any technical support "upgrade everything first" so if it solves my problem all our uLinks will be hitting ebay. I noticed that you are using a uLink2, if that is the case it does not seem to be solving your problem. I noticed you said you dropped the speed maybe try to set the JTAG Speed to RTCK (Adaptive Clock)? I'll let you know how things go when I get the uLink2 (TNT pre 12AM). Ian
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