We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I'm working with the demo version, so that might be the problem, but I want to ask anyway.
I've got the demo working with a ULINK2 and an LPC1114 target. Another developers' uVision4 screens (which was purchased) can show and modify his LPC1758 peripherals. It looks like most, if not all, peripherals are accessible.
When I try the same thing, the only menu items under the Peripherals/Core Peripherals menu are: NVIC System Control & Config System Tick Timer
Is this because of the demo version of Keil (Ver 4.10), a limitation of the LPC11xx series, or something I have to set up yet?
Thanks.
Tom
If you are trying NXP's examples they have selected Generic Cortex-M0 device but NXP LPC1114 has to be selected from device list.
So in example under "Options for Target" -> "Device" select the appropriate NXP LPC1114 device, and it should all work.
Already did that: selected LPC1114/301.
As I'm using the blinky.c example to experiment with, is there anywhere in the code that could override the setting in the Options/Device selection? A quick search came up with nothing.
The code can't override the device selection. You must select the top item in Project Workspace window and then open options and select the correct device.
The code only affects what instructions the processor (simulated or real) will execute. But the project options affects what settings the tools will see. And the tools must know about the device to know that there are peripherials to handle.
The tools will not bother to check what include file you may have selected in your source file.
As I said, I did the selected the correct part: Alt-F7, Device, highlight LPC1114/301.
Still no joy.
I just tried the same thing and it works.
What peripherals are you able to view?
All that this chip has.
Once more, download NXP examples code.bundle.lpc11xx.keil.zip extract blinky example, change chip and try.
You can also try switching to simulator and try debug.