• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 249 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.

Original question:

TMS570LS1114: why cannot the MCU start after reset?

TMS570LS1114: VIM parity error interrupt Group1 15channel can't be entered periodically?

zhang xiaohong
Intellectual 730 points
Part Number: TMS570LS1114

hi,The first time I made a VIM parity error and entered the interrupt of the Group1 15 channel, but the second time I made the VIM parity interrupt, it would not enter the interrupt of the Group1 15 channel, and at the same time SR1[0] bit15 It has not been set, but when I entered the interrupt for the first time, I knew the corresponding interrupt flag. What is the reason for this?

  • 0
    Intellectual 730 points

     FBPARERR and ESM Group1.15 are entered only once. When making VIM parity error again, these two interrupt programs will not be triggered. The VIM parity error address I created is the address provided by the diagnostic library, and the code is as follows:

  • 0 in reply to zhang xiaohong
    TI__Guru**** 197046 points

    Did you clear the parity error flags and restore the corrupted data after the selftest is done?

    Can you get the interrupt if you perform the test at different location of VIM RAM? For example, if the 0xFFF82000U is used in your previous test, please try the test at 0xFFF82020U for example.

  • 0 in reply to QJ Wang
    Intellectual 730 points

    1. After VIM parity failure occurs, parity Error Flag is cleared in the interruption of ESM Group1.15, and the corrupted data is restored after the selftest.

    2. First，I made a parity error at 0xFFF82008，which generated an interrupt，FBPARERR and ESM Group1.15. Then, I made a parity error at 0xFFF82000, which also generated an interrupt. FBPARERR and ESM Group1.15, however, there is no interrupt when the address 0xFFF82008 or 0xFFF82000 fails again. Can VIM parity errors on the same address only be diagnosed once？

  • 0 in reply to zhang xiaohong
    Intellectual 730 points

    The problem has been solved