LS2085ARDB BSP support

ronakadesai · ‎09-30-2015

Hi, We have a LS2085ARDB devkit with us and we wanted to regenerate the binaries, which mainline kernel and uboot we should be using?

Another question is we wanted to tftp the board and we get following error, what could be wrong.

e1000: e1000#0: ERROR: Valid Link not detected

Following is the uboot console log,

U-Boot 2015.01Layerscape2-SDK+g16c10aa (May 14 2015 - 15:17:11)

SoC: LS2085E (0x87010010)

Clock Configuration:

CPU0(A57):1800 MHz CPU1(A57):1800 MHz CPU2(A57):1800 MHz

CPU3(A57):1800 MHz CPU4(A57):1800 MHz CPU5(A57):1800 MHz

CPU6(A57):1800 MHz CPU7(A57):1800 MHz

Bus: 600 MHz DDR: 1866.667 MT/s DP-DDR: 1600 MT/s

Reset Configuration Word (RCW):

00: 48303830 48480048 00000000 00000000

10: 00000000 00200000 00200000 00000000

20: 00c12980 00002580 00000000 00000000

30: 00000e0b 00000000 00000000 00000000

40: 00000000 00000000 00000000 00000000

50: 00000000 00000000 00000000 00000000

60: 00000000 00000000 00027000 00000000

70: 412a0000 00000000 00000000 00000000

Board: LS2085E-RDB, Board Arch: V1, Board version: D, boot from vBank: 0

FPGA: v1.18

SERDES1 Reference : Clock1 = 156.25MHz Clock2 = 156.25MHz

SERDES2 Reference : Clock1 = 100MHz Clock2 = 100MHz

I2C: ready

DRAM: Initializing DDR....using SPD

Detected UDIMM 18ASF1G72AZ-2G1A1

DP-DDR: Detected UDIMM 18ASF1G72AZ-2G1A1

19.5 GiB

DDR 15.5 GiB (DDR4, 64-bit, CL=13, ECC on)

DDR Controller Interleaving Mode: 256B

DDR Chip-Select Interleaving Mode: CS0+CS1

DP-DDR 4 GiB (DDR4, 32-bit, CL=11, ECC on)

DDR Chip-Select Interleaving Mode: CS0+CS1

Waking secondary cores to start from fff1b000

All (8) cores are up.

Using SERDES1 Protocol: 42 (0x2a)

Using SERDES2 Protocol: 65 (0x41)

Flash: 128 MiB

NAND: 2048 MiB

MMC: FSL_SDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

PCIe1: disabled

PCIe2: disabled

PCIe3: Root Complex x1 gen1, regs @ 0x3600000

01:00.0 - 8086:10d3 - Network controller

PCIe3: Bus 00 - 01

PCIe4: Root Complex no link, regs @ 0x3700000

In: serial

Out: serial

Err: serial

Error! Not a FIT image

SATA link 0 timeout.

AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst

Found 0 device(s).

SCSI: Net: crc32+

fsl-mc: Booting Management Complex ... SUCCESS

fsl-mc: Management Complex booted (version: 7.0.3, boot status: 0x1)

fsl-mc: Deploying data path layout ... SUCCESS

e1000: 68:05:ca:36:90:df

DPNI10, DPNI8

Error: DPNI8 address not set.

, DPNI1, DPNI2

Error: DPNI2 address not set.

, DPNI3

Error: DPNI3 address not set.

, DPNI4

Error: DPNI4 address not set.

, DPNI7, DPNI9

Error: DPNI9 address not set.

, e1000#0 [PRIME]

Warning: e1000#0 MAC addresses don't match:

Address in SROM is 68:05:ca:36:90:df

Address in environment is 68:05:ca:2e:24:ee

marius_grigoras · ‎09-30-2015

Hi,

You should set up the e1000 as "prime" interface using setenv or editenv in u-boot console. Also, make sure that ethact is e1000#0. My envs are:

=> printe

baudrate=115200

boot_linux=tftp a0000000 b36300/kernel-ls2085ardb.itb; bootm a0000000

bootargs=console=ttyS1,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0600,115200 ramdisk_size=9600000 default_hugepagesz=2m hugepagesz=2m hugepages=16

bootcmd=tftp a0000000 ls2085ardb/EAR4/kernel-ls2085ardb.itb;bootm a0000000

bootdelay=10

ear5=tftp a0000000 ear5.0/rdb/kernel-ls2085ardb.itb; bootm a0000000

eth1addr=68:05:ca:29:de:51

eth2addr=68:05:ca:29:de:51

eth6addr=68:05:ca:29:de:51

ethact=e1000#0

ethaddr=68:05:ca:2b:b2:2a

ethprime=e1000#0

fdt_high=0xa0000000

fileaddr=80000000

filesize=3631

hwconfig=fsl_ddr:bank_intlv=auto

initrd_high=0xffffffffffffffff

ipaddr=192.168.1.2

kernel_addr=0x100000

kernel_load=0xa0000000

kernel_size=0x2700000

kernel_start=0x581100000

linux=tftp a0000000 b36300/kernel-ls2085ardb.itb; bootm a0000000

loadaddr=0x80100000

mcboottimeout=100000

myaddr=0x580700000

netmask=255.255.255.0

ramdisk_addr=0x800000

ramdisk_size=0x9600000

run4=tftp a0000000 ls2085ardb/EAR4/kernel-ls2085ardb.itb;bootm a0000000

runc=tftp a0000000 LS2/kernel-ls2085ardb.itb; bootm a0000000

runk=tftp a0000000 ear4.0/kernel-ls2085ardb.itb; bootm a0000000

scsidevs=0

serverip=192.168.1.1

stderr=serial

stdin=serial

stdout=serial

write_aiop=setenv filesize; setenv myaddr 0x580900000; tftp 0x80000000 b36300/aiop_reflector.elf; protect off $myaddr +$filesize; erase $myaddr +$filesize; cp.b 0x80000000 $myaddr $filesize; protect on $myaddr +$filesize

write_dtb_aiop=setenv filesize; setenv myaddr 0x584700000; tftp 0x80000000 b36300/dpl_AIOP_dpni.6_to_dpmac.5.dtb; protect off $myaddr +$filesize; erase $myaddr +$filesize; cp.b 0x80000000 $myaddr $filesize; protect on $myaddr +$filesize

Environment size: 1765/8188 bytes

Regards,

Marius

ronakadesai · ‎09-30-2015

Thanks Marius for your quick response. But, in my environment, these variables are already set. Please refer below snippet. Also, I see that you are generating your own kernel binaries so would you please suggest which version of kernel you are compiling.

Environment size: 862/8188 bytes

=>

baudrate=115200

bootargs=console=ttyS1,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0600,115200 default_hugepagesz=2m hugepagesz=2m hugepages=16 ramdisk_size=0x2000000

bootcmd=cp.b $kernel_start $kernel_load $kernel_size && bootm $kernel_load

bootdelay=10

eth2addr=68:05:ca:12:6e:67

eth6addr=68:05:ca:12:6e:67

eth8addr=68:05:ca:2e:24:ee

ethact=e1000#0

ethaddr=68:05:ca:12:6e:67

ethprime=e1000#0

fdt_high=0xa0000000

fileaddr=a0000000

filesize=22fbb

gateway=10.10.0.1

hwconfig=fsl_ddr:bank_intlv=auto

initrd_high=0xffffffffffffffff

ipaddr=10.10.0.29

kernel_addr=0x100000

kernel_load=0xa0000000

kernel_size=0x3000000

kernel_start=0x581100000

loadaddr=0x80100000

mcboottimeout=100000

ramdisk_addr=0x800000

ramdisk_size=0x2000000

scsidevs=0

serverip=10.10.0.1

stderr=serial

stdin=serial

stdout=serial

Environment size: 862/8188 bytes

=> dhcp

e1000: e1000#0: ERROR: Valid Link not detected

BOOTP broadcast 1

BOOTP broadcast 2

yipingwang · ‎10-10-2015

Hello Ronak Desai,

Please configure different MAC address for "ethxaddr" than ethaddr, for example as the following, and try whether you could use DPNI Ethernet ports to connect to the Networking environment and ping the Server.

eth10addr=00:E0:0C:00:78:0a

eth11addr=00:E0:0C:00:78:0b

eth12addr=00:E0:0C:00:78:0c

eth13addr=00:E0:0C:00:78:0d

eth14addr=00:E0:0C:00:78:0e

eth15addr=00:E0:0C:00:78:0f

eth1addr=00:E0:0C:00:78:01

eth2addr=00:E0:0C:00:78:02

eth3addr=00:E0:0C:00:78:03

eth4addr=00:E0:0C:00:78:04

eth5addr=00:E0:0C:00:78:05

eth6addr=00:E0:0C:00:78:06

eth7addr=00:E0:0C:00:78:07

eth8addr=00:E0:0C:00:78:08

eth9addr=00:E0:0C:00:78:09

ethact=e1000#0

ethaddr=00:04:9F:01:0B:B3

ethprime=e1000#0

Thanks,

Yiping

marius_grigoras · ‎10-08-2015

I think you can first try the 1^st option below. If the issue is still there, try the 2^nd option below.

Power off and power on the board. Then run ‘dhcp’ command under u-boot to see whether the issue is still there.
Power off the board. Plug out and plug in the Intel e1000 NIC. Power on the board. Then run ‘dhcp’ command under u-boot to see whether the issue is still there.

Thank you,

Marius