AM2432: EIP stack seems to be not working normally though dp83822 has been negotiated successfiully with pc

sigong

Part Number: AM2432
Other Parts Discussed in Thread: DP83826E

Hi experts，

Firstly,the EIP scanner in pc can works normally with the AM243x_LP running as a EIP adapter.

Secondly,I used the same scanner and made it work with my board which selects AM2432 and dp83822.The program in board is changed from that in AM243x_LP.

And dp83822 can be detected by the pc and negotiated at 100MHz successfully.

Here it is:

However,the problem is the board excutes and uart logs in ccs doesn't show any info about 'Forward open Connection' .

Here is the latter part of the uart logs by AM2432 board:

And here is the part of the logs by AM243x_LP:

+EI_API_ADP_pruicssStart
-EI_API_ADP_pruicssStart
Assembly 0x64 size: 0
Assembly 0x64 size: 2 (attrId 0x340)
Assembly 0x64 size: 4 (attrId 0x341)
Assembly 0x64 size: 6 (attrId 0x342)
Assembly 0x64 size: 8 (attrId 0x343)
Assembly 0x64 size: 10 (attrId 0x344)
Assembly 0x64 size: 12 (attrId 0x345)
Assembly 0x64 size: 14 (attrId 0x346)
Assembly 0x64 size: 16 (attrId 0x347)
Assembly 0x64 size: 18 (attrId 0x348)
Assembly 0x64 size: 20 (attrId 0x349)
Assembly 0x64 size: 22 (attrId 0x34a)
Assembly 0x64 size: 24 (attrId 0x34b)
Assembly 0x64 size: 26 (attrId 0x34c)
Assembly 0x64 size: 28 (attrId 0x34d)
Assembly 0x64 size: 30 (attrId 0x34e)
Assembly 0x64 size: 32 (attrId 0x34f)
Local interface IP is 192.168.1.11
EI_API_ADP_getMacAddr: 1c:63:49:25:19:d6
Configuration Size 64 byte
0x1 0x21 0x2 0x31 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x31 0x0 0x31 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Forward open Connection Serial Number: 0x1757

So,what's the problem?What I should do next?

regards

sigong

over 1 year ago

0 sigong over 1 year ago

Prodigy 250 points

If the problem is still related with the PHYs,what can I do to verify it?

0 Ashwani Goel over 1 year ago

TI__Mastermind 27310 points

Hi sigong,

Thanks for your query.

I will check on this and get back to you.

Regards

Ashwani

0 sigong over 1 year ago in reply to Ashwani Goel

Prodigy 250 points

Hi Ashwani，

I think it helpful to add these info.

The info about REG in logs is read and output in function 'CUST_PHY_DP83826E_setMIIMode' which is excuted in the initial process of dp83822.

Because when the initial period has been away,I could not use these phy_read or phy_write function.

From the logs,we can find :

BMCR 0x7849;

SOR1 0x2001;

SOR2 0x0000.

However,the value of SOR1 does not seem to match my hardware configuration.Is it related with the time of the read-execution?

Can you give me some advice?Thank you.

If more info are needed,please do not hesitate to tell me.

[MCSPI] Loopback example started 3
Pruicss  max =3 selected PRU:3
The data is corrupted, write default values.
Did Map 0x30080000 len 0x2000 to 0x30080000 (dram0)
Did Map 0x30082000 len 0x2000 to 0x30082000 (dram1)
Did Map 0x300b4000 len 0x4000 to 0x300b4000 (iram0)
Did Map 0x300b8000 len 0x4000 to 0x300b8000 (iram1)
Did Map 0x30090000 len 0x10000 to 0x30090000 (shdram)
Did Map 0x300a2000 len 0x400 to 0x300a2000 (control0)
Did Map 0x300a4000 len 0x400 to 0x300a4000 (control1)
Did Map 0x300a0000 len 0x2000 to 0x300a0000 (intc)
Did Map 0x300a6000 len 0x2000 to 0x300a6000 (cfg)
Did Map 0x300a8000 len 0x2000 to 0x300a8000 (uart0)
Did Map 0x300ae000 len 0x2000 to 0x300ae000 (iep)
Did Map 0x300b0000 len 0x2000 to 0x300b0000 (ecap0)
Did Map 0x300b2000 len 0x400 to 0x300b2000 (mii_rt)
Did Map 0x3009f000 len 0x1c00 to 0x3009f000 (mdio)
Did Map 0x3008a000 len 0x2000 to 0x3008a000 (txPru0Iram)
Did Map 0x3008c000 len 0x2000 to 0x3008c000 (txPru1Iram)
Did Map 0x300a5000 len 0x100 to 0x300a5000 (txPru0CtlReg)
Did Map 0x300a5000 len 0x100 to 0x300a5000 (txPru1CtlReg)
DP83826E detected
DP83826E detected
PRU_PHY_detect:185 Phy 1 alive
PRU_PHY_detect:185 Phy 4 alive
Phy 1 : REG[0x0000] = 0x3100
Phy 1 : REG[0x0001] = 0x7849
Phy 1 : REG[0x0002] = 0x2000
Phy 1 : REG[0x0003] = 0xA240
Phy 1 : REG[0x0004] = 0x01E1
Phy 1 : REG[0x0005] = 0x0000
Phy 1 : REG[0x0006] = 0x0004
Phy 1 : REG[0x0007] = 0x2001
Phy 1 : REG[0x0008] = 0x0000
Phy 1 : REG[0x0009] = 0x0000
Phy 1 : REG[0x000A] = 0x0100
Phy 1 : REG[0x000B] = 0x1040
Phy 1 : REG[0x000C] = 0x0000
Phy 1 : REG[0x000D] = 0x0000
Phy 1 : REG[0x000E] = 0x0000
Phy 1 : REG[0x000F] = 0x0000
Phy 1 : REG[0x0010] = 0x0002
Phy 1 : REG[0x0011] = 0x0108
Phy 1 : REG[0x0012] = 0x0000
Phy 1 : REG[0x0013] = 0x0000
Phy 1 : REG[0x0014] = 0x0000
Phy 1 : REG[0x0015] = 0x0000
Phy 1 : REG[0x0016] = 0x0100
Phy 1 : REG[0x0017] = 0x0041
Phy 1 : REG[0x0018] = 0x0400
Phy 1 : REG[0x0019] = 0x8021
Phy 1 : REG[0x001A] = 0x0000
Phy 1 : REG[0x001B] = 0x007D
Phy 1 : REG[0x001C] = 0x05EE
Phy 1 : REG[0x001D] = 0x0000
Phy 1 : REG[0x001E] = 0x0102
Phy 1 : REG[0x0467] = 0x2001
Phy 1 : REG[0x0468] = 0x0000

Phy 4 : REG[0x0000] = 0x3100
Phy 4 : REG[0x0001] = 0x7849
Phy 4 : REG[0x0002] = 0x2000
Phy 4 : REG[0x0003] = 0xA240
Phy 4 : REG[0x0004] = 0x01E1
Phy 4 : REG[0x0005] = 0x0000
Phy 4 : REG[0x0006] = 0x0004
Phy 4 : REG[0x0007] = 0x2001
Phy 4 : REG[0x0008] = 0x0000
Phy 4 : REG[0x0009] = 0x0000
Phy 4 : REG[0x000A] = 0x0100
Phy 4 : REG[0x000B] = 0x1040
Phy 4 : REG[0x000C] = 0x0000
Phy 4 : REG[0x000D] = 0x0000
Phy 4 : REG[0x000E] = 0x0000
Phy 4 : REG[0x000F] = 0x0000
Phy 4 : REG[0x0010] = 0x0002
Phy 4 : REG[0x0011] = 0x0108
Phy 4 : REG[0x0012] = 0x0000
Phy 4 : REG[0x0013] = 0x0000
Phy 4 : REG[0x0014] = 0x0000
Phy 4 : REG[0x0015] = 0x0000
Phy 4 : REG[0x0016] = 0x0100
Phy 4 : REG[0x0017] = 0x0041
Phy 4 : REG[0x0018] = 0x0400
Phy 4 : REG[0x0019] = 0x8024
Phy 4 : REG[0x001A] = 0x0000
Phy 4 : REG[0x001B] = 0x007D
Phy 4 : REG[0x001C] = 0x05EE
Phy 4 : REG[0x001D] = 0x0000
Phy 4 : REG[0x001E] = 0x0102
Phy 4 : REG[0x0467] = 0x2001
Phy 4 : REG[0x0468] = 0x0000

+EI_API_ADP_pruicssStart
-EI_API_ADP_pruicssStart
Assembly 0x64 size: 0
Assembly 0x64 size: 2 (attrId 0x340) 
Assembly 0x64 size: 4 (attrId 0x341) 
Assembly 0x64 size: 6 (attrId 0x342) 
Assembly 0x64 size: 8 (attrId 0x343) 
Assembly 0x64 size: 10 (attrId 0x344) 
Assembly 0x64 size: 12 (attrId 0x345) 
Assembly 0x64 size: 14 (attrId 0x346) 
Assembly 0x64 size: 16 (attrId 0x347) 
Assembly 0x64 size: 18 (attrId 0x348) 
Assembly 0x64 size: 20 (attrId 0x349) 
Assembly 0x64 size: 22 (attrId 0x34a) 
Assembly 0x64 size: 24 (attrId 0x34b) 
Assembly 0x64 size: 26 (attrId 0x34c) 
Assembly 0x64 size: 28 (attrId 0x34d) 
Assembly 0x64 size: 30 (attrId 0x34e) 
Assembly 0x64 size: 32 (attrId 0x34f) 
Local interface IP is 192.168.1.19
EI_API_ADP_getMacAddr:  1c:63:49:20:7c:d3

Regards

sigong

0 Ashwani Goel over 1 year ago in reply to sigong

TI__Mastermind 27310 points

Thanks sigong,

Which SDK you are working on ?

I understand that you are facing the problem when running EIP on custom PHY.

You are not facing any problem while executing EIP on AM243-lp and AM243-evm out of box. correct ?

software-dl.ti.com/.../INDUSTRIAL_COMMS_TI_STACK.html

Regards

Ashwani

0 sigong over 1 year ago in reply to Ashwani Goel

Prodigy 250 points

Thank you for the response.

The SDK in use is ind_comms_sdk_am243x_09_00_00_03.

And there is no problem currently while executing EIP on AM243x-lp.

Regards

sigong

0 sigong over 1 year ago in reply to sigong

Prodigy 250 points

Hi Ashwani,

I'm sorry for some wrong info because of wrong operations.

I changed the PHY's address ,rectifyed and executed the READ operation until the link-status LED is on.

Here is the latest logs:

Starting NULL Bootloader ... 

DMSC Firmware Version 8.6.4--v08.06.04 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

INFO: Bootloader_runCpu:155: CPU r5f1-0  is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU m4f0-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runSelfCpu:217: All done, reseting self ...

[MCSPI] Loopback example started 3
Pruicss  max =3 selected PRU:3
The data is corrupted, write default values.
Did Map 0x30080000 len 0x2000 to 0x30080000 (dram0)
Did Map 0x30082000 len 0x2000 to 0x30082000 (dram1)
Did Map 0x300b4000 len 0x4000 to 0x300b4000 (iram0)
Did Map 0x300b8000 len 0x4000 to 0x300b8000 (iram1)
Did Map 0x30090000 len 0x10000 to 0x30090000 (shdram)
Did Map 0x300a2000 len 0x400 to 0x300a2000 (control0)
Did Map 0x300a4000 len 0x400 to 0x300a4000 (control1)
Did Map 0x300a0000 len 0x2000 to 0x300a0000 (intc)
Did Map 0x300a6000 len 0x2000 to 0x300a6000 (cfg)
Did Map 0x300a8000 len 0x2000 to 0x300a8000 (uart0)
Did Map 0x300ae000 len 0x2000 to 0x300ae000 (iep)
Did Map 0x300b0000 len 0x2000 to 0x300b0000 (ecap0)
Did Map 0x300b2000 len 0x400 to 0x300b2000 (mii_rt)
Did Map 0x3009f000 len 0x1c00 to 0x3009f000 (mdio)
Did Map 0x3008a000 len 0x2000 to 0x3008a000 (txPru0Iram)
Did Map 0x3008c000 len 0x2000 to 0x3008c000 (txPru1Iram)
Did Map 0x300a5000 len 0x100 to 0x300a5000 (txPru0CtlReg)
Did Map 0x300a5000 len 0x100 to 0x300a5000 (txPru1CtlReg)
DP83826E detected
DP83826E detected
PRU_PHY_detect:185 Phy 3 alive
PRU_PHY_detect:185 Phy 15 alive
Phy 3 : REG[0x0000] = 0x3100
Phy 3 : REG[0x0001] = 0x786D
Phy 3 : REG[0x0002] = 0x2000
Phy 3 : REG[0x0003] = 0xA240
Phy 3 : REG[0x0004] = 0x01E1
Phy 3 : REG[0x0005] = 0xCDE1
Phy 3 : REG[0x0006] = 0x000F
Phy 3 : REG[0x0007] = 0x2001
Phy 3 : REG[0x0008] = 0x5806
Phy 3 : REG[0x0009] = 0x0000
Phy 3 : REG[0x000A] = 0x0100
Phy 3 : REG[0x000B] = 0x1000
Phy 3 : REG[0x000C] = 0x0000
Phy 3 : REG[0x000D] = 0x0000
Phy 3 : REG[0x000E] = 0x0000
Phy 3 : REG[0x000F] = 0x0000
Phy 3 : REG[0x0010] = 0x4615
Phy 3 : REG[0x0011] = 0x0108
Phy 3 : REG[0x0012] = 0x6400
Phy 3 : REG[0x0013] = 0x2800
Phy 3 : REG[0x0014] = 0x0000
Phy 3 : REG[0x0015] = 0x0000
Phy 3 : REG[0x0016] = 0x0100
Phy 3 : REG[0x0017] = 0x004D
Phy 3 : REG[0x0018] = 0x0400
Phy 3 : REG[0x0019] = 0x8C23
Phy 3 : REG[0x001A] = 0x0000
Phy 3 : REG[0x001B] = 0x007D
Phy 3 : REG[0x001C] = 0x05EE
Phy 3 : REG[0x001D] = 0x0000
Phy 3 : REG[0x001E] = 0x0102
Phy 3 : REG[0x0467] = 0x3FC3
Phy 3 : REG[0x0468] = 0x0000

Phy 15 : REG[0x0000] = 0x3100
Phy 15 : REG[0x0001] = 0x7849
Phy 15 : REG[0x0002] = 0x2000
Phy 15 : REG[0x0003] = 0xA240
Phy 15 : REG[0x0004] = 0x01E1
Phy 15 : REG[0x0005] = 0x0000
Phy 15 : REG[0x0006] = 0x0004
Phy 15 : REG[0x0007] = 0x2001
Phy 15 : REG[0x0008] = 0x0000
Phy 15 : REG[0x0009] = 0x0000
Phy 15 : REG[0x000A] = 0x0100
Phy 15 : REG[0x000B] = 0x1000
Phy 15 : REG[0x000C] = 0x0000
Phy 15 : REG[0x000D] = 0x0000
Phy 15 : REG[0x000E] = 0x0000
Phy 15 : REG[0x000F] = 0x0000
Phy 15 : REG[0x0010] = 0x4002
Phy 15 : REG[0x0011] = 0x0108
Phy 15 : REG[0x0012] = 0x0000
Phy 15 : REG[0x0013] = 0x0800
Phy 15 : REG[0x0014] = 0x0000
Phy 15 : REG[0x0015] = 0x0000
Phy 15 : REG[0x0016] = 0x0100
Phy 15 : REG[0x0017] = 0x0045
Phy 15 : REG[0x0018] = 0x0400
Phy 15 : REG[0x0019] = 0x802F
Phy 15 : REG[0x001A] = 0x0000
Phy 15 : REG[0x001B] = 0x007D
Phy 15 : REG[0x001C] = 0x05EE
Phy 15 : REG[0x001D] = 0x0000
Phy 15 : REG[0x001E] = 0x0102
Phy 15 : REG[0x0467] = 0xFFC3
Phy 15 : REG[0x0468] = 0x0003

+EI_API_ADP_pruicssStart
-EI_API_ADP_pruicssStart
Assembly 0x64 size: 0
Assembly 0x64 size: 2 (attrId 0x340) 
Assembly 0x64 size: 4 (attrId 0x341) 
Assembly 0x64 size: 6 (attrId 0x342) 
Assembly 0x64 size: 8 (attrId 0x343) 
Assembly 0x64 size: 10 (attrId 0x344) 
Assembly 0x64 size: 12 (attrId 0x345) 
Assembly 0x64 size: 14 (attrId 0x346) 
Assembly 0x64 size: 16 (attrId 0x347) 
Assembly 0x64 size: 18 (attrId 0x348) 
Assembly 0x64 size: 20 (attrId 0x349) 
Assembly 0x64 size: 22 (attrId 0x34a) 
Assembly 0x64 size: 24 (attrId 0x34b) 
Assembly 0x64 size: 26 (attrId 0x34c) 
Assembly 0x64 size: 28 (attrId 0x34d) 
Assembly 0x64 size: 30 (attrId 0x34e) 
Assembly 0x64 size: 32 (attrId 0x34f) 
Local interface IP is 192.168.1.19
EI_API_ADP_getMacAddr:  1c:63:49:20:7c:d3

About PHY 3:

BMCR 0x786D;

SOR1 0x3FC3;

SOR2 0x0000.

Maybe that is helpful to locate to the key point.Thank you.

Regards

sigong

0 Ashwani Goel over 1 year ago in reply to sigong

TI__Mastermind 27310 points

Hi sigong,

Let me know if below thread will be helpful?

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1341100/am2432-eip-connection-failure-occurs-with-using-dp83822

Regards

Ashwani

0 sigong over 1 year ago in reply to Ashwani Goel

Prodigy 250 points

Hi Ashwani,

The thread you metion is undergoing.

We all try to find the key point currently.

Regards

sigong

0 Ashwani Goel over 1 year ago in reply to sigong

TI__Mastermind 27310 points

sigong said:
The thread you metion is undergoing.

As it is same issue discussion going on.

Can we close this thread ?

Regards

Ashwani

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2432: EIP stack seems to be not working normally though dp83822 has been negotiated successfiully with pc