Forum : ARM
Original Post
| Post Information | Post |
|---|---|
|
August 24, 2014 - 8:13pm
|
I've used my RLink Std for debugging hundreds of STM32F1xx's for over a year. Now I have a STM32F429 based project. My code compiles, but when I push Ctrl-D, got "Multi Rlink debugging requires either RLink-PRO or RKit-ARM Enterprise, OPI Driver Error (231)" message. I have a single Rlink, a single MCU board, a single project opened...what is this multi debugging? I know that Std Rlink has the 64k debug limit. F429 has 192+64kB RAM, but project is below 64kB (until now. I plan to upgrade to Enterprise for using max RAM.). Any clue, how to get rid of this message? |
Hello,
You activated an option that allows you to use several Rlink at the same time.
To remove this option you should uncheck "Filter SN" from the Cortex Debug Options window.
Launch Ride7
Click on Project Options -> Rlink configuration -> Advanced options -> Click here to open options dialog box
remove filter SN from Debugger Selection
Then confirm by OK
I hope it helps.
Best regards,
Thanks Etienne, message gone after unchecking Filter s/n, but I still have issues.
When I push Ctrl-D, SmartReload fires up, flash erasing and programming are successful, Disassembly View window opens up,
but no execution point marker, and Ctrl-F9 doesn't work. On Debug menu Run, Run To, Steps are disabled (grayed) while Start, Reset, Terminate, Stop are active.
My only hint is I've reached the Lite's 64k debug limit.
How to check if I reached the debug limit? Should I got any message when "make", or at Debug start ?
I tried turning on/off Project Prop - LD Linker - Scripts - Start Kit Limited, but still can't debug.
Dear Novak,
The compilation is unlimited for the Rkit-ARM.
If you reach the lite limit in debug, a message window will appear and doesn't allow you to enter in debug mode.
Concerning your issue, I suggest you to make a clean unistall, see at [url]http://forum.raisonance.com/viewtopic.php?id=3643 [/url] for the small application which unistall all Ride7 and Rkits (maybe you didn't install them with the administrator rights).
Then, download and install the latest release of Ride7 and Rkit-ARM you can find at http://support-raisonance.com/extranet/tools/index.php?param=tool__id__7
Best regards,
I've switched to RLink Pro with no limitations, but still can't debug run my project.
I uninstalled normally, then cleaned with Raisonance clean tool, then fresh installed Ride7 7.50.14.0185 and RKit-ARM 1.54.14.0185
I'd send you privately two printscreens (one for good debug run at an STM32F100 project, and another screenshot of my bad F429 project ..or maybe my whole project to investigate if you mail me at .
If compile and smart reload (erasing then programming flash) is successful, can't it be h/w error on SWD connection (this board is a newly designed and seated PCB...can be anything with it) ?
Dear Novak,
Could you send all the following questions/informations to :
- your serial key license or a serial number of an Rlink/dongle
- Did you tried with the example provided in c:\Raisonance\ride\examples?
- The screenshot of the error message
- The steps you followed to raise to encounter the error
- the entire project in a zip format
Thank you
Regards,
I solved finally.
The original error message was because of "Filter SN" option as Etienne said.
The "debug not start" issue was my fault: at startup SystemInit() is called from
system_stm32f4xx.c
Previously I had made a local copy of this "system_stm32f4xx.c", edited clock/PLL settings, but ruined something,
that prevented debug from reaching the beginning of main().
When I replaced my version of "system_stm32f4xx.c" with the original from STM32F4xx_DSP_StdPeriph_Lib_V1.3.0\Libraries\CMSIS\Device\ST\STM32F4xx\Source\Templates
it worked well.