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

Unable to read the internal registry contents

Akhilesh Raju
Intellectual 285 points
Other Parts Discussed in Thread: TM4C123GH6PM

Hi all,

In the CCS debug window when i try to read the registry contents of the TM4C123GH6PM it shows  "error:unable to read".

A few days back I did not face this problem and was perfectly able to read the contents of all the peripheral registers.

Now suddenly it is giving this error. Another peculiarity is that it is able to read a few registers such as TIMER 0/1, Core Resigters etc but I am not able to read majority of the registers linked with the onboard peripherals such as ADC,SSI,UART etc.

Kindly help

Thanks,

Akhilesh

  • 0
    Guru 92251 points

    Akhilesh Raju said:
    Another peculiarity is that it is able to read a few registers such as TIMER 0/1, Core Resigters etc but I am not able to read majority of the registers linked with the onboard peripherals such as ADC,SSI,UART etc.

    Has the clock been enabled on the peripherals for which the read errors are reported for?

    Upon device reset the Tiva peripherals are disabled (no clock), which prevents the debugger (and CPU) from reading the peripheral registers. See http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/288233.aspx

  • 0 in reply to Chester Gillon
    Intellectual 285 points

    Hi Chester,

    I tried the solution in that post and so happens that it was correct.

    But I still wonder why all of a sudden this problem arose. I never faced such a problem before. Before running the program also I was able to view the registry contents.

    Thanks

  • 0 in reply to Akhilesh Raju
    Guru 92251 points

    Akhilesh Raju said:
    But I still wonder why all of a sudden this problem arose. I never faced such a problem before. Before running the program also I was able to view the registry contents.

    One possible reason is that when you download a program that by default CCS doesn't perform a "system reset" on the target. This means that when you start running a "new" program, any peripherals which were enabled by the last program run can be left enabled (and thus be viewed).