• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 132 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:

TMS570LS1224: In SPI compatibility mode, are the SPI registers with offsets greater than 70h readable?

TMS570LS1224: UERRCTRL register read value for SPI that is not a MibSPI

PauloP
Prodigy 220 points
Part Number: TMS570LS1224


Tool/software:

I am aware the UERRCTRL register is a multi-buffering (Mib) related register.

Technical Reference Manual (SPNU515C) states the 'value after reset' for register UERRCTRL is 00000005h

If I read this register for an SPI that is not a MibSPI, such as SPI4, the read return value is 00000000h

Is a read return value of 00000000h as expected for the UERRCTRL register if it is read for an SPI that is not a MibSPI?

 

  • 0
    TI__Guru 72866 points

    Hi Paulo,

    Yes, a read return value of 0x00000000 is expected and correct for the UERRCTRL register if it is read for an SPI module that is not a MibSPI (Multi-buffered SPI), such as SPI4 in your device.

    Here's why:

    1. UERRCTRL is MibSPI-Specific: As its full name "Multi-buffer RAM Uncorrectable Parity Error Control Register" and the context in the Technical Reference Manual (TRM) clearly indicate, this register is specifically associated with the Multi-buffer RAM feature. This RAM is a key distinguishing characteristic of the MibSPI module, used for efficient data handling with DMA.

    2. Standard SPI Lacks Multi-buffer RAM: A standard SPI module (like SPI4, if it's not a MibSPI in your TMS570LS1224 device) does not possess this dedicated multi-buffer RAM. Therefore, it does not have the associated parity error detection and control hardware that UERRCTRL manages.

    3. Reading Unimplemented Registers: When you attempt to read a memory-mapped register address that corresponds to a feature or hardware block not implemented in a particular instance of a peripheral (or not implemented at all), the system typically returns 0x00000000. This is a common design practice to indicate that the feature is absent, or the register is not valid for that specific module.

    We will note down this and we will try to include a note regarding this in our next document release.

    --

    Thanks & regards,
    Jagadish.