I'm using PSoC creator 4.3 and PDL 3.1.3
I created an SPI block as a master (see screen shot). There are two slave devices, one is write-only and a data width of 9 bits. The other is read-only and has a data width of 11 bits.
According to the UDB editor, if the Tx and Rx data widths are not the same, you have to use the "National Semiconductor" sub mode.
I selected "National Semiconductor" and it built fine. However, when I run the code, during SPI initialization there is an exception generated by an ASSERT which checks if "National Semiconductor" mode is selected when the Tx/Rx sizes are different. I found that the reason for this assertion is that for some reason, the generated SPI config code does NOT set sub-mode to "CY_SCB_SPI_NATIONAL", but instead uses "CY_SCB_SPI_TI_COINCIDES". (see code snippet below)
I'd like to know if this is a bug, or if I am doing something wrong.
cy_stc_scb_spi_config_t const SPI_DISPLAY_config =
{
.spiMode = CY_SCB_SPI_MASTER,
.subMode = CY_SCB_SPI_TI_COINCIDES,
.sclkMode = CY_SCB_SPI_CPHA0_CPOL0,
.oversample = 16UL,
.rxDataWidth = 11UL,
.txDataWidth = 9UL,
.enableMsbFirst = true,
.enableInputFilter = false,
.enableFreeRunSclk = false,
.enableMisoLateSample = false,
.enableTransferSeperation = false,
.ssPolarity = ((((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT0) | \
(((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT1) | \
(((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT2) | \
(((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT3)),
.enableWakeFromSleep = false,
.rxFifoTriggerLevel = 0UL,
.rxFifoIntEnableMask = 0x0UL,
.txFifoTriggerLevel = 0UL,
.txFifoIntEnableMask = 0x0UL,
.masterSlaveIntEnableMask = 0x0UL
};
