Note: I already tried the solution on "http://www.keil.com/support/docs/3561.htm" (update to latest version then add patch).
I had a working project for one processor (LM3S9B95) and migrated over to another one of the same family (LM3S5P36). I chose the new chip. I adjusted the SRAM size/range and flash size/range in "target driver setup \ Flash Download" window. I changed the program range in the "*.sct" file.
When attempting to load program, popup says "Cannot Load Flash Programming Algorithms", and build output says "Cannot Write to RAM for Flash Algorithms". Press OK then popup says "Error: Flash Download Failed - "Cortex-M3"" and build output says "Erase Failed".
I can detect the debugger interface in the "target driver setup \ Debug" window (0x2BA01477 ARM CoreSightSW-DP).
Pressing the "debug" icon makes the software go into debug mode with no errors indicated.
I am able to load programs onto the previous board so the debugger is fine.
I was even able to load the current project for the NEW chip onto the board with the OLD chip (after adding an offset of 0x1000 to the ROM load region(LR_IROM) in the *.sct file to compensate for an issue with that chip. Otherwise, the second error message above appears).
The only anamoly is that "Driver DLL" and "Dialog DLL" fields (and their "Parameter" fields) were left blank when I chose the new chip. Usually they are filled with values that depend on what you choose and the instructions say to never edit these values. I simply filled in the values from the last project and changed the "Parameter" appropriately (-pLM3S9B95 -> -pLM3S5P36).
I've used uVision for several processors of 3 different families at this point but have never encountered these particular symptoms.
Am I missing something obvious or should I give up on a software solution and do more debugging on the board itself?
Hi,
> Cannot Write to RAM for Flash Algorithms
The LMI devices like(d in the past) to lock themselves out from JTAG/SW randomly, this can be solved in most cases by downloading the LMI Flash Programmer from the TI Homepage (registration required), and then, on the last TAB of that programm, select "Unlock". This only works with the on board FTDI and this programm, per USB.
. BR, /th.
Already tried the unlock sequence (by soldering in some extra leads to a Luminary development board). It DOES reset the JTAG (as does turning the board off & on) and I can use it to program the chip, but I still can't program or debug with Ulink2 (which we paid $500 for).
Ok,
so please raise a support request on http://www.keil.com
Already did. I was just hoping that someone might have already had experience with this exact chip so they could either tell me how they got it to work, or in the case that they had no problems, just post the uVision version & settings they used.
It Works!!!
After over an hour on the phone with tech support, they suggested (after they read through the chip's errata) that I try setting "Reset:" (in Options \ Debug \ Settings \ Debug) from "Autodetect" to "VECTRESET".