• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 611 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.

RTOS/TM4C1294NCPDT: Ti-RTOS GPIO interrupt example debugging/programming problem.

digvijay khambe
Expert 2735 points
Part Number: TM4C1294NCPDT

Tool/software: TI-RTOS

Respected sir,

  I have started working on TI-RTOS. I am trying to implement the GPIO interrupt example from TI target examples.But there is problem while debugging/programming. When i follow the procedure given in 

TI-RTOS 2.20 User’s Guide(page 96-102) for UARTMon module i get the following error.

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.

I referred to other threads from forum but none solved the problem. So please give me solution for this.

Also as method given in TI-RTOS 2.20 User’s Guide was not working i directly debugged the project without changing debugger configuration and it worked. But the question is , is it safe to do it??  Will i be able to use UARTMon module and other features??

  • 0
    TI__Guru**** 190806 points

    Hi,

     Did you try the gpiointerrupt_EK_TM4C129XL_TI example?

     I just tried the above example and followed the user's guide to set up a new target configuration for the UART connectio and it is working for me on the LaunchPad. I tried to monitor the the variable count via the UART connection as shown below. As I pressed the switches on the board, the count will increment. 

  • 0 in reply to Charles Tsai
    Expert 2735 points

    Respected sir,

    I am using same example. .Its not working for me. It is giving the error as mentioned in the post.

  • 0 in reply to digvijay khambe
    TI__Guru**** 190806 points

    Hi DK,

     So the error you see is when you tried to load the program to the flash, correct? Did you somehow change the .cmd file? Please also check if you use the correct target configuration file when you connect to the target. You target configuration should look something like below if you are using the launchpad with the Stellaris ICDI debug probe. If you are using a different debug probe then it will look different but still similar. I'm curious as to what gel file you are loading. The gel file specifies which memory regions are read or writeable. 

     One quick experiment is -can you delete the existing gpiointerrupt_EK_TM4C129XL_TI project and go to resource explorer and re-import the same project again? After you import the gpiointerrupt_EK_TM4C129XL_TI example, try to rebuild it and will you still see the problem when loading the program?