• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 182 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.

AM62P: DMA channel confilict between U-Boot/Linux and MCAL

Changxing Du
Prodigy 90 points
Part Number: AM62P

Tool/software:

Hello 

We configured dma channel  for CPSW at MCAL side. It affect  CPSW DMA  init because the channel looks already used by MCU.

Do you have any guide on how to avoide this confilict?

The device tree at U-Boot/Linux side is like this (dmas = <&main_pktdma 0xc600 15>,)， but at mcu  mcal side it is only channel number is configured, how converstion can be done to avoid conflict?

Any guide like for resource managment we can refer to?

B.R.

Changxing DU

  • 0
    Prodigy 90 points

    Here is the u-boot error:

    ti_sci system-controller@44043000: Message not acknowledged
    ti_sci system-controller@44043000: Message not acknowledged
    ti-udma dma-controller@485c0000: PSI-L pairing failed: 0x4600 -> 0x9013
    ti-udma dma-controller@485c0000: alloc dma res failed -19
    am65_cpsw_nuss_port ethernet@8000000port@1: RX dma get failed -22
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    ti_sci system-controller@44043000: Message not acknowledged
    ti_sci system-controller@44043000: Message not acknowledged
    ti-udma dma-controller@485c0000: PSI-L pairing failed: 0x4600 -> 0x9013
    ti-udma dma-controller@485c0000: alloc dma res failed -19
    am65_cpsw_nuss_port ethernet@8000000port@2: RX dma get failed -22
    am65_cpsw_nuss_port ethernet@8000000port@2: am65_cpsw_start end error