• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 911 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC1310: "memory map preventing re..." message when running NVSINTERNAL SimpleLink example.

Jason Russo
Prodigy 50 points
Part Number: CC1310


Tool/software: Code Composer Studio

I am running the SimpleLink Academy Example for NVSINTERNAL for the CC1310. I can build the example project just fine, and when I debug it, I get the expected output being shown in PuTTY as my output terminal. However, in 'attrs' folder under variables, I have a number of red messages saying "memory map prevented re...". Is there any particular cause of this? How can I fix this? Sorry if the question is a little vague, I'm still a  little new to this, but I am simply using the example files, not modified at all, and a CC1310 Launchpad along with PuTTY for my display. Thanks!

  • 0
    TI__Guru**** 171299 points
    Hi,

    From a pure IDE standpoint, these messages sometimes happen when non-initialized variables are being accessed by the debugger. For example, if a device does not have memory at address 0x0 but a pointer that is not yet initialized points to this address, the Expressions view cannot access the contents of the pointed address. This can happen in both the 'Variables" (local variables) or "Expressions" (globals and custom expressions) views.

    This scenario solves itself as the execution progresses and the pointer is properly initialized.

    However, if you are watching variables in the Expressions view, the context of the program can influence the values of this view, given that certain variables may lose context during program execution (static or local variables, for example).

    Obviously that this pre-supposes the code is running correctly, which per your description it seems to be doing fine.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 50 points
    Thank you for your reply! I see now that I was running the example in debug mode and that it was stopping at the entrance to the main function and I had to advance it myself, novice mistake.