Why phy(mdio) driver and ecspi1 confict?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Why phy(mdio) driver and ecspi1 confict?

1,842件の閲覧回数
guochgz
Contributor III

hello.

      I have faced a strange issues, that when I compiled the spi driver into the kernel, the PHY mdio can not get the chipID ex. got the value is 0xffffffff, but when I compile the spi driver to module,  and disabled ecspi1, the network is ok.

Is there a iomux confict? 

the following is the iomux define, pls tell me what's wrong? 

ECSPI1:

pastedImage_1.png

pastedImage_2.png

FEC1:

pastedImage_3.png

pastedImage_4.png

ラベル(1)
0 件の賞賛
返信
3 返答(返信)

1,718件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi 国承 张 

one can look at ecspi1 dts example

imx6ul-14x14-ddr3-arm2.dts\dts\boot\arm\arch - linux-imx - i.MX Linux kernel 

probably one can try to rebuild all image from scratch.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 件の賞賛
返信

1,718件の閲覧回数
guochgz
Contributor III

hi, igor

      the ecspi1 dts is the same with my ecspi1 define. 

      how to check this hex num like 0x10b0, 0x1b0b0

   pastedImage_1.png

   what does these fields mean? 

0 件の賞賛
返信

1,718件の閲覧回数
guochgz
Contributor III

this issue has been fixed, I have change nRST pins to another GPIO.

0 件の賞賛
返信