Topic : RFlasher7 claims "Wrong MCU DEVICE ID"

Forum : ARM

Original Post
Post Information Post
January 19, 2010 - 9:21pm
Guest

I have correctly specified the device on my board as an STM32F101CBT6.

RFlasher7 (the latest, 7.26.09.0351, with Rkit-ARM for Ride7 1.22.09.0254) correctly connects to RLink ("RLink Serial number is 'dngStd00300126' This RLink can be used for STM3x devices without limitation.")

It correctly connects to my target ("Connection OK. Silicon RevisionID=0x20036410. Option Bytes: RDP=0xA5, USER=0xFF, WRP0=0xFF, WRP1=0xFF, WRP2=0xFF, WRP3=0xFF.")

However, when I select Auto mode / Go! or Erase, I get a failure: "Wrong MCU DEVICE ID: 0x20036410" and subsequent attempts to Connect to the target also fail: "Unable to read IdCode. Please check that the target is connected."

I can get a correct Connect to target by cycling power, but I cannot get this chip programmed. What is the problem here? This is new for me.

Replies
Post Information Post
+1
0
-1
January 19, 2010 - 9:28pm
Guest

Per another of your messages, I tried to run this in a DOS window and got the following result:

C:\Documents and Settings\larrykoen>Cortex_pgm TSTM32F101CBT6 B
Cortex_pgm: software for programming Cortex chips using a RLink as master.
Copyright Raisonance 2009.

(0)
Selecting target: STM32F101CBT6...
(0)
Connecting to RLink... OK
Connecting to target... OK
Silicon Revision Id: 0x20036410.
Option bytes: RDP=0xA5, USER=0xFF, WRP=0xFFFFFFFF

(2)

Blank-Checking Flash... OK
Flash IS blank.

(4)
Closing com with RLink... OK

C:\Documents and Settings\koenigsbergl>

+1
0
-1
January 19, 2010 - 9:35pm
Guest

OK, I'm able to program this using Cortex_pgm in a DOS window:

=================

G:\Engineering Share\Current Product\800>cortex_pgm TSTM32F101CBT6 E P800-0141-1
00.hex
Cortex_pgm: software for programming Cortex chips using a RLink as master.
Copyright Raisonance 2009.

(0)
Selecting target: STM32F101CBT6...
(0)
Connecting to RLink... OK
Connecting to target... OK
Silicon Revision Id: 0x20036410.
Option bytes: RDP=0xA5, USER=0xFF, WRP=0xFFFFFFFF

(2)

Erasing Option Bytes... OK

Erasing flash... OK

(6)
Programming file 800-0141-100.hex to flash... OK

(15)
Closing com with RLink... OK

G:\Engineering Share\Current Product\800>

=================

however I would rather use RFlasher if possible. The above is not an appropriate solution but it does make a viable workaround in a pinch.

+1
0
-1
January 20, 2010 - 9:43am
Raisonance Support Team

Hi,

This is a very strange problem.
Are you using JTAG or SWD?

Please make this test, that will help me understand the issue:
Erase the flash of the device using 'Cortex_pgm TSTM32F101CBT6 E B'.
Then, try to use the 'Program' command in RFlasher to program your hex file to the flash.
Tell me the result of the test.

Best Regards,

Vincent

+1
0
-1
January 20, 2010 - 10:31am
Raisonance Support Team

Hi,

After making some tests, I think that your problem is related to RFlasher being unable to store the options in its temp file...

Please confirm that you installed the software while logged in with a user account that has admin rights.

Please try the connection using this same user account, if the problems you describe have been observed with a different account.

Please try to change the options (target CPU, JTAG/SWD protocol, Option bytes action), close RFlasher and reopen it, and see if the options that you changed are still like you set them, or if they have been put back to their default values.

Please check that the RFlasher7.dbi file is modified whenever you change one of the options. (look at its date)
On Vista, this file is here: (possibly on a different drive)
C:\Users\\AppData\Roaming\RFlasher7\RFlasher7.dbi
On XP it is here:
C:\Documents and Settings\\Application Data\RFlasher7\RFlasher7.dbi

Make sure that you have write access to this folder and its parent, that you are able to create sub-folders and text files there.

Please let me know the results of these tests.

Best Regards,

Vincent

+1
0
-1
January 20, 2010 - 8:49pm
Guest

PLEASE SEE MY INTERLINEAR RESPONSES TO YOUR REQUESTS. -- LK

Please confirm that you installed the software while logged in with a user account that has admin rights.

THERE IS ONLY ONE USER ON MY SYSTEM, "ADMINISTRATOR" WITH MY LOGIN "LARRYKOEN". I PRESUME THAT THIS FULFILLS YOUR REQUIREMENT HERE. -- LK

Please try to change the options (target CPU, JTAG/SWD protocol, Option bytes action), close RFlasher and reopen it, and see if the options that you changed are still like you set them, or if they have been put back to their default values.

RFLASHER ORIGINALLY CAME UP AS SWD AND I CHANGED IT TO JTAG YESTERDAY, THEN CLOSED IT. IT'S STILL JTAG TODAY AFTER REOPENING. TODAY I DID THE SAME WITH THE OPTION BYTES SECTION, CHANGING "LEAVE AS IS" TO "PROGRAM" AND CHECKING "READ-OUT PROTECTION." THESE CAME UP AS I'D SET THEM AFTER CLOSING/REOPENING RFLASHER. -- LK

Please check that the RFlasher7.dbi file is modified whenever you change one of the options. (look at its date)

THE DATE IS THE SAME AS WHEN I EXITED RFLASHER, REGARDLESS OF WHETHER OR NOT I CHANGED AN OPTION. -- LK

Make sure that you have write access to this folder and its parent, that you are able to create sub-folders and text files there.

I AM USING XP. I CAN CREATE SUB-FOLDERS AND TEXT FILES THERE, SO EVIDENTLY I DO HAVE WRITE ACCESS. -- LK

+1
0
-1
January 21, 2010 - 11:43am
Raisonance Support Team

Hi,

Are you using a RFlasher project or not?

If yes, please send us the project and all the associated temp files, especially the dbi file. (zip the whole folder and send it to 'support@raisonance.com')

In any case please send us the complete folder containing the RFlasher7.dbi file in the Windows temp dir that we spoke about in the previous posts.

Best Regards,

Vincent