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'v just started working with a MCB2300 evaluation board with a NXP LPC2368 ARM. I can download the example programs fine, but when I start a new project and build my own code, I get the "ULINK - ARM Error: LPC_IAP2_512.FLX" window, "Cannot Load Flash Programming Algorithm"
I've checked and double checked ALL of the settings in the target options, flash download settings, etc, compared side-by-side with a project that will load, and still no joy!
I've searched through the forum and app-notes, and none of the answers to this problem have been any help.
uVision says this about itself: IDE-Version: µVision3 V3.62c Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2008
License Information: Nate Duffy Shadin Co, Inc LIC=----
Tool Version Numbers: Toolchain: RealView MDK-ARM Version: 3.22a Toolchain Path: BIN31\ C Compiler: Armcc.Exe V3.1.0.934 [Evaluation] Assembler: Armasm.Exe V3.1.0.934 [Evaluation] Linker/Locator: ArmLink.Exe V3.1.0.934 [Evaluation] Librarian: ArmAr.Exe V3.1.0.934 [Evaluation] Hex Converter: FromElf.Exe V3.1.0.934 [Evaluation] CPU DLL: SARM.DLL V3.22a Dialog DLL: DARMP.DLL V1.40 Target DLL: BIN\UL2ARM.DLL V1.40 Dialog DLL: TARMP.DLL V1.40
Does anybody have any idea what I can try to get this thing to work?
thanks,
Nate
You say that you can download some example files with uLink so I would severly compare my Utilities Flash setup with the example code. I'm not familiar with the Eval tools. Do you need to offset your startup? Do you have your memory setup the same as the example code? Once again, look closely at the flash utilities setup in your new project. Can you strip your code to a minimum set and post to see if we can emulate your problem? Bradford
I'M GOING TO GO HOME AND STAB MYSELF IN THE EYE!
Or maybe not...I'd have to take my glasses off to get to my eye, and apparently I can't see well enough with my glases on to see the differance in the JTAG clock setting in options->Debug->Settings, I'd probably end up with the knife in my ear!
The max JTAG clock rate was set a 1Mhz in my new project, 200kHz in the example project that worked. Now that I found the problem, I'm sure I even read about the solution somewhere!
Thanks for your help Al!