• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 1399 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

runtime error when using SPI1

Jonathan Duan
Intellectual 570 points
Other Parts Discussed in Thread: SYSBIOS

Hi,

I have 3 SPI devices in my hardware architecture. They use SPI0, 2, and 1 respectively.

RTOS has SPI 0 and 2 configured aleady. I tried to add SPI1, but I got the following error message.  How do I configure SPI1 correctly?

Error from Console :

{module#48}: line 143: error {id:0x110000, args:[0x13, 0x0]}
Starting ESU Firmware ... 
Level 0, 1mS
ng execution...
{module#30}: line 202: error {id:0x10000, args:[0x5730, 0x5734]}
xdc.runtime.Error.raise: terminating execution

Stack Dump :

<terminated>ESU_Firmware_9252 [Code Composer Studio - Device Debugging] 
ESU_Firmware_9252 [Code Composer Studio - Device Debugging] 
Stellaris In-Circuit Debug Interface/CORTEX_M4_0 (Suspended) 
loader_exit() at exit.c:52 0x00005C44 
abort() at exit.c:117 0x00005C4E 
xdc_runtime_System_abort__E(unsigned char *)() at System.c:100 0x00006BD0 
xdc_runtime_Error_policyDefault__E(struct xdc_runtime_Error_Block *, unsigned short, unsigned char *, int, unsigned int, int, int)() at Error.c:165 0x00002842 
xdc_runtime_Error_raiseX__E(struct xdc_runtime_Error_Block *, unsigned short, unsigned char *, int, unsigned int, int, int)() at Error.c:114 0x00006B7C 
xdc_runtime_Assert_raise__I(unsigned short, unsigned char *, int, unsigned int)() at Assert.c:34 0x00005728 
ti_sysbios_knl_Semaphore_pend__E(struct ti_sysbios_knl_Semaphore_Object *, unsigned int)() at Semaphore.c:208 0x00000904 
SPITivaDMA_transfer(struct SPI_Config *, struct SPI_Transaction *)() at SPITivaDMA.c:534 0x0000522E 
SPI_transfer(struct SPI_Config *, struct SPI_Transaction *)() at SPI.c:122 0x0000720A 
read9252SPIData(unsigned char *)() at spiloopback.c:485 0x00001AB0 
<...more frames...>

In mu .c fle :

    masterSpi = SPI_open(Board_SPI_16bit_DAC, &masterSpiParams);

In my Board.h file :

#define Board_SPI_16bit_DAC         EK_TM4C123GXL_SPI1

In my EK_TM4C123GXL.h file :

typedef enum EK_TM4C123GXL_SPIName {
EK_TM4C123GXL_SPI0 = 0,
EK_TM4C123GXL_SPI2,
EK_TM4C123GXL_SPI3,
EK_TM4C123GXL_SPI1,

EK_TM4C123GXL_SPICOUNT
} EK_TM4C123GXL_SPIName;

In my EK_TM4C123GXL.c file :

/*
* =============================== SPI ===============================
*/
/* Place into subsections to allow the TI linker to remove items properly */
#if defined(__TI_COMPILER_VERSION__)
#pragma DATA_SECTION(SPI_config, ".const:SPI_config")
#pragma DATA_SECTION(spiTivaDMAHWAttrs, ".const:spiTivaDMAHWAttrs")
#endif

#include <ti/drivers/SPI.h>
#include <ti/drivers/spi/SPITivaDMA.h>

/* SPI objects */
SPITivaDMA_Object spiTivaDMAObjects[EK_TM4C123GXL_SPICOUNT];
#if defined(__TI_COMPILER_VERSION__)
#pragma DATA_ALIGN(spiTivaDMAscratchBuf, 32)
#elif defined(__IAR_SYSTEMS_ICC__)
#pragma data_alignment=32
#elif defined(__GNUC__)
__attribute__ ((aligned (32)))
#endif
uint32_t spiTivaDMAscratchBuf[EK_TM4C123GXL_SPICOUNT];

/* SPI configuration structure */
const SPITivaDMA_HWAttrs spiTivaDMAHWAttrs[EK_TM4C123GXL_SPICOUNT] = {
{
SSI0_BASE,
INT_SSI0,
~0, /* Interrupt priority */
&spiTivaDMAscratchBuf[0],
0,
UDMA_CHANNEL_SSI0RX,
UDMA_CHANNEL_SSI0TX,
uDMAChannelAssign,
UDMA_CH10_SSI0RX,
UDMA_CH11_SSI0TX
},
{
SSI2_BASE,
INT_SSI2,
~0, /* Interrupt priority */
&spiTivaDMAscratchBuf[1],
0,
UDMA_SEC_CHANNEL_UART2RX_12,
UDMA_SEC_CHANNEL_UART2TX_13,
uDMAChannelAssign,
UDMA_CH12_SSI2RX,
UDMA_CH13_SSI2TX
},
{
SSI3_BASE,
INT_SSI3,
~0, /* Interrupt priority */
&spiTivaDMAscratchBuf[2],
0,
UDMA_SEC_CHANNEL_TMR2A_14,
UDMA_SEC_CHANNEL_TMR2B_15,
uDMAChannelAssign,
UDMA_CH14_SSI3RX,
UDMA_CH15_SSI3TX
}
};

const SPI_Config SPI_config[] = {
{&SPITivaDMA_fxnTable, &spiTivaDMAObjects[0], &spiTivaDMAHWAttrs[0]},
{&SPITivaDMA_fxnTable, &spiTivaDMAObjects[1], &spiTivaDMAHWAttrs[1]},
{&SPITivaDMA_fxnTable, &spiTivaDMAObjects[2], &spiTivaDMAHWAttrs[2]},
{NULL, NULL, NULL},
};

/*
* ======== EK_TM4C123GXL_initSPI ========
*/
void EK_TM4C123GXL_initSPI(void)
{
/* SPI0 */
SysCtlPeripheralEnable(SYSCTL_PERIPH_SSI0);

/* Need to unlock PF0 */
GPIOPinConfigure(GPIO_PA2_SSI0CLK);
GPIOPinConfigure(GPIO_PA3_SSI0FSS);
GPIOPinConfigure(GPIO_PA4_SSI0RX);
GPIOPinConfigure(GPIO_PA5_SSI0TX);

GPIOPinTypeSSI(GPIO_PORTA_BASE, GPIO_PIN_2 | GPIO_PIN_3 |
GPIO_PIN_4 | GPIO_PIN_5);


/* SPI1 */
SysCtlPeripheralEnable(SYSCTL_PERIPH_SSI1);

/* Need to unlock PF0 */
GPIOPinConfigure(GPIO_PF0_SSI1RX);
GPIOPinConfigure(GPIO_PF1_SSI1TX);
GPIOPinConfigure(GPIO_PF2_SSI1CLK);
GPIOPinConfigure(GPIO_PF3_SSI1FSS);

GPIOPinTypeSSI(GPIO_PORTF_BASE, GPIO_PIN_0 | GPIO_PIN_1 |
GPIO_PIN_2 | GPIO_PIN_3);


/* SSI2 */
SysCtlPeripheralEnable(SYSCTL_PERIPH_SSI2);

GPIOPinConfigure(GPIO_PB4_SSI2CLK);
GPIOPinConfigure(GPIO_PB5_SSI2FSS);
GPIOPinConfigure(GPIO_PB6_SSI2RX);
GPIOPinConfigure(GPIO_PB7_SSI2TX);

GPIOPinTypeSSI(GPIO_PORTB_BASE, GPIO_PIN_4 | GPIO_PIN_5 |
GPIO_PIN_6 | GPIO_PIN_7);

/* SSI3 */
/*
* NOTE: TI-RTOS examples configure pins PD0 & PD1 for SSI3 or I2C3. Thus,
* a conflict occurs when the I2C & SPI drivers are used simultaneously in
* an application. Modify the pin mux settings in this file and resolve the
* conflict before running your the application.
*/
SysCtlPeripheralEnable(SYSCTL_PERIPH_SSI3);

GPIOPinConfigure(GPIO_PD0_SSI3CLK);
GPIOPinConfigure(GPIO_PD1_SSI3FSS);
GPIOPinConfigure(GPIO_PD2_SSI3RX);
GPIOPinConfigure(GPIO_PD3_SSI3TX);

GPIOPinTypeSSI(GPIO_PORTD_BASE, GPIO_PIN_0 | GPIO_PIN_1 |
GPIO_PIN_2 | GPIO_PIN_3);

EK_TM4C123GXL_initDMA();
SPI_init();
}

  • 0
    TI__Mastermind 37985 points
    Jonathan,
    it seems that there is a Semaphore_pend call that's not coming from a Task context, but the timeout is not 0. I can't tell which of the relevant stack frames is your code. Is spiloopback.c your file? What's the name of the file where you call
    masterSpi = SPI_open(Board_SPI_16bit_DAC, &masterSpiParams);
  • 0 in reply to Sasha Slijepcevic
    Intellectual 570 points
    Hi Sasha,
    My main file is spiloopback.c. The call to masterSpi = SPI_open(Board_SPI_16bit_DAC, &masterSpiParams); is made from spiloopback.c.
    Jonathan
  • 0 in reply to Jonathan Duan
    TI__Mastermind 37985 points

    Jonathan,
    in the original example, the call to SPI_open comes from a Task function 'masterTskFxn'. Is that still a case in your code? If you moved the call to main(), I can see why you would Semaphore_pend not come from a Task context.
    Also, I see that you added SPI1 to the list of SPI names, but there is no corresponding structure in SPI_config. I am not familiar enough with SPI to figure out if that's OK, so I'll have to ask around.

  • 0 in reply to Sasha Slijepcevic
    Intellectual 570 points
    Yes, please check on the SPI configuration for me. I probably did not do it correctly. Maybe that's causing the problem.

    I am still calling SPI_open from a task function. At least I believe I am. I can send the spiloopback.c source file to you by private email for your review.
  • 0 in reply to Jonathan Duan
    TI__Mastermind 37985 points
    Jonathan,
    if you want to use SPI1, you need to add appropriate configuration entries for it. You already added the name for SPI1 to EK_TM4C123GXL_SPIName, but you also need to add a corresponding entry to spiTivaDMAHWAttrs, and then refer to that entry in SPI_config:
    const SPI_Config SPI_config[] = {
    {&SPITivaDMA_fxnTable, &spiTivaDMAObjects[0], &spiTivaDMAHWAttrs[0]},
    {&SPITivaDMA_fxnTable, &spiTivaDMAObjects[1], &spiTivaDMAHWAttrs[1]},
    {&SPITivaDMA_fxnTable, &spiTivaDMAObjects[2], &spiTivaDMAHWAttrs[2]},
    {&SPITivaDMA_fxnTable, &spiTivaDMAObjects[3], &spiTivaDMAHWAttrs[3]},
    {NULL, NULL, NULL},
    };

    I am not really sure how to initialize spiTivaDMAHWAttrs[3] for SPI1. Developers who may be able to tell you more will be in the office on Monday. Also, I see that you added SPI1 related code to initSPI, which is also needed but I can't tell if that code is valid.