Forum : ARM
| Post Information | Post |
|---|---|
|
November 25, 2009 - 9:46am
|
I get this strange error message when trying to debug my project based on STM32F103C8T6 device (with 64KB FLASH). The debug session is launched correctly but i get this error when resetting device is performed by RLink. The problem don't appear when I use STM32F103VBT6 chip. My application occupies 24KB so the debug limitation with RLink-STD is not exceeded. I searched other forums for how to solve the problem with no success. I tried to reinstall Ride7 and RKit but it didn't help. I also created new project which contained only "int main(void)" function with default startup files but the problem persists. From what I got to know the PC gets corrupted but I can't understand why this doesn't happen in my project based on STM32F103VBT6 device but does happen in STM32F103C8T6 ? |
Hi
Can you confirm that you have this issue doing the steps listed below
- openning a project example from installation
- changing target to STM32F103VBT6
- starting debug (CTRL+D)
- Sotpping debug
- changing target to STM32F103C8T6
- (CTRL+D)
If going this leeds to the error message you have it might be a hardware issue
can you give more information about the difference between target boards?
Regards,
Matloub
The error occurs during starting debug session. First "Erasing Flash" is dispplayed. Then "Programming flash". At the end i can see "resetting the target" - and the error message is displayed.
However, i think i know where the error comes from but still don't know why it happens. I programmed the microcontroller using RFlasher. Programming is ok but it doesn't pass verification. All the flash locations equeal to 0xFF after programming. When i change the target board to one with STM32F103VBT6 device everything is ok (verification succeeds)
It means that Ride7 doesn't verify programmed flash against *.hex file when starting debug session (it doesn't detect that all the flash contens is 0xFF). Is it correct ? If all the Flash bytes are 0xFF it is no wonder that PC gets corrupted.
Perhaps it is something wrong with soldered STM32F103C8T6 on the board ? But why Ride7 doesn't detect incorrect flash programming ?
The difference between target board is only different devices used in each of them. One board contains STM32F103VBT6 and the other - STM32F103C8T6. With STM32F103VBT6 there are no issues.