LPC MicrocontrollersのトピックSPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

danielholala — Fri, 18 Feb 2022 14:59:48 GMT

Hello everybody,

On my custom LPC55xx based board I'm trying to communicate via a single SPI interface with several slaves (SSEL0 - SSEL2).

The MCU obviously supports this as the FIFO Write register contains bits to select the slave for a transfer.

FIFOWR provides the possibility of altering some SPI controls at the same time as
sending new data.

Do the SDK drivers support this and how?

I checked SDK examples but could not find an anwer to my question. Further, SDK documentation is lacking. There's no information about, e.g., SPI_MasterInit() or SPI_MasterTransferNonBlocking() in the SDK doxygen doc.

I gleaned from the source code fsl_spi.h that the slave number is encoded in a struct spi_master_config_t and this struct is used when calling SPI_MasterInit(). According to fsl_spi.h, the slave number is not used when doing a transfer. So it seems it is not possible to easily switch between slaves from one transfer to another.

Any help is appreciated.

Best regards,
Daniel

Re: SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

Alice_Yang — Wed, 23 Feb 2022 05:41:24 GMT

Hello danielholala,

The slave number is used in SPI_WriteData() function:

So if you want to use more than one slave, you need change the number for call this data write function.

Alice

Re: SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

danielholala — Thu, 03 Mar 2022 11:48:09 GMT

Dear Alice,

Thanks, I appreciate your reply.

You seem to be confirming that the SDK SPI driver does not support more than one slave per SPI interface.

In that case I'd say that the SDK is utterly lacking as it misses basic functions and that NXP has done a bad job regarding SDK.

I hope that NXP is working on the shortcomings of the SDK (documentation and functionality).

Best regards,
Daniel

Re: SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

danielholala — Thu, 03 Mar 2022 13:51:30 GMT

Dear Alice,

as you know the Peripherals Tool generates code based on the CMSIS API. I used Peripherals Tool to configure Flexcomm interfaces, e.g., Flexcomm3 for SPI. For the SPI component this code in "peripherals.c" looks like:

static void FLEXCOMM3_init(void) { /* Interrupt vector FLEXCOMM3_IRQn priority settings in the NVIC. */ NVIC_SetPriority(FLEXCOMM3_IRQN, FLEXCOMM3_IRQ_PRIORITY); /* Initialize CMSIS SPI */ FLEXCOMM3_PERIPHERAL.Initialize(SPI_SignalEvent); /* Power control of CMSIS SPI */ FLEXCOMM3_PERIPHERAL.PowerControl(ARM_POWER_FULL); /* Control of CMSIS SPI */ FLEXCOMM3_PERIPHERAL.Control(ARM_SPI_MODE_MASTER | ARM_SPI_CPOL0_CPHA0 | ARM_SPI_DATA_BITS(8) | ARM_SPI_MSB_LSB | ARM_SPI_SS_MASTER_HW_OUTPUT, 500000); /* Control of CMSIS SPI */ FLEXCOMM3_PERIPHERAL.Control(ARM_SPI_SET_DEFAULT_TX_VALUE, 0); }

Further, I have to add the SPI callback function.

With that said and referring to your suggestion to use calls from the standard SDK SPI driver:

how do I continue/move from here (CMSIS based driver code and initialized SPI interface) to the standard SDK driver?

Thanks.

Daniel

Re: SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

Alice_Yang — Tue, 08 Mar 2022 04:25:38 GMT

Hello Daniel,

The SDK SPI driver support multiple slaves. I have reply you on your private case.

Alice

Re: SPI: slave select using SDK, e.g., SPI_MasterTransferNonBlocking()?

danielholala — Thu, 23 Nov 2023 08:58:26 GMT

Dear Alice,

I appreciate your reply. However, I have to disagree. I can not find any API functions to select a different slave for each transaction short of calling the init function again (as I mentioned before).

I'm using Peripherals Tool and selected "Universal Driver" for Flexcomm. This generates initialization code based on the CMSIS driver. The CMSIS driver is not using SPI_WriteData() but SPI_MasterTransferNonBlocking() and SPI_TransferHandleIRQInternal() in fsl_spi.c.

The latter includes this piece of code:

/* select slave to talk with */ tx_ctrl |= ((uint32_t)SPI_DEASSERT_ALL & (uint32_t)SPI_ASSERTNUM_SSEL(handle->sselNum)); /* set width of data */ tx_ctrl |= SPI_FIFOWR_LEN(handle->dataWidth);

That is, in each interrupt request, the slave is selected according to handle->sselNum.

A quick solution is to add an API call (to fsl_spi_cmsis.c) in order to change sselNum.

uint8_t SPI3_getSSEL() { return SPI3_InterruptDriverState.handle->masterHandle.sselNum; } void SPI3_setSSEL(uint8_t slave) { SPI3_InterruptDriverState.handle->masterHandle.sselNum = slave; }

This sets sselNum of Flexcomm3. Should be called before a call to Transfer().

Further resource locking is recommended.

Best regards,
Daniel