Hello,
I am definitely having a hard time getting started with Keil development tools. I just received my ULINK 2, plugged it into the MCB1700. It went fine, until I tryed to download the "blinky example" to the LPC1768.
Debugger starts, runs through System_init() then gets out of control : I keep getting "Cannot access memory" on the output window. I have been looking around since I understand that the error is due to an attempt to reach memory locations that are not physically present in the 1768. Yet I have tried several times to configure the target according to the memory specifications of the LPC which are on chip Flash starting at 0x0 to 0x80000 (I have tried lower values as well) and RAM from 0x1000 0000 to 0x1000 8000.
I have tried with different projects, checking various options in the debug/target otpions windows (tried flash and RAM programming, or unchecking caching options for example), but none of these solved my problem, I still get the "cannot access memory" error right after the system_init() routine.
So I am kind of out of ideas at this point, any help/suggestions would be really helpful!
Thanks!
You need to be more specific: * Are you sure you are running the target and not the simulator? * What address seems to cause the problem? Preferably, copy-paste the error message.
Hi Côme MAESTRACCI,
I think you are using Keil MDK v3.50 and RL ARM v3.50 with ULINK 2, but what kind of example projects are you using? It is the example project within KEIL v3.50, or it is the example project from NXP? NXP has at least two software packages as example projects.
I guess that, your system_init() did some improper CCLK/PCLK configuration, after that, ULINK2 failed to talk to MCB1700.
http://www.keil.com/support/man/docs/ulink2/ulink2_errors.htm
ULINK2 User's Guide
Debug
Cannot access Memory Memory on the target cannot be accessed by the debugger. Avoid accessing invalid memory areas on the target system. This message can also be displayed due to the target's debug block being improperly powered or clocked (for example in deep-sleep mode). A lower Max Clock frequency in the Target Driver Setup - Debug dialog might help.