c - How do I execute a function from RAM on a Cortex-M3 (STM32)? -

I am trying to run the function with RAM on a Contex-M3 processor (STM 32). The function erases the internal flash and rewrites it, so I should definitely be in RAM, but how can I do this? Is

I have tried to do it: Memkpi (copy it to function in a byte array in RAM using the check right is aligned properly), function pointers point to the byte array (Indicator) when calling a function for

This probably works well for 10 instructions (I can follow the execution with the debugger) but then I get a bass error and reset the processor. The buzz error occurs through the loop on the second loop, so the code should be fine (because this first pass works). I am thinking that using RAM faster in some way eliminates Brus time ...

Is there any way to do this anyway? How does a scatter file look like a function automatically in RAM (I use the Qylax UI for Cortex-M3)? In

Edit: More information: Tulcan: Real Viyyu Mdike-ARM v 4.10 Compiler: Armsisi v4.0.0.728 Assembler: Armsm v4.0.0.728 Linker: Armlink v4.0.0.728 processor: STM32F103ZE < / P>

It is possible to run on a crash loop because the function is in the branches And the new function in RAM is not relative to the location. Could that be a bus error due to flash area operation at the point of access to the original code location?

I believe that you can mark a code for compiling and the RAM is correctly defined in the RAM with reference to the __rm function definition. RealView see technical support article for instructions with the compiler to do how to do:

μVision lets you search the modules in specific memory areas which are entered in the dialog Project - Option - Goal To do this, right-click on the source file (or file group) and open the dialog Option - Properties then under Memory Assignments Select areas.

There is an example in the ARMExamplesRAM_Function folder.

To start copying that function to RAM and adding the call correctly to that location, the startup code should be generated. Otherwise, if you need to dynamically copy the arbitrary tasks for RAM, see the compilation with the actual view.