Forum : ARM
| Post Information | Post |
|---|---|
|
August 31, 2010 - 10:55am
|
Hello ! I'm using the JTAG Rlinkv3.3 of my revaStarterkit in order to program and debug my own card with the STM32F103VBT6. It's working well since a long time now but when, with Ride7, I want to program my device and debug it ( when I click on the blue arrow for making and launching the code), I have this message from the OPI Driver "Code size limit exceeded". I would like to know if it is my own STM32F103 who limit the code size ( STM32F103VBT6 so 128 k ) or if it is the rlink v3.3 on the revaStarterKit, and I hope the problem is from the rlink. So I suppose I Have to buy the rlink Pro to program and debug illimiteed code size but I prefer to be sure before that. So if someone can answer me... About the same subject, I would like to know how can I know the code size of my program, there is several .C and .h files, and I don't find in Ride7 where can I see the code size who is programmed in my STM32. Maybe I have to chech the.hex, if someone can help me... Thanks again and I hope to find informations about my problems.. Thanks. Hervé |
Hi,
The RLink from the REva kits are standard RLinks.
That means they are limited in debugging on ARM CPUs. Programming is not limited (unless you are programming as part of a debug session, of course).
To debug large applications, you can either purchase a RLink-PRO, or upgrade your current RLink to PRO.
See the Raisonance website for more information on RLink types, upgrades, features and prices.
The best and normal way to know the size of flash that the application uses is the map file.
You can also look at the hex file if you know how to read it.
Best Regards,
Vincent
Thanks for informations, and I go check the Rlink on your website !
Thanks again for your support
Hervé