Hello, I was looking for some clarification about the evaluation limitations for the ARM-MDK tools. My development board is a Keil MCBSTM32E, my debugger is a ULINK2, the uVision3 version is 3.72 and the MDK-ARM version is 3.40. I have found that some demo programs compile fine, but exceed the debug limit (ULINK2 or Simulation).
At first glance (http://www.keil.com/demo/limits.asp) it appears that both the compiler and debugger are limited to 32K with the knowledge the there will be 16K additional padding to ensure that you can't use a small device. What I have found is that the compiler is limited to 32K, but the debugger is limited to 16K. For the "Measure" demo project, the Code=11418, RO=22762 (including the 16K padding), and RW=60 for a total of 34240. This seems reasonable since the program compiled to 17856 + 16384 padding. This will download into flash and run fine. The problem comes when trying to debug it. The output says "Restricted Version with 32768 Byte Code Size Limit, Currently used: 34240 Bytes (104%)". My problem is that this includes the 16K of padding.
My conclusion is that the compiler is limited to 32K, but the debugger is limited to 16K (of actual, usable Code+RO+RW). Could someone please provide clarification on this issue? Why can I only debug half of my potential to compile (especially when the demo limit is exceeded due to LCD constants in the included demo program)?
Thanks for your help, Greg C.