• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 102 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28379S: Is there any possibility of data corruption when displaying data stored in the 28x MCU's internal memory in the Expressions or Graph views of CCS through a JTAG debug probe.

Sang-il Nam
Expert 2335 points
Part Number: TMS320F28379S

Hi,

While checking the data inside the chip through real-time debugging(JTAG), I found that there was some error(not exactly matched) between the data displayed in Expressions and Graph view and the actual data stored inside the memory of TMS320F2837xS MCU.

I'm curious as to whether there is a possibility of data corruption when displaying data stored in the 28x MCU's internal memory in the Expressions or Graph views of CCS through a JTAG debug probe.

I think the inquiry in the post below is similar to mine.

>> Difference between the actual value and the value being shown by emulator on 'Expressions' (click)


Thanks and regards,
Sang-il

  • +1
    TI__Mastermind 30180 points

    Hello Sang-il,

    Sang-il Nam said:
    I'm curious as to whether there is a possibility of data corruption when displaying data stored in the 28x MCU's internal memory in the Expressions or Graph views of CCS through a JTAG debug probe.

    I have not heard of a case like this ever happening, the memory is not corrupted by an emulator read of the memory itself; if there is unexpected alteration of the data, it's more than likely not because of the JTAG probe.

    As far as why this issue might be occurring, would it be possible to show an exact instance of this? I.e. where the graph is displaying one value and when you check the memory it displays a different value; if you could attach a screenshot of this in CCS itself, that would be helpful.

  • 0 in reply to Omer Amir
    Expert 2335 points

    Hello Amir,

    Thank you for your quick reply.

    Omer Amir said:
    I have not heard of a case like this ever happening, the memory is not corrupted by an emulator read of the memory itself; if there is unexpected alteration of the data, it's more than likely not because of the JTAG probe.

    I agree with your answer, and I do think that it will be.
    On second thought, I think I probably observed the wrong result in the wrong environment or settings.

    You may close this thread.
    I will run the test again, and if the problem still occurs, I will collect the relevant data and ask the question again.

    Thanks and regards,
    Sang-il