TDA4VH-Q1: Use SPI on MCU2_0

Hello,

jin zhu said:

I found three spi examples of MCU domain in the SPI driver code(SPI_soc.c) of rtos sdk, but only two groups of SPI can be configured in the sysconfig tool.

We have only 2 domains MCU and MAIN domain SPI instances .In MCU domain we have 3 SPI instances and MAIN domain we have 8 SPI instances.

Your pin mux configuration looks good.

The MCU_MCSPI1 and MCU_MCSPI2 modules include internal connectivity to the MCSPI3 and MCSPI4modules in the MAIN SoC domain. By default, the MAIN MCSPI3 is connected as Initiator to MCU_MCSPI1 as Target. Alternatively, MAIN MCSPI3 and MCU_MCSPI1 can be pinned out externally. 

You can refer https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1323100/tda4vm-mcu_spi1-cannot-work-while-mcu_spi0-is-working-well/5045028#5045028

Regards

Tarun Mukesh

Thank you for your reply.

I try to put myself as the master of SPI and then send the data.

But with no clock signal on the clock line (CLK).

My pinmux configuration is as follows:

static pinmuxPerCfg_t gMcu_spi1PinCfg[] =
{
    /* TC397_SPI1 -> MCU_SPI1_CLK -> H38 */
    {
        PIN_WKUP_GPIO0_0, PIN_MODE(0) | \
        ((PIN_PULL_DISABLE) & (~PIN_PULL_DIRECTION & ~PIN_INPUT_ENABLE))
    },
    /* TC397_SPI1 -> MCU_SPI1_CS0 -> J36 */
    {
        PIN_WKUP_GPIO0_3, PIN_MODE(0) | \
        ((PIN_PULL_DISABLE) & (~PIN_PULL_DIRECTION & ~PIN_INPUT_ENABLE))
    },
    /* TC397_SPI1 -> MCU_SPI1_D0 -> J34 */
    {
        PIN_WKUP_GPIO0_1, PIN_MODE(0) | \
        ((PIN_PULL_DISABLE | PIN_INPUT_ENABLE) & (~PIN_PULL_DIRECTION))
    },
    /* TC397_SPI1 -> MCU_SPI1_D1 -> J35 */
    {
        PIN_WKUP_GPIO0_2, PIN_MODE(0) | \
        ((PIN_PULL_DISABLE) & (~PIN_PULL_DIRECTION & ~PIN_INPUT_ENABLE))
    },
    {PINMUX_END}
};

Data line (D1)  waveform of the does not show actual data, but just pulls up the level.

CS line waveform is consistent with the data line.

(When idle, the data line (D1) is low, and the CS line is high),

Clock signal never appeared.

When idle, the data line (D1) is low, and the CS line is high.

When I call the SPI_transfer() interface, the data line (D1) is pulled up and kept high, and the CS line is pulled down and kept low.

When I call the SPI_transferCancel() interface, the data line and CS line go back to idle.

(Waveform change in the figure above is because I am calling the SPI_transfer() and SPI_transferCancel() interfaces periodically.)

After the SPI interface is changed to an MCSPI interface, the SPI master mode can send clock signals and data.

The slave device can receive data, but the master cannot receive the data returned from the slave device.

OK, thank you.