Linux/DP83620: Use DP83620 as fiber mode,could not ping

Hi Chitransh,

Did you use section 2.9 of the user guide to determine fiber modifications for the 620 EVK? www.ti.com/.../snlu002.pdf

Which fiber transceiver are you using? Is the FX_SD signal properly routed to the 620? Some fiber transceivers provide a LOS pin instead of SD pin, which will cause the 620 to not establish communications.

It is hard to tell if the Linux driver is causing problems at this time. One way to determine where the problem could be is to probe the MII signals on the header like PRXD0. If there is activity on that line, then the PHY is receiving data and the problem is with the driver. If there is no activity on PRXD0 or PRXDV, then the problem is likely with the hardware.

Best Regards,

Hello Rob,

I have made the modification as per section 2.9 in the EVK document.
The transceiver that I am using is Avago's "AFBR 5803ATZ". I hope DP98620 supports this transceiver.
To route the the FX_SD signal the document suggests suffing a 0 ohms at R128 position which I already did.

I can definitely probe the signals at the locations and will update.

P.S.
I need to understand that can an uneven soldering at the resistor points affect this communication and what will be the max TX/RX speed which 620 can provide in the outputs can I use a jumper instead of 0 Ohms resister since these are quite small. :-)

Thank you.

Hi Chitransh,

I will wait to see the signals being probed. If you have register access, it will also be helpful to provide register values for addresses 0x0 to 0x1f when the fiber transceiver is connected.

Uneven soldering of the resistors may be a problem, if they are a problem, we will see RX symbol errors indicated in the 620 registers. The TX/RX speed is fixed to 100M by the standard, so any soldering issue cannot be fixed by running the interface slower if that is what you are asking.

Best Regards,

Hello Rob,
I tried probing the header PRXD0 using an oscilloscope and did not observed any activity on the line.
The MDIO and MDC line show the signals on probing.

TO confirm that the IC on the DP83620 EVK is working fine i reconfigured it in the copper mode which is functioning well.

About the register access details:
- I tried using the USB-2-MDIO TI's software but the EVK is not getting recognized. Does it need some USB drivers?
- Does the 620 EVK support register access via USB or some software?

Also on reading the schematic sheet 7 of the EVK demo board. the circuit suggest that there are some registers 130 Ohms and 80 Ohms which are to be stuffed for the FO transceiver, i tried using that too but still no response.

Kinldy suggest further.

Thank you.

Hi Chitransh,

Good... no activity on PRXD0 or PRXDV indicates that the 620 is not receiving anything on the wire, or does not have a link up.  This means you do not have to consider driver problems on Linux at this point.

About the register access details:

- I tried using the USB-2-MDIO TI's software but the EVK is not getting recognized. Does it need some USB drivers?  

[Rob] The common issues for USB-2-MDIO problems are 1. incorrect PHY ID and 2. Using extended register access mode

The DP83620 doesn't support extended register access mode, so this must be set to No.

Also ensure your PHY ID is correct, once extended register option is set to No, use the Find PHY ID function in the File menu.

- Does the 620 EVK support register access via USB or some software?

[Rob] Yes, but it is a very complicated process that involves a virtual machine running windows XP and very old drivers.  I recommend using USB-2-MDIO.

In the EVK, you need to ensure all the passive components in schematic sheet 7 for fiber mode. In sheet 6, R112, R115, R119, and R116 should be removed.

From there, you should verify when you connect your FO transceiver, you get a high level on the SD line.  This will tell the DP83620 that a valid optical link is present.

Once that has all been confirmed, we must look at your MDIO registers for any further information to continue debugging.

Best Regards,

 

Hello Rob,

I am attaching the USB port of the EVK to my laptop and when running the USB-2-MDIO is shows HW disconnected. (Image attached)

I presume the connection to DP83620 requires MSP430 board as well.

I have a EK-TM4C123GXL, can this be used and how.?

Appreciate your support.

Thank you.

Hi Chitransh,

The USB-2-MDIO FW is not ported to the EK-TM4C123GXL.

I do not see your image you attached. Can you please try to reattach it.

The DP83620 EVK cannot be directly plugged into your USB and rub USB-2-MDIO. You need a MSP430F5529 LaunchPad to use USB-2-MDIO with the EVK.

Best Regards,

Hello Rob,

Got into a weird situation this FO mode is not working any more and I am yet to find out the reason for this.

To check whether the PHY is alright ,I rewired it into the Copper mode and to my surprise even the copper mode is not functioning now and I am getting "Could not mark the interface up", "eth1 device not found" on my linux console. MDIO and MDC pins are showing the activity.

i believe getting into the registers would be need to get this through. but I am struggling a bit as the timelines are stringent.

About the USB 2 MDIO tool, Can you help me in compiling the source code for either of below development boards:
- TI's EK-TM4C123GXL
- Raspberry PI3 - Model B
- STM32 discovery board

or you can guide on "...very complicated process that involves a virtual machine running windows XP and very old drivers..." as you said above.

Appreciate your help so far on this.

Thank you.

Hi Chitransh,

The process is below to access the DP836x0 EVKs from Windows XP:

1.       I have a fresh virtual machine on my Win 7 64-bit laptop.

a.       It is the virtual machine provided by Microsoft.  Follow this tutorial:

2.       I have downloaded Analog LaunchPAD Ethernet Integrity Framework Utility from this link:

3.       I have downloaded the Cypress USB drivers from this link:

4.       Move ALP and Cypress driver downloads into XP virtual machine

5.       Install national_ALPF.exe on Windows XP virtual machine

a.       ALP will run and say it didn’t detect an EVK, then go into demo mode.  If it does this, just close ALP and continue on.

6.       Navigate to XP machine’s C:\Program Files\National Semiconductor Corp\Analog LaunchPAD v1.26.0002\Drivers path

7.       Move Cypress driver files to this location.  I moved over the entire wxp folder in the Cypress download

8.       Now attach the DP83640-EVK to the Windows XP machine using the USB tab.  It will likely be called “Unidentified Device”

9.       Windows will ask for drivers, tell it to find the drivers in the path: C:\Program Files\National Semiconductor Corp\Analog LaunchPAD v1.26.0002\Drivers

10.    Accept the warning that the drivers aren’t signed or verified

a.       If drivers are successful, the USB will enumerate a device named “NSC ALP Nano”

11.   Run Analog LaunchPAD and you should get no warnings, and under the devices tab you should see “ALP Nano USB 1” and DP83640

12.   Then click on DP83640 in the devices tab on the left and you should get status information and other tabs you can use to evaluate the board

Best Regards,

Hello Rob,

I followed the instruction and installed the necessary tools.

On the file instruction I am getting the error "DP83640_Nano_GUI" and unable to access the registers. Attaching the image for reference.

I tried searching this code on the web but there is no information on this bit.Kindly help me fix these.

Are there some specific jumper setting i need to alter on the EVK-DP83620 for this?

Thank you.

I also tried installing the python 2.4.4 and the "ALP profile update.exe" still I am getting the same issue.

Appreciate your support rob.

Hello Rob,

I am expecting some support.

You may also share some manual or similar document for getting this through.

Kindly share your thoughts.

Thanks!

Hi Chitransh,

I do not have a solution for the error in the python script. This may be due to using DP83620 EVK, but I am not the originator of the GUI source code, so debug is extremely difficult.

I also cannot compile the USB-2-MDIO source code for new targets for you.

At this point, the path will be for you to order an MSP430F5529 LaunchPad.

Best Regards,