• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 250 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDA4VM: How to configure the DMA channel of SPI.

JIAN WANG
Prodigy 30 points
Part Number: TDA4VM

When configuring MCAL using the EB tool, it can be seen in the SPI module that SPI can support DMA for data transmission. So, may I ask how to configure the values in SpiDmaTxChIntrNum and SpiDmaRxChIntrNum, what documents need to be referenced, and where specific information can be found in the documents.

Thank you very much.

  • +1
    TI__Mastermind 24835 points

    Hello,

    sorry for the delay.

    we have these details as part of mcusw user guide document.

    https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/ug_spi_top.html

    Here you can find 

    "Dedicated interrupt lines are available from DMA after event completion to the R5 core (80-90 for MCU1_0) and (229 to 247 for MCU2_1)"

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 30 points

    Hello,

    I would like to add a question. I have configured MCSPI3 and MCSPI5 in EB, and both use DMA mode. In addition, I registered the relevant DMA interrupt in Autosar OS, with the interrupt type being CAT1. However, when using SPI to send data, it was found that SPI_ The value returned by GetHWUnitStatus is not SPI_ IDLE, I believe that the SPI function is abnormal. However, the configuration is correct in both EB and OS, and it is currently unknown where the problem occurred. So please ask where the problem should be.

  • 0 in reply to JIAN WANG
    TI__Mastermind 24835 points

    Hello,

    MCSPI example app is ported and tested with single MCSPI instance on MCU1_0 and MCU2_1 cores using UDMA MCU and MAIN NAVSS respectively. MCU MCSPI Instance on MCU1_0 core and MCSPI3 Instance on MCU2_1.Please go through the respective examples in the SDK.

    MCSPI3 is connected as a master to MCU_MCSPI1 by default at power-up. MCU_MCSPI1 and MCSPI3 may be optionally mapped to external device pads.

    To enable MCU_MCSPI1 and MCSPI3 independently pin out. We just need to break the connection between MCU_MCSPI1 and MAIN_MCSPI3 and this is done by setting CTRLMMR_MCU_SPI1_CTRL[0] SPI1_LINKDIS register field to 1.

    Regards

    Tarun Mukesh