Topic : Connecting the debugger to the target

Forum : Ride IDE

Original Post
Post Information Post
September 17, 2009 - 12:57am
Guest

Hi All

When I debug on the target in FLASH the debugger always first builds the project and then reprograms the FLASH memory.
Is there a way to configure it to connect to the processor without actually performing a download each time?

Usually there is a configuration for this or a command to "connect", which is also useful for connecting a debugger to a running system so that break points can be set or it can be paused without first having to do a reset.

Regards

Mark

Replies
Post Information Post
+1
0
-1
September 17, 2009 - 9:37am
Raisonance Support Team

Hi,

There is no such option for now. It is in the TODO list.

Best Regards,

Vincent

+1
0
-1
September 28, 2010 - 12:19pm
Guest

It is a good suggestion - Mr. mjbcswitzerland. I kindly ask for this together with you.

I guess it wouldn't be difficult to add a simple option not to reprogram the target. Just to omit this stage. Debugger would trust the operator that nothing has changed since last compilation.

It is very useful when I debug not the u_controler itself but the rest of PCB... the environment.
And every time I must observe the flash being reprogramming. The limit is 1000 or 10000 but ....

I kindly insist.
Please

Robert

+1
0
-1
October 1, 2010 - 12:01pm
Raisonance Support Team

Hi,

The current version of the RKit-STM8 allows to skip the erasing and programming phases for STM8. (not ST7)
The next version of the RKit-ARM will provide the same option for Cortex. (not ARM7 nor ARM9)

Whether or not we do that for other targets will depend on customer requests... Please always specify which target CPU(s) you are working with when posting in this forum.

Adding an option for starting debug without resetting (hot plug) is much more complex and will not be available in the short term. Still, I'm interested in knowing which target CPUs you are using, in order to plan those things ahead...?

Best Regards,

Vincent

+1
0
-1
November 26, 2010 - 9:18am
Guest

Hi, i also would appreciate very much this feature. I have asked for this back in 2009. Additional it would be very helpful that not all of the flash is being erased when downloading the program. This way it would be possible to preserve calibration settings or similar important data which is stored in defined flash sectors outside the program sectors. I am using Rkit-ARM 1.26.10.0130. My target is a STM32F103ZEH6. Regards, Christian

+1
0
-1
December 12, 2012 - 2:31pm
Raisonance Support Team

Hi,

Better late than never, the latest version of RKit-ARM (1.46) allows to disable Reset (and Erase and Program, as before) before debugging Cortex devices. Enjoy! ;)

It also contains a new SmartReload option for reprogramming only if the code has changed. Some people will gain much time with this one. :)

See the GettingStartedARM doc for the details about these new options.

We plan to implement the partial erase in one of the coming releases, hopefully during the first quarter of 2013. (still for Cortex only)

Whether or not (and when) we do all this for STM8 will depend on customer feedback about these features for Cortex, and on customer requests for these features on STM8. You can send this feedback and requests by replying to this post.

Best Regards,

Vincent