- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I am trying to use the RM48L952 HDK board's SPI2 peripheral in Master mode. I originally used SPI1 and was able to verify the code and the HalCoGen settings as working. However, because this system also requires the Ethernet on the board and the HDK board has Ethernet and SPI1 muxed, I had to switch over to SPI2. I replicated the settings for SPI2 in HalCoGen, but the output is different. Attached are screenshots of my HalCoGen tabs for SPI1 and SPI2.
The code below are functions I am using to interact with my SPI slave. This code works when using SPI1, with the HalCoGen settings attached.3771.spi settings.zip
void init_spi_interface() {
spiInit();
data_config.CS_HOLD = 1;
data_config.WDEL = 0;
data_config.DFSEL = SPI_FMT_0;
data_config.CSNR = SPI_CS_0;
}
void send_spi_message() {
uint16_t txBuf[] = {0x03U, 0x60U, 0xF4U, 0x6CU};
spiTransmitData(spiREG2, &data_config, 4, txBuf);
}The (correct) output of SPI1 is 03 60 F4 6C, whereas the (incorrect) output of SPI2 is 03 07 10. (Notice I only get a byte and a half rather than two bytes)
Is there something inherently different about SPI2 and SPI1 that would cause this?
Thank you,
John
Hello John,
I tested SPI2 on HDK this morning, it works without any problem. If you use an external SPI tool, you need to enable the CS hold mode. In CS hold mode, the chip select signal is held active at the end of a transfer until a control field with new data and control information is loaded into SPIDAT1. If the new chip select number equals the previous one, the active chip select signal is extended until the end of transfer with CSHOLD cleared, or until the chip-select number changes.
This is the code I used in my test:
/* USER CODE BEGIN (0) */
/* USER CODE END */
/* Include Files */
#include "sys_common.h"
/* USER CODE BEGIN (1) */
#include "spi.h"
/* USER CODE END */
/** @fn void main(void)
* @brief Application main function
* @note This function is empty by default.
*
* This function is called after startup.
* The user can use this function to implement the application.
*/
/* USER CODE BEGIN (2) */
uint16 TX_Data[16] = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10 };
uint16 RX_Data[16] = { 0 };
/* USER CODE END */
int main(void)
{
/* USER CODE BEGIN (3) */
volatile uint32 SpiBuf, blocksize, i;
spiDAT1_t dataconfig1_t;
dataconfig1_t.CS_HOLD = TRUE;
dataconfig1_t.WDEL = FALSE;
dataconfig1_t.DFSEL = SPI_FMT_0;
dataconfig1_t.CSNR = 0xFE;
/* Enable CPU Interrupt through CPSR */
_enable_IRQ();
/* Initialize SPI Module Based on GUI configuration
* SPI2 - Master ( SIMO, SOMI, CLK, CS0 )
* */
spiInit();
/* Initiate SPI2 Transmit and Receive through Polling Mode*/
for (i=0; i<100; i++){
spiTransmitData(spiREG2, &dataconfig1_t, 16, TX_Data);
}
while(1);
/* USER CODE END */
return 0;
}
Teh SPI2 is configured as master, the baud rate is 1000Kbps, data length is 16bit. The SPI slave is Aardvark SPI/I2C adaptor. From the figure below, the txed data from SPI2 is the same as the rxed data on SPI adatpor (the data format is 16-bit, so they are 00 01 00 02 00 03...):
TX_Data[16] = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10 };
