No MAC ports show up in Linux in T1024RDB

cancel
Showing results for 
Search instead for 
Did you mean: 

No MAC ports show up in Linux in T1024RDB

1,037 Views
pratik_vadher
Contributor II

Hi, I am trying to set mac address in T1024RDB. However while trying show all connections with 'ifconfig -a' no mac ports show up. Log is attached 

root@t1024rdb:~# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-10-11-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Tags (1)
0 Kudos
14 Replies

909 Views
ufedor
NXP TechSupport
NXP TechSupport

Please provide U-Boot log.

0 Kudos

909 Views
pratik_vadher
Contributor II

U-Boot 2016.012.0+ga9b437f (Feb 18 2020 - 04:32:18 +0530)

CPU0: T1024E, Version: 1.0, (0x85480010)
Core: e5500, Version: 2.1, (0x80241021)
Single Source Clock Configuration
Clock Configuration:
CPU0:1200 MHz, CPU1:1200 MHz,
CCB:400 MHz,
DDR:800 MHz (1600 MT/s data rate) (Asynchronous), IFC:100 MHz
QE:200 MHz
FMAN1: 600 MHz
QMAN: 400 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 0810000c 00000000 00000000 00000000
00000010: 4a800003 80000012 ec027000 21000000
00000020: 00000000 00000000 00000000 00030810
00000030: 00000000 0b005a08 00000000 00000006
I2C: ready
Board: T1024RDB, Board rev: 0x03 CPLD ver: 0x07, boot from NOR vBank4
SERDES Reference Clocks:
SD1_CLK1=156.25MHZ, SD1_CLK2=100.00MHZ
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM 18KSF51272AZ-1G6K1
2 GiB left unmapped
4 GiB (DDR3, 64-bit, CL=11, ECC on)
DDR Chip-Select Interleaving Mode: CS0+CS1
Flash: 128 MiB
L2: 256 KiB enabled
Corenet Platform Cache: 256 KiB enabled
Using SERDES1 Protocol: 149 (0x95)
SEC0: RNG instantiated
NAND: 1024 MiB
MMC: FSL_SDHC: 0
QE microcode not found
EEPROM: Invalid ID (ff ff ff ff)
PCIe1: Root Complex, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe250000
PCIe2: Bus 01 - 01
PCIe3: Root Complex, no link, regs @ 0xfe260000
PCIe3: Bus 02 - 02
In: serial
Out: serial
Err: serial
Net: Fman1: Uploading microcode version 107.4.2
FM1@DTSEC3
Error: FM1@DTSEC3 address not set.
, FM1@DTSEC4 [PRIME]
Error: FM1@DTSEC4 address not set.
, FM1@TGEC1
Error: FM1@TGEC1 address not set.

Hit any key to stop autoboot: 0
=> bootm 0xe8020000 0xe9300000 0xe8800000

0 Kudos

909 Views
ufedor
NXP TechSupport
NXP TechSupport

Please provide log of the "printenv".

0 Kudos

909 Views
pratik_vadher
Contributor II

Please note that in the log, one static ip is set. I tried using uboot env variables to set ip. It did not work

Here's the log

Hit any key to stop autoboot: 0
=> printenv
FM1@DTSEC3=192.168.14.56
baudrate=115200
bdev=sda3
bootargs=root=/dev/ram rw console=ttyS0,115200
bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;setenv ramdiskaddr 0x02000000;setenv fdtaddr 0x00c00000;setenv loadaddr 0x1000000;bootm $loadaddr $ramdiskaddr $fdtaddr
bootdelay=10
bootfile=uImage
consoledev=ttyS0
ethact=FM1@DTSEC4
ethprime=FM1@DTSEC4
fdtaddr=c00000
fdtfile=t1024rdb/t1024rdb.dtb
fman_ucode=eff00000
hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1
loadaddr=1000000
netdev=eth0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
ramdiskaddr=2000000
ramdiskfile=t1024rdb/ramdisk.uboot
rootpath=/opt/nfsroot
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize
uboot=u-boot.bin
ubootaddr=0xeff40000
usb1:dr_mode=host,phy_type=utmi

0 Kudos

909 Views
ufedor
NXP TechSupport
NXP TechSupport

There are no MAC addresses for the Ethernet controllers.

Did you preserve firmware image which was installed on the brand-new RDB board?

Also MAC addresses can be printed on an on-board sticker.

0 Kudos

909 Views
pratik_vadher
Contributor II

No, I don't think we have preserved firmware image pre-installed with the brand new board. Two things: how do I get the MAC addresses now and we also have a brand new board, do you have any work instructions on how to store the original image onto any PC?

0 Kudos

909 Views
ufedor
NXP TechSupport
NXP TechSupport

> how do I get the MAC addresses now

Have you searched the board PCB and the case for a sticker with original (factory) MAC addresses?

> we also have a brand new board

Execute "printenv" on this board and provide the log.

0 Kudos

909 Views
pratik_vadher
Contributor II

I'll get the MAC addresses printed on the PCB in a while since I am working remotely

Log for brand new board T1042RDB:

=> printenv
baudrate=115200
bdev=sda3
bootargs=root=/dev/ram rw console=ttyS0,115200
bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000
bootdelay=3
bootfile=uImage
c=ffe
consoledev=ttyS0
eth1addr=00:04:9F:06:55:4E
eth2addr=00:04:9F:06:55:4F
eth3addr=00:04:9F:06:55:50
eth4addr=00:04:9F:06:55:51
eth5addr=00:04:9f:8e:7b:b4
ethact=FM1@DTSEC1
ethaddr=00:04:9F:06:55:4D
ethprime=e1000#0
fdtaddr=2000000
fdtfile=uImage-t1042d4rdb.dtb
fileaddr=2000000
filesize=9a83
fman_ucode=eff00000
hvboot=setenv bootargs console=$consoledev,$baudrate config-addr=0xfe8900000;bootm 0xfe8700000 - 0xfe8800000
hwconfig=fsl_ddr:bank_intlv=cs0_cs1
ipaddr=192.168.2.105
loadaddr=1000000
netdev=eth0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
nohvboot=tftp 1000000 $dir/$bootfile;tftp 5000000 $dir/$ramdiskfile;tftp 2000000 $dir/$fdtfile;setenv bootargs root=/dev/ram rw console=ttyS0,115200 $othbootargs;bootm 1000000 5000000 2000000;
othbootargs=ramdisk_size=1000000
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr
ramdiskaddr=5000000
ramdiskfile=fsl-image-core-t1042d4rdb.ext2.gz.u-boot
rootpath=/opt/nfsroot
serverip=192.168.2.1
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize
uboot=u-boot.bin
ubootaddr=0xeff40000

0 Kudos

909 Views
ufedor
NXP TechSupport
NXP TechSupport

On the problem board you have to create environment variables similar to:

eth1addr=00:04:9F:06:55:4E
eth2addr=00:04:9F:06:55:4F
eth3addr=00:04:9F:06:55:50
eth4addr=00:04:9F:06:55:51
eth5addr=00:04:9f:8e:7b:b4

As a temporary measure it is possible to "clone" this MAC addresses to the problem board.

0 Kudos

909 Views
pratik_vadher
Contributor II

Hi, I used Uboot-environment variables to set the addresses, but did not work. here's the log for printenv 

=> printenv
FM1@DTSEC3=00:04:9F:06:55:4E
FM1@DTSEC4=00:04:9F:06:55:4F
baudrate=115200
bdev=sda3
bootargs=root=/dev/ram rw console=ttyS0,115200
bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;setenv ramdiskaddr 0x02000000;setenv fdtaddr 0x00c00000;setenv loadaddr 0x1000000;bootm $loadaddr $ramdiskaddr $fdtaddr
bootdelay=10
bootfile=uImage
consoledev=ttyS0
eth1addr=00:04:9F:06:55:4E
eth2addr=0:04:9F:06:55:4F
eth3addr=00:04:9F:06:55:50
eth4addr=00:04:9F:06:55:51
eth5addr=00:04:9f:8e:7b:b4
ethact=FM1@DTSEC4
ethprime=FM1@DTSEC4
fdtaddr=c00000
fdtfile=t1024rdb/t1024rdb.dtb
fman_ucode=eff00000
hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1
loadaddr=1000000
netdev=eth0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
ramdiskaddr=2000000
ramdiskfile=t1024rdb/ramdisk.uboot
rootpath=/opt/nfsroot
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize
uboot=u-boot.bin
ubootaddr=0xeff40000
usb1:dr_mode=host,phy_type=utmi

As of now, I am trying to use older SDK 1.7 to extract an older version of uboot and fman code (if present) since this is somewhat older board.

0 Kudos

909 Views
pratik_vadher
Contributor II

Hi I used an older Uboot version and Fman code compiled from SDK 1.7 and the error which appeared in setting FM1@DTSEC4 in Uboot log no longer does. However still I am not getting the ethernet options. I am not able to set MAC addresses. I am attaching the uboot log for your reference.

U-Boot 2014.07QorIQ-SDK-V1.7+g659b6a2 (Jul 23 2020 - 10:29:16)

CPU0: T1024E, Version: 1.0, (0x85480010)
Core: e5500, Version: 2.1, (0x80241021)
Single Source Clock Configuration
Clock Configuration:
CPU0:1200 MHz, CPU1:1200 MHz,
CCB:400 MHz,
DDR:800 MHz (1600 MT/s data rate) (Asynchronous), IFC:100 MHz
QE:200 MHz
FMAN1: 600 MHz
QMAN: 400 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 0810000c 00000000 00000000 00000000
00000010: 4a800003 80000012 ec027000 21000000
00000020: 00000000 00000000 00000000 00030810
00000030: 00000000 0b005a08 00000000 00000006
Board: T1024RDB, Board rev: 0x03 CPLD ver: 0x07, boot from NOR vBank4
SERDES Reference Clocks:
SD1_CLK1=156.25MHZ, SD1_CLK2=100.00MHZ
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM 18KSF51272AZ-1G6K1
4 GiB (DDR3, 64-bit, CL=11, ECC on)
DDR Chip-Select Interleaving Mode: CS0+CS1
Flash: 128 MiB
L2: 256 KiB enabled
Corenet Platform Cache: 256 KiB enabled
Using SERDES1 Protocol: 149 (0x95)
NAND: 1024 MiB
MMC: FSL_SDHC: 0
Not a microcode
EEPROM: Invalid ID (ff ff ff ff)
PCIe1: Root Complex, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe250000
PCIe2: Bus 01 - 01
PCIe3: Root Complex, no link, regs @ 0xfe260000
PCIe3: Bus 02 - 02
In: serial
Out: serial
Err: serial
Net: Fman1: Uploading microcode version 107.4.2
FM1@DTSEC3, FM1@DTSEC4 [PRIME], FM1@TGEC1
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
bdev=sda3
bootargs=root=/dev/ram rw console=ttyS0,115200
bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;setenv ramdiskaddr 0x02000000;setenv fdtaddr 0x00c00000;setenv loadaddr 0x1000000;bootm $loadaddr $ramdiskaddr $fdtaddr
bootdelay=10
bootfile=uImage
consoledev=ttyS0
eth1addr=00:04:9F:03:C7:4A
eth2addr=00:04:9F:03:C7:4B
eth3addr=00:04:9F:03:C7:49
eth4addr=00:04:9F:06:55:51
eth5addr=00:04:9f:8e:7b:b4
ethact=FM1@DTSEC4
ethprime=FM1@DTSEC4
fdtaddr=c00000
fdtfile=t1024rdb/t1024rdb.dtb
fman_ucode=eff00000
hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1
loadaddr=1000000
netdev=eth0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
ramdiskaddr=2000000
ramdiskfile=t1024rdb/ramdisk.uboot
rootpath=/opt/nfsroot
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize
uboot=u-boot.bin
ubootaddr=0xeff40000
usb1:dr_mode=host,phy_type=utmi

0 Kudos

909 Views
ufedor
NXP TechSupport
NXP TechSupport

> Also I have set the variables:  FM1@DTSEC3=00:04:9F:06:55:4E
> FM1@DTSEC4=00:04:9F:06:55:4F

Why you did that if required settings are:

eth1addr=00:04:9F:06:55:4E
eth2addr=00:04:9F:06:55:4F
eth3addr=00:04:9F:06:55:50
eth4addr=00:04:9F:06:55:51
eth5addr=00:04:9f:8e:7b:b4

Please consider using complete NOR Flash image provided in the QorIQ Linux SDK v2.0 PPC64E5500 IMAGE.iso which could be downloaded from:

Linux® SDK for QorIQ® Processors | NXP 

0 Kudos

909 Views
pratik_vadher
Contributor II

Hi, 

I was finally able to figure out and get the ethenet working, It is T1024RDB, and I was able to get the mac address from the tags on the board. I loaded older version of uboot and fman code (107.4.2) from SDK 1.7. This got the error in FM1@DTSEC3, FM1@DTSEC4 [PRIME], FM1@TGEC1 resolved

Then I set the address 'ethaddr' cause without it no ports started. And then I was able to get ETH0 and ETH1 working.

"QorIQ Linux SDK v2.0 PPC64E5500 IMAGE.iso", are this images, the completely test ones on RDB and guaranteed to work?

0 Kudos

909 Views
pratik_vadher
Contributor II

Also I have set the variables:  FM1@DTSEC3=00:04:9F:06:55:4E
FM1@DTSEC4=00:04:9F:06:55:4F

0 Kudos