cryptic message "Error: Flash Download failed - "Cortex-M3"
I am using the STM32f103 and another project loads just fine on the same board.
The "informative" message above does not give me anything to hunt for.
anyone know what actually causes the above?
Erik
PS will cross post at ST
this project has run just fine for about a year, the fault happened after a major merge with a coworkers stuff. Before the merge both the coworker and yours truly did not have any problems.
the map show both flash and RAM within the limits
somehow the programmin algorithm in options for target>debug>settings>Flash download was lost. Have no idea how it happened, but now it works
PS would it not be nice if the Fault stated "programming algorihnm missing"?
If there was to be any change, then I would hope that whoever did the change was able to use a keyboard properly so the spelling could be correct ;)
:)
Strange - I thought that at least earlier, Keil gave an error message about not having any algorithm for a specific memory region. Or maybe that was only for NXP LPCxxxx chips.
Additional information about the error (besides the error box) is typically displayed in the Command window.
When there is no algorithm the following message is printed: "Missing Flash Algorithms !"
great for those of us that save screen space by not having the command window (which in most cases is irrelevant) displayed.
If you open all the windows uVision provides (in debug), you are lucky to see two lines of source.
Get a bigger monitor. :)
Some windows aren't needed all the time, but when getting build errors for example, it is obviously a good idea to have the relevant build output log visible.
it is obviously a good idea to have the relevant build output log visible. Of course, I do. I, like, hopefully, everyone, need to see errors/warnings
but that does not help
"Additional information about the error (besides the error box) is typically displayed in the Command window.
had the "Additional information" been in the logical place (the build output log) I would have seen it.
How is it particularly logical for debugger problems to show up in the build output window? And yes, flashing the code onto a device really is part of debugging more than it is one of of building.
There's a reason uVision has always maintained two separate child window layouts, one for edit/build mode, the other for debug mode. You really do need rather wildly different sets of things on the screen in both situations. The build output window shouldn't even be visible when the flash problem is triggered, because by that time you're in debug mode.
... the elaboration is
WHY NOT
in the actual error message?