I have a MCB2300 and Ulink2. The demos work fine IN FLASH ONLY. I can not get any of them to work in RAM despite nearly a week of trying everything I know of. A small list of problems:
If the RAM version loads at all ( the ulink2 bombs out at a nerve wracking rate!:-(( the PC is always 0x0000000 and I have to set it manually. This is not the case with my olde Mulit-ICE.
I am using uLink4 with these settings for the Keil demos sourcs: --predefine "REMAP SETL {TRUE}" --predefine "RAM_MODE SETL {TRUE}" with a simple scatter file ER1 == 0x40000000 and DATA at 0x040000xxxx ( depending on code size),
Either the image loads and runs crazyly OR it seems to load but the memory at 0x4000000 is empty. I can fill the mem with memset.
I have tried MAP 0x4000000 0x40007fff READ WRITE EXEC to no avail
Note that if I use the simulator, ( with the exception of PC as above) all seems to work well.
Also, I can not flash with my on prroject files???? Keils work well, mine bombm, even though I have copied the settings exactly in the options ( ie. LPC200 512K etc with RAM add 0x40000000) I always get "cannot wirte to RAM for flash algorithm" etc.
Finally, I can sucessfully load ( via ulink2) and execute in RAM on an other 7TDMI board the image for that board.
Going crazy in Munich RonBarker
Solved most of the problems. The uLink as it comes out of the box is not configured to refelct the proper JTAG clock speed. Deep in the Docs I found this reference. It seems as if the clock on the old board was within the default of the ulink2 hence it worked well.
The quirk of the PC not being set to the RAM start address is still annoying-:))
Finally, there are some significant differences between the c-lib start/setup between uVision 3 / ADS 2.1 and uVision Real View. These were also giving me fits.