Re: [U-Boot-Users] Patch: Support for Motorola PQ2FADS-ZU board
Hi Yuli,
I have a PQ2FADS-ZU board with a 8270 and am having trouble getting the ethernet working. I was wondering if you were able to get yours functional. When I do:
tftp 0x0 host/memtest.bin
it shows:
=> tftp 0x0 host/memtest.bin TFTP from server 10.186.20.95; our IP address is 10.186.20.99 Filename 'host/memtest.bin'. Load address: 0x0 Loading: T T T T ...
Everytime the T occurs the collision light comes on on my 10 Mbit-only hub.
I commented out the 1st line of:
miiphy_write(0, 16, 0x610); miiphy_write(0, PHY_BMCR, PHY_BMCR_AUTON | PHY_BMCR_RST_NEG);
because bit 0x400 on register 16 on the Davicom 9161 part doesn't exist but it had no effect.
One idea I have is that the speed (baud) is wrong but I couldn't find anywhere to set it in the docs.
Any ideas/help are greatly appreciated.
Rick Bronson
Rick Bronson writes:
Rick> Hi Yuli, I have a PQ2FADS-ZU board with a 8270 and am having Rick> trouble getting the ethernet working. I was wondering if you Rick> were able to get yours functional.
Yes, I was. My card is connected to LAN and works OK.
Rick> When I do:
Rick> tftp 0x0 host/memtest.bin
Rick> it shows:
Rick> => tftp 0x0 host/memtest.bin TFTP from server 10.186.20.95; Rick> our IP address is 10.186.20.99 Filename 'host/memtest.bin'. Rick> Load address: 0x0 Loading: T T T T ...
Rick> Everytime the T occurs the collision light comes on on my 10 Rick> Mbit-only hub.
I haven't got 10Mbit hardware so I can't test in such an environment but I can think about some possible problems. By default, FCC is configured for full-duplex operation. Try to configure it for half-duplex by changing CFG_FCC_PSMR in MPC8260ADS.h. Also check in PHY status registers (5, 6, and 17) results of auto-negotiation.
Rick> I commented out the 1st line of:
Rick> miiphy_write(0, 16, 0x610); Rick> miiphy_write(0, PHY_BMCR, PHY_BMCR_AUTON | PHY_BMCR_RST_NEG);
Rick> because bit 0x400 on register 16 on the Davicom 9161 part Rick> doesn't exist but it had no effect.
According to the Data Sheet (p.27) bit 0x400 is 100Base-TX Mode Control. Bit 0x200 is reserved and it's always 1. Try writing 0x210.
Rick> One idea I have is that the speed (baud) is wrong but I Rick> couldn't find anywhere to set it in the docs.
By default, auto-negotiation is enabled so the PHY must determine correct speed automatically. If you want to force it to 10Mbit/s half-duplex mode (it's what your hub supports) just write 0 to register 0 (BMCR).
Rick> Any ideas/help are greatly appreciated.
Hope this helps,
Hi Yuli,
Thanks very much for the help. I really appreciate it.
I got it to work by bypassing the hub and using a straight thru cross over cable to my PC. I'm on my way to buy a switching hub ;-) But I found that even to get this to work required two things:
1. The MII/RMII switch (JP2) MUST be in the MII mode. 2. The ethaddr doesn't seem to like xf:xx:xx:xx:xx
setenv ethaddr 12:aa:bb:cc:dd:ee # works setenv ethaddr 1f:aa:bb:cc:dd:ee # doesn't work setenv ethaddr ff:aa:bb:cc:dd:ee # doesn't work setenv ethaddr 0f:aa:bb:cc:dd:ee # doesn't work
Just thought I'd let you know.
Thanks again for the help.
Rick
Dear Rick,
in message E19fm59-0000GX-00@c-67-164-43-44.client.comcast.net you wrote:
- The ethaddr doesn't seem to like xf:xx:xx:xx:xx
This has nothing to do with "to like" or not to like.
This has a lot to do with standards.
It is definitely a Bad Idea to use random MAC addresses.
All this has been discussed here before. More than once.
Wolfgang Denk
participants (3)
-
Rick Bronson -
Wolfgang Denk -
Yuli Barcohen