/var/www/restricted/ssh/stm32/www/stm32circle/ STM CircleOS forum / EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Username:     
Password:     
             

Forum
  • Index
  •  » STM32 primer
  •  » EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

# 1   2010-11-22 11:01:48 EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

klamsy
New member
Registered: 2009-10-31
Posts: 2

EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Since a few days I have the new EvoPrimer, and I tried out the device, but i cannot debug a Program. Even if I try the "Hello World" example Programm is debugging/stepping not possible.
There is an Error Message "Opi Driver  Error: Execution out of debug Memory 0x800C20A"  although the User manual allows debugging until Program code 0x0800FFFF

I think a have the newest Versions: Ride7  7.30.10.0159   with Patch 7.30.10.0169 and Rkit Arm 1.26.10.130.
When I read out the RLink Serial Number of the Evoprimer I get: dngP***3432  and Starter Kit limitation  applies: Debug Limited to 32kb

Is the debugging not possible or only my problem? The Manual  and the description says that debugging up to 64kb is allowed with the standard EvoPrimer Version.


Thanks in advance   
Klaus

Offline

 

# 2   2010-11-23 07:34:41 EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

yrt
Administrator
From: Grenoble-France
Registered: 2008-06-11
Posts: 520
Website

Re: EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Hi,

I confirm that EvoPrimer can be debugged up to 64 Kb with standard version.
Did you install your Ride version and RKitARM from the CD image available on this website (resources page) ?

Yves

Offline

 

# 3   2010-11-29 12:38:43 EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

klamsy
New member
Registered: 2009-10-31
Posts: 2

Re: EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Hi,
I have installed the Patch, the CD Image : CD_STM32-Primer_20100909   , and I updated from CircleOS 4.03 to Version 4.1.
Debugging ist only possible without CircleOS up to Adress 0x8008000, I have tested it with an old bigger project(Made with Rlink-Pro), and stepping/debugging  this program behind this limit is not possible with  the Evoprimer. 

Klaus

Offline

 

# 4   2010-11-30 15:45:34 EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

yrt
Administrator
From: Grenoble-France
Registered: 2008-06-11
Posts: 520
Website

Re: EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Hi Klaus,

Sorry, but it seems we forgotten some things in this patch !
It is fixed in the next release of the KitARM, which will be posted in the next weeks.
Meanwhile the release, I have put a beta version (v1.29) on our FTP server : ftp://www.raisonance.com/pub/CircleOS

Yves

Offline

 

# 5   2010-12-07 21:29:17 EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

mikepo
Member
From: USA
Registered: 2010-12-03
Posts: 36

Re: EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

I had the same error message just trying to debug "toggle_with_CircleOS". I can confirm that the latest RKit-ARM posted above solves the problem.
It also fixes the missing examples folders (e.g. folder ..\Examples\ARM\Primer\EvoPrimer" is missing in the 20100909 CD image).

Offline

 

  • Index
  •  » STM32 primer
  •  » EvoPrimer(64 Kbyte debug limitation) STM32E Debugging Problem

Board footer