Infineon SPI CPU 1 User manual

AURIX™ TC2xx Microcontroller Training
V1.0.0
SPI_CPU_1
SPI communication via QSPI
Please read the Important Notice and Warnings at the end of this document

Scope of work
A QSPI module configured as SPI master sends five bytes to another
QSPI module which is configured as SPI slave.
QSPI2 is configured in master mode and used to send five bytes to QSPI3
configured in slave mode. The received data is read by the CPU and
compared against the transmitted data. Port pin 13.3, to which LED D110 is
connected, indicates the successful transfer.
2
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Introduction
›The Queued Synchronous Peripheral Interface (QSPI) enables
synchronous serial communication with external devices based on the
standardized SPI-bus signals: clock, data-in, data-out and slave select.
›The QSPI works in full duplex mode either as Master or Slave with up to
50 MBit/s.
3
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Hardware setup
This code example has been
developed for the board
KIT_AURIX_TC297_TFT_BC-Step.
4
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Hardware Setup
KIT_AURIX_TC297_TFT_BC-
Step
X103 : QSPI3 (Slave)
WIRE
X102 : QSPI2 (Master)
P02.7 : 20
: SCLKI 
P15.3 : 32 : SCLKO
P02.4 : 17 : SLSI_A

P15.2 : 31 : SLSO_0
P02.5 : 18 : MRST

P15.4
: 33 : MRST_A
P02.6 : 19 : MTSR_A

P15.5 : 34 : MTSR
KIT_AURIX_TC297_TFT_BC-Step
›Use the stencils as
illustrated. ›Connect following pins
as described and
illustrated using wires.
5
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Implementation
Configuring the SPI communication
The configuration of the SPI communication is done once in the setup phase through the
function initQSPI() in two different steps:
›QSPI Slave initialization
›QSPI Master initialization
QSPI Slave initialization
›The initialization of the QSPI slave module is done by defining an instance of the
IfxQspi_SpiSlave_Config structure.
›The structure is filled with default values by the function
IfxQspi_SpiSlave_initModuleConfig().
›Afterwards, the pins and the protocol.dataWidth are modified, due to the fact that the
default data width in slave-mode is 8-bit and it needs to be explicitly specified to 32-bit.
›The function IfxQspi_SpiSlave_initModule() is used to initialize the QSPI slave
module.
›Additionally, the buffers used by the QSPI slave are initialized.
The above functions can be found in the iLLD header IfxQspi_SpiSlave.h.
6
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Implementation
QSPI Master initialization
›The initialization of the QSPI master module is done by defining an instance of the
IfxQspi_SpiMaster_Config structure.
›The structure is filled with default values by the function
IfxQspi_SpiMaster_initModuleConfig().
›Afterwards, the pins are modified.
›The function IfxQspi_SpiMaster_initModule() is used to initialize the QSPI master
module.
›A QSPI module controls 16 communication channels, which are individually
programmable. In this example, the function initQSPI2MasterChannel() initializes the
channel zero using an instance of the structure IfxQspi_SpiMaster_ChannelConfig.
Afterwards, the slave select channel number is set through the parameter sls.output
and the baud rate is modified via the parameter base.baudrate.
›The function IfxQspi_SpiMaster_initChannel() is used to initialize the QSPI master
channel.
›Additionally, the buffers used by the QSPI master are initialized.
The above functions can be found in the iLLD header IfxQspi_SpiMaster.h.
7
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Implementation
QSPI Master Slave communication
›The function transferData() triggers the data transfer between the SPI-Master and
SPI-Slave.
›Additionally, LED D110 connected to port pin 13.3 is used to signal if the transmission
was successful.
8
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

Run and Test
After code compilation and programming
the device, perform the following steps:
›Set a breakpoint to transferData() in the
Cpu0_main.c and check the
spiMasterTxBuffer and
spiSlaveRxBuffer inside spiBuffers
structure.
›Run the demo project and check if the
LED D110 (1) is on (Data transmitted
without errors).
›The spiMasterTxBuffer and
spiSlaveRxBuffer now should show the
same transmitted and received data.
›Remove a cable (e.g. SCLKx), perform a
Reset and re-run the application to see
that the data transmission is interrupted
and the LED D110 (1) is off (Data
transmission blocked) .
1
9
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

References
›More code examples can be found on the GIT repository:
›https://github.com/Infineon/AURIX_code_examples
›For additional trainings, visit our webpage:
›https://www.infineon.com/aurix-expert-training
›AURIX™ Development Studio is available online:
›https://www.infineon.com/aurixdevelopmentstudio
›Use the „Import...“ function to get access to more code examples.
›For questions and support, use the AURIX™ Forum:
›https://www.infineonforums.com/forums/13-Aurix-Forum
10
2019-10-17 Copyright © Infineon Technologies AG 2019. All rights reserved.

IMPORTANT NOTICE
The information given in this document shall in no
event be regarded as a guarantee of conditions or
characteristics (“Beschaffenheitsgarantie”).
With respect to any examples, hints or any typical
values stated herein and/or any information
regarding the application of the product, Infineon
Technologies hereby disclaims any and all
warranties and liabilities of any kind, including
without limitation warranties of non-infringement
of intellectual property rights of any third party.
In addition, any information given in this
document is subject to customer’s compliance
with its obligations stated in this document and
any applicable legal requirements, norms and
standards concerning customer’s products and
any use of the product of Infineon Technologies in
customer’s applications.
The data contained in this document is exclusively
intended for technically trained staff. It is the
responsibility of customer’s technical
departments to evaluate the suitability of the
product for the intended application and the
completeness of the product information given in
this document with respect to such application.
For further information on the product,
technology, delivery terms and conditions and
prices please contact your nearest Infineon
Technologies office (www.infineon.com).
WARNINGS
Due to technical requirements products may
contain dangerous substances. For information
on the types in question please contact your
nearest Infineon Technologies office.
Except as otherwise explicitly approved by
Infineon Technologies in a written document
signed by authorized representatives of Infineon
Technologies, Infineon Technologies’ products
may not be used in any applications where a
failure of the product or any consequences of the
use thereof can reasonably be expected to result
in personal injury.
Edition 2019-10
Published by
Infineon Technologies AG
81726 Munich, Germany
© 2019 Infineon Technologies AG.
All Rights Reserved.
Do you have a question about this
document?
Email: [e-mail]
Document reference
QSPI_CPU_1
Trademarks
All referenced product or service names and trademarks are the property of their respective owners.