• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 543 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.

TMS570LS0432: Set RXOVRNINTFLG in Spi3 Register.

Andy Bolanos
Prodigy 40 points

Part Number: TMS570LS0432

Hello,

I'm part of a software testing project, currently I'm working in creating test for the SPI communication between two processors, one requirement require to check for the SPI3 receive buffer overruns. Basically what the software does is checking the RXOVRNINTFLG flag in the spi3 registers, if the flag is set do X if not do something else. However I've been having problems to set the flag, I have tried to open the debugger in both processors halt the master while the slave is sending data and then resume the master but the flag is no set.

Is there any workaround to set the flag? If so, what are the step to set the flag?

Kind Regards, Andy

  • 0
    TI__Guru 59540 points
    Hello Andy,

    This flag is an indication that a message was received and not read prior to the current message being received. If you would like to force this flag to be set, you would need skip the read of a message during a stream of messages from the master to the slave or vice versa. One method to do this would be to halt the CPU in a debugger after a message is received and prior to reading the receive buffer. Once halted, set the program counter to an address after the read so that the Rx buffer is never accessed for that message. Once skipped and the next message is received, the error flag should be set and the fault path taken.

    Note that this method is suitable for code testing only and not necessarily for a SW diagnostic test where the error can be introduced more programmatically. i.e., in a SW diagnostic test, the read can be deliberately bypassed to create this error condition and test for the proper operation of both the error flag and fault notification path of the safety system.