Hi,
I have KSZ9031RNX phy using rgmii interface but the address is 0x3, does this work with existing generic phy driver ? I get failed to read bmcr, while doing tftp.
Thanks & Reagrds,
Mike
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.
Mike,
mike A said:I have KSZ9031RNX phy using rgmii interface but the address is 0x3
I think you should update the code to apply this change.
See the below links:
http://processors.wiki.ti.com/index.php/TI81xx_PSP_Porting_Guide#Miscellaneous_details
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/358952.aspx
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/247923.aspx
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/269151.aspx
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/353786.aspx
mike A said:I get failed to read bmcr, while doing tftp.
Please provide full boot up log.
BR
Pavel
Hi Pavel,
Here is the complete boot log:
DRAM: 2 GiB
DCACHE: Off
MMC: OMAP SD/MMC: 0
Using default environment
Loading 2nd stage U-Boot...
Hit any key to stop autoboot: 0
reading u-boot.bin
178096 bytes read
## Starting application at 0x80800000 ...
I2C: ready
DRAM: 2 GiB
DCACHE: On
NAND: HW ECC BCH8 Selected
512 MiB
MMC: OMAP SD/MMC: 0
Net: Detected MACID:84:7e:40:f4:f1:12
cpsw
Hit any key to stop autoboot: 0
DM814X#
DM814X#mii info
DM814X#mii dump 0
Error reading from the PHY addr=00 reg=00
DM814X#tftp
phyid: ffffffff
failed to read bmcr
Using cpsw device
TFTP from server 192.168.1.115; our IP address is 192.168.1.105
Filename 'uImage'.
Load address: 0x81000000
Loading: *
Abort
DM814X#
Thanks & Regards,
Mike
Mike,
mike A said:Here is the complete boot log:
DRAM: 2 GiB
DCACHE: Off
MMC: OMAP SD/MMC: 0
Using default environment
Loading 2nd stage U-Boot...
Hit any key to stop autoboot: 0
reading u-boot.bin
178096 bytes read
## Starting application at 0x80800000 ...
I2C: ready
DRAM: 2 GiB
DCACHE: On
NAND: HW ECC BCH8 Selected
512 MiB
MMC: OMAP SD/MMC: 0
Net: Detected MACID:84:7e:40:f4:f1:12
cpsw
Hit any key to stop autoboot: 0
DM814X#
DM814X#mii info
DM814X#mii dump 0
Error reading from the PHY addr=00 reg=00
DM814X#tftp
phyid: ffffffff
failed to read bmcr
Using cpsw device
TFTP from server 192.168.1.115; our IP address is 192.168.1.105
Filename 'uImage'.
Load address: 0x81000000
Loading: *
Abort
DM814X#
Below is how I use the tftp command:
Net: <ethaddr> not set. Reading from E-fuse
Detected MACID:90:d7:eb:d5:13:96
cpsw
Hit any key to stop autoboot: 0
TI8148_EVM#setenv autoload no
TI8148_EVM#dhcp
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 172.20.0.110
TI8148_EVM#setenv serverip 172.20.1.195
TI8148_EVM#setenv nfsserver 172.20.1.195
TI8148_EVM#tftp 0x81000000 uImage
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 172.20.1.195; our IP address is 172.20.0.110
Filename 'uImage'.
Load address: 0x81000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
####################
done
Bytes transferred = 2762004 (2a2514 hex)
TI8148_EVM#
Can you try this flow at your side? The serverip and nfsserver is the ip of your host PC.
BR
Pavel
Hi Pavel,
The problem in first place is I am not able to read mii registers itself. If you look at my boot log you can see that error.
Do I need to add support for the phy driver or the generic phy driver will work ? How can I change the phy address to 3 ?
Thanks & Regards,
Mike
Mike,
mike A said:The problem in first place is I am not able to read mii registers itself. If you look at my boot log you can see that error.
What do you mean by "mii registers"? Are these the DM814x EMAC registers? Or the external eth PHY registers? There is no mii command in u-boot.
mike A said:Do I need to add support for the phy driver or the generic phy driver will work ?
The u-boot ethernet driver is generic and should work fine.
mike A said:How can I change the phy address to 3 ?
See the below links:
http://processors.wiki.ti.com/index.php/TI81xx_PSP_Porting_Guide#Miscellaneous_details
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/358952.aspx
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/247923.aspx
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/269151.aspx
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/353786.aspx
BR
Pavel
Hi Pavel,
Here is the o/p of mii command on 8148 evm:
ti8148_evm#mii info
PHY 0x00: OUI = 0x1374, Model = 0x07, Rev = 0x04, 10baseT, HDX
PHY 0x01: OUI = 0x1374, Model = 0x07, Rev = 0x04, 1000baseT, FDX
ti8148_evm#mii dump 1
0. (3100) -- PHY control register --
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:2000) 0. 6,13 = b01 speed selection = 100 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)
CONFIG_CMD_MII needs to enabled to get mii command.
Thanks & Regards,
Mike