+ Reply to Thread
Results 1 to 2 of 2

Thread: XMC4700 SPI TX FIFO via DMA doesn't load TBUF / Shift Register

  1. #1
    New Member New Member mjkinfhtx is on a distinguished road
    Join Date
    Mar 2019
    Posts
    5
    Points
    70

    XMC4700 SPI TX FIFO via DMA doesn't load TBUF / Shift Register

    Hello All,

    I'm trying to setup an XMC4700, USIC.SSC slave (10MHz) to transmit via DMA to the USIC FIFO.

    The receive side is using RBUF via DMA and has no problems.

    The transmit side was previously using TBUF via DMA, but it was transmitting occasional 0xFF bytes, presumable because the Shift register was not being filled fast enough.

    The transmit side was then changed to DMA via the FIFO using the Fill Level mechanism to trigger the DMA.

    When I enable the DMA channel I can see the initial burst read of 8 bytes from the SRAM in the DMA channel registers (SAR and CTLH are as expected).

    When I trigger the initial Service Request I can see that the DMA has burst transferred the 8 bytes into the FIFO (TBFLVL == 8) and the burst transferred another 8 bytes from the SRAM.

    When I then enable the SPI channel and start my external SPI Master, the SPI slave transmits an 0xFF byte, followed by the contents of the FIFO. My data is always shifted by 1 byte and the last byte is wrapped to the next transmission.

    I was expecting the initial FIFO fill level to be less than 8, as the transfer to the FIFO should have also loaded the TBUF / DSU with the first byte for transmission.

    So, now the question:

    As an XMC4700 SPI slave, how do I trigger the initial SPI load to TBUF / DSU from the data already loaded in the FIFO?

  2. #2

    Infineon Employee
    Infineon Employee
    jferreira will become famous soon enough
    Join Date
    Oct 2012
    Posts
    601
    Hi,

    See attached example.The master clock is generated by a CCU slice and the CS by a GPIO.
    Click image for larger version

Name:	spi_slave.png
Views:	9
Size:	117.6 KB
ID:	3942

    Regards,
    Jesus
    ?????
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.