But I am getting this error : WRONG MCU Device ID : 0x10006430
After that I am not able to see even the defualt MENU of the primer on the screen. Can i flash it with the factory image.Where Can I found it? Kindly assit.Really looking fwd to get the assistance on this.
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
it says : (0) Configuring RLink Driver ... OK Connecting to Rlink ... OK Cionnecting to target ... !!! Error 203 : Wrong MCU DEVICE ID : 0x10006430 . Do I have to change some setting ! Rgds, softy
" Pain is temporary, Quitting Lasts for ever"
Offline
#
5
2012-12-04 14:32:48STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi Vincent, Thanks for the reply. I found that the Device I am having is evo_primer (same as OP4 I guess).I am creating the project for evo primer (plz see the attachment) STM32E_Evo_CircleOS
RLink Sno. is : dngP00000001881 (see the attachment)
When I opened the Menu > About , I get the following on the LCD screen :
STM32E Open 4
CPU : STM32F103VET6 OS : V 4.03 225 KB App : 11 218 KB Avail FLASH : 69 KB
I can see another STM32 (visible) on the device that is STM32F103VGT6 P .Are there two MCUs (STM32F103VET6 and STM32F103VGT6 ) .Which one is target .I am confused on this?
Last edited by softy (2012-12-05 04:31:10)
" Pain is temporary, Quitting Lasts for ever"
Offline
#
7
2012-12-05 08:55:20STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi,
Thanks for the information. You have an EVO-Primer, which is indeed the same as OP4, but different from Primer2.
Indeed you have two STM32 MCUs in this product:
The STM32F103VE that is inside the OP4 base (under the LCD) is the embedded RLink. It allows to program the other STM32. Don't try to reprogram it or your OP4 will become unusable. Just forget about the fact that it is an STM32 and close the base with the screws. There should be no need for you to open it n the future, except maybe for inserting an extension board.
The STM32F103VG that is on the daughterboard is the target. This is the one you will work on.
The LCD probably displays "STM32F103VE" because you tried to program the Primer2 default flash image. But it's the STM32F103VG that controls the LCD at this point. Please try to restore the correct default: Restore_EvoPrimer_STM32G_Circle_Factory.bat
Then it should be better. Make sure you have the latest Ride (7.42) and RKit-ARM (1.46) before that.
Best Regards,
Vincent
Offline
#
8
2012-12-05 09:10:05STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi Vincent, Thanks for the answers.It explains a lot. I have downloaded Primer_Upgrade v4.32 for evo_primer (last updated 09/19/2012 ) from this page - >
I extrcated it and it gaveme this folder - > EvoSTM32G_upgrade and double clicked this Restore_Evo_STM32G_Circle_Factory.bat It went well till erasing but then gave thsi error : !!! Error 103: Error 0x82 reported by programmation plugin: Device Error
I am downloading the latest version of Ride and RKit-ARM from the raisonance site
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi Vincent, You are correct !! I have upgraded the versions of both Rkit-ARM and Ride to what you have suggested.Now I am able to do the following :
(1) Able to restore the factory image of evo_primer by double clicking Restore_Evo_STM32G_Circle_Factory.bat
(2) Able to flash the Toggle application which is there in the manual of evo primer STM32F103VE and STM32F103VG.
But I am not able to create/build an application by selecting STM32G_Evo_CircleOS device . STM32G_Evo_CircleOS v4.32
I get the following error when I try to build it. C:\tmp\test\Application.c:9:24: fatal error: circle_api.h: No such file or directory compilation terminated. Error Code: 0x1
Build failed
But if I try to create/build an application by selecting STM32E_Evo_CircleOS device . I do not get any error , it compiled successfully but when I get the same error :
Wrong MCU Devie ID : 0x100006430
I know I am doing wrong as it shouldn't flash the STM32F103VE(under the LCD - base STM32) but why it is failing to compile for STM32F103VG . We dont have to flash the STM32F103VE , correct !! , STM32F103VE is used to flash the STM32F103VG.So application for STM32F103VG must be build completely and flashed properly on STM32F103VG (target).
PLz provide your inputs. Rgds Softy
Last edited by softy (2012-12-05 11:19:47)
" Pain is temporary, Quitting Lasts for ever"
Offline
#
10
2012-12-05 16:32:45STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi Vincent, Thanks again.It worked !! I can see my application (Hello world string on the LCD) running now.SO waht we did basically ? We added the option for building the Applications for STM32F103VGT6 (which is the target daughter board or Application board) and flashed it using the USB(RLINk) via STM32F103VET6 correct!! Where can I found the Schematic for the interconnections between the STM32F103VET6 and STM32F103VGT6 in the evo_primer. I may be fixing some other Application Board (with or without the STM MCU - STM32F103VGT6 or any other) and making applications for them.How to proceed for that .I have downloaded the CircleOS code and Documentation from this site.How useful will it be in developing the application for evo_primer.I guess I have to use the CircleOS APIs for that like - DRAW_* calls , etc).Any tips to start with. Rgds, softy
Last edited by softy (2012-12-06 05:07:02)
" Pain is temporary, Quitting Lasts for ever"
Offline
#
12
2012-12-06 08:45:59STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi,
All schematics are available in the resources section of this website and also in the doc folder of Ride. Your other questions are answered in the GettingStartedARM and CircleOS docs.
For using the tools on a board that is not an OP4 Primer, you will need to purchase either an RLink or the OP4-RLink ADP extension daughterboard that allows to use the Open4 base as an RLink.
The CircleOS will only be useful on OP4 Primers (that's an OP4 base with an OP4 daughterboard). On other boards the CircleOS will not be of more use than an example from which you can pick a few pieces of code, except if you design the board specially for being compatible with the OP4... But then you'd better stay with the OP4 and add an extension board.
Best Regards,
Vincent
Offline
#
13
2012-12-07 04:42:50STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi, I am little confused on this :
When I opened the Menu > About , I get the following on the LCD screen :
STM32E Open 4
CPU : STM32F103VET6 OS : V 4.03 225 KB App : 11 218 KB Avail FLASH : 69 KB
but now after installing the new RIde7 and Rkit and flashing the same factory image - Restore_Evo_STM32G_Circle_Factory.bat from the EvoSTM32G_upgrade_v4.32 folder.But now when i do the same I am getting this output :
STM32G Primer
CPU : STM32F103VGT6 OS : V 4.32 180 KB App : 12 330 KB Avail FLASH : 514 KB
Why the change in the CPU.It should get the CPU name of the base of evoprimer , right !! That is STM32F103VET6 .I can open it and under the LCD see the STM32F103VET6 MCU. PLz provide teh clarification . rgds, softy
" Pain is temporary, Quitting Lasts for ever"
Offline
#
14
2012-12-07 08:13:48STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi,
The LCD is driven by the target CPU, which in your case is the G.
The CPU in the base has nothing to do with this and as I said earlier, you should completely forget that this one exists at all. It's only confusing you.
So it is G that should be displayed. What you have is a STM32G Primer.
It used to be E at the beginning because the boards are the same and the first production of Gs was programmed with the firmware for the Es as I explained in the other thread. Just forget about this too and remember you have a STM32G Primer, not a STM32E Primer .
Best Regards,
Vincent
Offline
#
15
2012-12-11 06:46:05STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi Vincent, I cant find the STM32F103VET6 in the schematics of Open4 base here- http://www.stm32circle.com/resources/stm32Gprimer.php in "Open4 base schematics" . Can you please point where it is or which is the correct document for that.I wanted to know the interconnections between VE(base) and VG(target). Rgds, Softy
Last edited by softy (2012-12-11 06:46:26)
" Pain is temporary, Quitting Lasts for ever"
Offline
#
16
2012-12-11 08:51:15STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Re: STM32 Primer 2 Application Running Failure : Wrong MCU DEVICE ID
Hi,
This part is not public, and there is no reason why you would need it.
The target CPU (G) is connected to its programmer/debugger like any other Cortex CPU as specified in the ARM and ST docs. (GND, VCC, RST, SWDCLK, SWDIO, SWO)
The fact that the programmer/debugger is also a STM32 is only confusing you. Just forget about it.
)