Simulator memory write 0x6002b1d0-0x60046407 failed
I am trying to run my project through the ARM simulator. I can connect to it (Target > Connect > ARM Simulator) successfully; but when I try to run the code, I get the following error:
Simulator memory write 0x6002b1d0-0x60046407 failed
I am very new to CrossWorks, so this is probably due to a very basic error on my part. Does the project need to be created in a special way in order to run it through the simulator? I have inherited the project from a former colleague and am learning (rapidly) on the job.
-
Hello Jon,
Thanks for your speedy reply. The target architecture is v7EM and the Core Type is Cortex-M7. As I'm a beginner, I've attached a couple of images to show you exactly what I normally do in case I've given you the wrong information. (The "SEGGER J-Link" connection is the one I use when flashing it to the real physical device; for the simulator I've been using the highlighted one at the top.)
Thanks in advance for any advice you might be able to give!
Cheers,
Ed
-
Hi Ed,
The Debug > Simulator > Memory Simulation Parameter project property specifies the memory segments created by the simulator.
The error message you are getting suggests the 0x60000000 FlexSPI segment is not specified by the property.
If you are using CrossWorks for ARM 4.8.4 or later, try setting this property to $(MemorySegments) which is a macro that expands to all the segments specified in the memory map file and is the default value of this property in the current version of the support package. If you are using an earlier version of CrossWorks you will need to add the segment to the property manually.
Regards,
Jon
-
That worked! Thank you so much, Jon. My code doesn't run for very long, mind you - but that's a different problem ... !
Just for the record (in case it helps someone else), my version of CrossWorks for ARM (4.9.1 for Windows) didn't have the Debug > Simulator > Memory Simulation Parameter menu item: Simulator doesn't appear under Debug. However, I was able to edit the property directly by double-clicking it in the Project Properties view shown earlier.
Thanks again - this should help shorten my develop-and-test cycles considerably!
Please sign in to leave a comment.
Comments
4 comments