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.

Memory Map Setup?

Other Parts Discussed in Thread: HALCOGEN

Our current specifications:

Windows 7 Enterprise (64 bit)

HALCoGen version 03.06.00

Code Composer Studio 5.5.0.00077

TMS570LS31x HDK

The following error has appeared as of this morning, and affects all of our projects, including those created before this error appeared (as in, no modifications since before the error appeared). No updates to the above programs have been carried out that may have caused this issue, and the issue occurs on two separate computers (however it is the same board in all cases, as we currently only have the one).

Exactly every other time we use the debug option of Code Composer Studio to test our code on our mictrocontroller, the following appears in the console and the project fails to load:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.

The error occurs every other time that the debug option is used, regardless of what project we attempt to load.

Though there are several other threads that mention this error, in this case it is not tied to any larger issue, and the only other thread which had this exact problem was solved by upgrading from Code Composer Studio 5.2.1 to 5.3. As we are already using 5.5, this solution is not entirely helpful.

Additionally, since this problem occurred our sci practice code (which we've been incorporating into our RTOS-based projects to ensure functionality) are no longer receiving input. While they provide the prompt ("Please press a key") as expected, more often than not there is no response to any typing (the expected response is to return the typed letters in the terminal). I am unsure if this is related.

  • If you are using the default auto target configuration, you need to make sure you have a device variant selected:

    If you are using a user defined target configuration, you need to make sure that there is the device is listed in the tree:

    Whichever you are using, if done correctly you should see a Flash setting option page in the Debug properties for the target config:

  • Hi John,

    We are using the following settings for all of our projects, both those created before and after this issue started occurring.

    We do see the Flash setting option page for all our projects, however changing between wiping the entire flash to Necessary Sectors Only (recommended by the tutorial videos) has no effect on this issue, nor does keeping it set to erasing the entire flash solve the issue.

  • Would you attach the map file when the error occurs.  Also, a screenshot of you Flash Options.

  • What is the version of the Hercules Emulation installed?

  • Here is the screenshot for the flash options:

    The forum is listing the map file as not a valid file type and refuses to upload it, so I converted it into the attached .txt file.

    6036.RTOSCI.txt

    I am not sure what you mean by Hercules Emulation, we are running all of our code on a physical microcontroller, not an emulated chip. Could you elaborate?

    EDIT: The error is no longer occurring on my coworker's computer, however it is still affecting mine. All the other information in the initial post remains unchanged however.

  • Hercules emulation is what the device support package for Hercules devices in CCS. You can find the installed version in CCS if you go to help -> about and select the installation history button. The latest version is 5.5.0.9. 

  • Our current version was 5.5.0.5.

    I have since checked for updates and installed all available updates, however the problem still persists, exactly as described above.

  • ecoSAT team,

    The warning message is saying that a section of the program you are loading falls into a memory area that has been marked as not writeable in your memory map configuration. It also appears to be the intvecs section at address zero.

    Could you take a screenshot of your memory map after you have loaded the program that creates the error (while in the debug perspective, use the Tools->Memory Map menu) and post it here?  The other thing that might help us is a debug server log. If you can generate one by going to Help->CCS Support, select Debug Server Log, enable it to write to a file, perform the program load that causes the message, and then compress the log and post it here.

  • Hi AndyW,

    For whatever reason, as of this morning the error is no longer occurring. As far as I'm aware, no changes to the settings of Code Composer Studio have been carried out, but I am no longer able to cause it to occur.

    I guess my problem has been solved, however if the error ever reappears I will make sure to take screenshots and log data as you suggest.

  • Thanks for the update. Give us a shout if it comes up again.