Topic : Failure to program STM32 flash via RLink-Std unit

Forum : ARM

Original Post
Post Information Post
May 17, 2011 - 12:09pm
Guest

I am porting an STM32 firmware project from Keil uVision4 to Raisonance Ride7, but having difficulty programming with the RLink-Std flash programmer. I have previously programmed the project into the same target board/device successfully via Keil uLink. Additionally, I have used this Ride7 installation to build an STM32 Primer2 project and program that device successfully, via the built-in RLink in the handset.

I am using an STM32F103VGT6 processor on a custom board. I can read the RLink serial number, connect to the target and erase the device, but I get an error when trying to program from within Ride7 or RFlasher7. The error message is :

"Error 0x82 reported by plugin: Device Error"

I have searched the Ride7 documentation for error codes, and looked at the Raisonance & STM32Circle Forums for similar error reports. I have not found anything describing a similar issue.

I am running on Windows XP SP3, using :

Ride7 version 7.30.10.0159,
Ride7 Patch version 7.30.10.0169
RKit-ARM for Ride7 version 1.30.10.0356.

My RLink serial number is dngSTD000020487.

Connecting my RLink to the target, my Cortex Driver message is :

IdCode=0x3BA00477
Silicon Revision ID=0x10006430
Option Bytes: RDP=0xA5, All others are 0xFF.

I am using the JTAG-SWD adaptor with my RLink. When I connect the RLink to the PC, the pwr LED is ON, and the busy LED goes ON->OFF.

Can you suggest anything to explain why I can’t get this RLink unit to program?

Regards

John Alexander

Replies
Post Information Post
+1
0
-1
May 17, 2011 - 2:22pm
Raisonance Support Team

Hi,

This is probably the same problem as the one mentioned there:
http://forum.raisonance.com/viewtopic.php?id=3471

For now use the patch referenced in this other thread.
Then when the new release is available, you will not need the patch anymore.

Best Regards,

Vincent

+1
0
-1
May 17, 2011 - 3:21pm
Guest

Hi,

Thanks, applying the patch mentioned in the link solved my issue. I have now programmed the device successfully.

Regards

John