Forum : ARM
| Post Information | Post |
|---|---|
|
October 16, 2009 - 1:22am
|
I'm working with the STM3210C-EVAL with the STM32F107VCT6 processor. I recently upgraded RIDE to version 7.24.09.0251 and RKit-ARM to 1.22.09.0254. The first thing our firmware does is enable the read-out protection. After running our firmware once, I am not able to remove the read-out protection with the RLink Configuration "Debug options" dialog box. I am also not able to remove the read-out protection using RFlasher7. I am able to remove the read-out protection by booting to system memory and using the "Flash Loader Demo" software communicating through the USART. I am also able to remove the read-out protection using the RLink, if the read-out protection is originally enabled by the RLink. This issue only appears if the firmware enables the read-out protection. This is not really a major issue, since I have a work-around using the system memory boot option, but it would be much more convenient if I didn't have to change boot options to remove the read-protection every time I want to program the device... |
Hi
Just two points I would to clarify to make sure I understand the issue:
- This problem was not there before you made the software upgrade.
If yes can you also give the sofware versions you had before.
- What you call your firmware is it a project in Ride7 or just a programable file?
If it is a project is it possible for you to send it to us or at least to reduce the project
to the part which seems to create the problem (readout enabling)?
Regards,
Matloub
I'm not sure this issue appeared with the most recent versions of Ride7 and Rkit-ARM, as this is the first time I am using the RLink with this project. I never tried this with the previous versions.
Yes, the "firmware" is a project in Ride7. I can scale down the project to include just the code that enables the read-out protection so you can try to recreate the problem. Let me know how you would like me to send it.