STM CircleOS forum / Execution out of debugging limittion: PC=0xFFFFFFFE

krzysiu19 · 2009-11-09 00:41:00

Hello. I'm using Primer 2 without Circle OS. When I want to debug Ride displays weird looking error :

OPI driver
Execution out of debugging limittion: PC=0xFFFFFFFE.
And then I can't debug the program

Do you have any information how to deal with this type of error?

VincentC · 2009-11-09 08:57:16

Hi,

First, please make sure that you are using the latest versions of the Ride7 _and_ RKit-ARM kits. If not, please update them. (if you installed from the CD, then they are both obsolete)

If the problem persists, the first thing to do is determine if this is related to your application or to your hardware. To know this, please try to debug this Ride example:
<Ride>\examples\ARM\Primer\STM32Primer2\toggle\toggle.rprj

Depending on the results of this test, I will have other questions.

Best Regards,

Vincent

krzysiu19 · 2009-11-09 09:30:24

I've built this demo and there was no problem in debugging it. My program has only few lines and I'm using STM32 firmware library.

VincentC · 2009-11-09 09:51:10

Hi,

Please tell us the versions of the kits that you are using, or send a screenshot of the "help"->"about" window.

Best Regards,

Vincent

krzysiu19 · 2009-11-09 12:56:51

Ride7 ver 7.24.09.0251
RKit-ARM for Ride7 ver 1.22.09.0254

VincentC · 2009-11-09 15:19:16

Hi,

Thanks for the information.

So the problem is related to something in your application.

This message appears when the PC of your application goes outside the debug limitation.
That can happen in many cases, the most common being...

1. Your application is larger than the demo limitation. (doesn't seem to be your case)

2. There is a wrong interrupt vector that sends the PC in the wild.

3. A stack corruption occurred. (resulting usually from a wrong pointer manipulation, local buffer overflow, or stack overflow)

4. An indirect function call (usually through function pointer) was not written properly.

Please inquire in these directions. If you don't find the problem, please send an application showing the problem to 'support@raisonance.com' .

Best Regards,

Vincent

krzysiu19 · 2009-11-09 16:25:59

Ok I will try to check if everything is alright and I will send you feedback if manage to solve the problem. Thanks a lot!

dine909 · 2010-03-24 23:04:26

I too have this problem, i can compile the toggle and debug it successfully, and my project is way under the debug limitations.

I have spent days upsizing my code so its compatible with the latest Ride installation and libraries - and it made no difference, i have re-created my project until i'm blue in the face to no avail, i have removed everything apart from my empty main() and still get the problem......

Is there a fix for this or is it time to move platform?

cheers!

-- UPDATE --

I just found a workaround - copy the toggle project, remove main.c and add your project files and set up the include directories - appears to work perfectly..

So i'd say this is a possible problem with the saved project/compilation settings - i have compared them field for field and they are identical..

Last edited by dine909 (2010-03-24 23:27:56)

# 1 2009-11-09 00:41:00 Execution out of debugging limittion: PC=0xFFFFFFFE

Execution out of debugging limittion: PC=0xFFFFFFFE

# 2 2009-11-09 08:57:16 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 3 2009-11-09 09:30:24 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 4 2009-11-09 09:51:10 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 5 2009-11-09 12:56:51 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 6 2009-11-09 15:19:16 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 7 2009-11-09 16:25:59 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

# 8 2010-03-24 23:04:26 Execution out of debugging limittion: PC=0xFFFFFFFE

Re: Execution out of debugging limittion: PC=0xFFFFFFFE

Board footer