p2020rdb-pca u-boot console eTSEC problems

huyang · ‎07-10-2013

I flashed u-boot and vsc2bin on NOR using CW. and powered on the board.the boot information are as follows,it seemed to that the board couldn't check out the vsc2bin program .so i just can't flash my linux kernel and fs on the board through tftp. i wander that where should i flash the vsc2bin(the vsc2bin start flash address i specified is ff000000) ? or something wrong happened to the u-boot ?

U-Boot 2011.12-00025-gc6d9d50 (Mar 17 2013 - 11:09:26)

CPU0: P2020E, Version: 2.1, (0x80ea0021)

Core: E500, Version: 5.1, (0x80211051)

Clock Configuration:

CPU0:800 MHz, CPU1:800 MHz,

CCB:400 MHz,

DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:25 MHz

L1: D-cache 32 kB enabled

I-cache 32 kB enabled

Board: P2020RDB CPLD: V4.1 PCBA: V4.0

rom_loc: nor upper bank

SD/MMC : 4-bit Mode

eSPI : Enabled

I2C: ready

SPI: ready

DRAM: Detected UDIMM

1 GiB (DDR3, 64-bit, CL=6, ECC off)

Flash: 16 MiB

L2: 512 KB enabled

NAND: 32 MiB

MMC: FSL_SDHC: 0

*** Warning - bad CRC, using default environment

PCIe1: Root Complex of mini PCIe SLOT, no link, regs @ 0xffe0a000

PCIe1: Bus 00 - 00

PCIe2: Root Complex of PCIe SLOT, x1, regs @ 0xffe09000

02:00.0 - 1095:3132 - Mass storage controller

PCIe2: Bus 01 - 02

In: serial

Out: serial

Err: serial

Net: eTSEC2 is in sgmii mode.

No address specified for VSC7385 microcode.

PHY reset timed out

eTSEC1

Warning: failed to set MAC address

, eTSEC2

Warning: failed to set MAC address

, eTSEC3

Warning: failed to set MAC address

mingqiangyin · ‎02-24-2014

Hi Hu,

I have the same problem about my p2020rdb-pca board! Console shows the same msg with yours.

so i set the environment variable as below

Type the following commands to setup the U-Boot environment.

setenv ethaddr 00:04:9f:ef:01:01

setenv eth1addr 00:04:9f:ef:01:02

setenv eth2addr 00:04:9f:ef:01:03

setenv ipaddr 192.168.0.3

setenv netmask 255.255.255.0

setenv serverip 192.168.0.2

setenv gatewayip 192.168.0.1

saveenv

I also add environment variable vscfw_addr=ef000000. I also download the vsc2bin file and p2020rdb.dtb file by serial line.but i don't know what address these files should be put into flash. so could you tell me where you put them in flash?

i reset my board. etsec1,etsec2 and etsec3 can't still work。

Thanks in advance.

Regards.

Yin

huyang · ‎02-25-2014

Hi Yin,

vsc2bin should flash to ef000000 in uboot or ff000000 in codewarrior;

p2020rdb.dtb should flash to ef040000 in uboot.

Regards,

Hu

mingqiangyin · ‎02-25-2014

Hi Hu.

Thanks a lot . I set my board and flash these files as you said.my board can normally work.

all the eTSEC ports can work well.

Thanks for your patience!

Yin

mingqiangyin · ‎02-27-2014

Hi Hu

I have to ask you for help,I was in trouble. I have diffcult in booting vxworks with u-boot on my p2020rdb board.

I use the below command to download the vxworks.st image.

tftp 1000000 vxWorks.st

the follow command to boot:

bootvx 1000000

the console windown prints the msg:

U-Boot 2011.12-00025-gc6d9d50 (Oct 24 2012 - 11:00:29)

CPU0: P2020E, Version: 2.1, (0x80ea0021)

Core: E500, Version: 5.1, (0x80211051)

Clock Configuration:

CPU0:1200 MHz, CPU1:1200 MHz,

CCB:600 MHz,

DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:37.500 MHz

L1: D-cache 32 kB enabled

I-cache 32 kB enabled

Board: P2020RDB CPLD: V4.1 PCBA: V4.0

rom_loc: nor upper bank

SD/MMC : 4-bit Mode

eSPI : Enabled

I2C: ready

SPI: ready

DRAM: Detected UDIMM

1 GiB (DDR3, 64-bit, CL=6, ECC off)

Flash: 16 MiB

L2: 512 KB enabled

NAND: 32 MiB

MMC: FSL_SDHC: 0

PCIe1: Root Complex of mini PCIe SLOT, no link, regs @ 0xffe0a000

PCIe1: Bus 00 - 00

PCIe2: Root Complex of PCIe SLOT, x1, regs @ 0xffe09000

02:00.0 - 1095:3132 - Mass storage controller

PCIe2: Bus 01 - 02

In: serial

Out: serial

Err: serial

Net: eTSEC2 is in sgmii mode.

uploading VSC7385 microcode from ef000000

PHY reset timed out

eTSEC1, eTSEC2, eTSEC3

Hit any key to stop autoboot: 0

=>

=> tftp 1000000 vxWorks.st

Speed: 1000, full duplex

Using eTSEC1 device

TFTP from server 192.168.0.2; our IP address is 192.168.0.3

Filename 'vxWorks.st'.

Load address: 0x1000000

Loading: #################################################################

#####################################

done

Bytes transferred = 1487448 (16b258 hex)

=> bootvx 1000000

## Ethernet MAC address not copied to NV RAM

## Using bootline (@ 0x4200): eth(0,0)srv:uImage e=192.168.0.3 h=192.168.0.2 tn=

unknown

## Starting vxWorks at 0x00100000 ...

my board hangs in here. Why does this happen? I need your help! could you talk about booting vxworks with u-boot.

Looking forward to your comments.

Regards

Yin.

huyang · ‎02-27-2014

Hi Yin,

I'm not familiar with the vxwork on P2020RDB, we just use files in SDK1.4 to boot system.

Sorry for not helping.

Regards,

Hu

mingqiangyin · ‎02-27-2014

Hi Hu.

Thank you all the same!:smileyhappy:

Yin

yipingwang · ‎02-24-2014

You could find the flash memory map from SDK document, please refer to the following NOR Flash memory map of P2020RDB-PC.

mingqiangyin · ‎02-25-2014

Hi Wang

Thanks.I don't find this sheet in my document.I will save this picture of memory map you upload.

Yin

marius_grigoras · ‎07-10-2013

Hi Hu,

I observed you switch the discussion on this thread. Thanks for u-boot log, it really helps.

Taking a look in the u-boot code from SDK 1.4 for this board I observed:

#ifdef CONFIG_VSC7385_ENET

/* If a VSC7385 microcode image is present, then upload it. */

if ((tmp = getenv("vscfw_addr")) != NULL) {

vscfw_addr = simple_strtoul(tmp, NULL, 16);

printf("uploading VSC7385 microcode from %x\n", vscfw_addr);

if (vsc7385_upload_firmware((void *) vscfw_addr,

CONFIG_VSC7385_IMAGE_SIZE))

puts("Failure uploading VSC7385 microcode.\n");

} else

puts("No address specified for VSC7385 microcode.\n");

#endif

And according with your log, you got the "else" part -> No address specified for VSC7385 microcode.

Now, from code perspective, you're able to put the vsc2bin anywhere you want (please take care to not override something important like u-boot), but is mandatory to configure after the vscfw_addr variable in u-boot console.

Regards,

Marius

huyang · ‎07-11-2013

HI,

Thank you very much.

That problem is solved by adding environment variable vscfw_addr=ef000000, now we can login to the linux on RDB board.

But we reading the print msg and found another problem, it seems that our NAND Flash didn't found, relative booting msg showed below:

Creating 5 MTD partitions on "ef000000.nor":

0x000000000000-0x000000040000 : "NOR (RO) Vitesse-7385 Firmware"

ftl_cs: FTL header not found.

0x000000040000-0x000000080000 : "NOR (RO) DTB Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000400000 : "NOR (RO) Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000400000-0x000000f00000 : "NOR (RW) JFFS2 Root File System"

ftl_cs: FTL header not found.

0x000000f00000-0x000001000000 : "NOR (RO) U-Boot Image"

ftl_cs: FTL header not found.

fsl-lbc ffe05000.localbus: address did not match any chip selects

fsl-espi ffe07000.spi: Freescale eSPI Controller driver at 0xf110e000 (irq = 59)

fsl_m25p80 spi32766.0: s25sl128b (16384 Kbytes)

Creating 5 MTD partitions on "SPIFLASH0":

0x000000000000-0x000000080000 : "SPI (RO) U-Boot Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000100000 : "SPI (RO) DTB Image"

ftl_cs: FTL header not found.

0x000000100000-0x000000500000 : "SPI (RO) Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000500000-0x000000900000 : "SPI (RO) Compressed RFS Image"

ftl_cs: FTL header not found.

0x000000900000-0x000001000000 : "SPI (RW) JFFS2 RFS"

ftl_cs: FTL header not found.

Fixed MDIO Bus: probed

There is no MTD partition of NAND.

and booting msg below is what suppose to be:

reating 5 MTD partitions on "ef000000.nor":

0x000000000000-0x000000040000 : "NOR (RO) Vitesse-7385 Firmware"

ftl_cs: FTL header not found.

0x000000040000-0x000000080000 : "NOR (RO) DTB Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000400000 : "NOR (RO) Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000400000-0x000000f00000 : "NOR (RW) JFFS2 Root File System"

ftl_cs: FTL header not found.

0x000000f00000-0x000001000000 : "NOR (RO) U-Boot Image"

ftl_cs: FTL header not found.

NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bi)

RedBoot partition parsing not available

Creating 6 MTD partitions on "ff800000.flash":

0x000000000000-0x000000100000 : "NAND (RO) U-Boot Image"

ftl_cs: FTL header not found.

0x000000100000-0x000000200000 : "NAND (RO) DTB Image"

ftl_cs: FTL header not found.

0x000000200000-0x000000600000 : "NAND (RO) Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000600000-0x000000a00000 : "NAND (RO) Compressed RFS Image"

ftl_cs: FTL header not found.

0x000000a00000-0x000001900000 : "NAND (RW) JFFS2 Root File System"

ftl_cs: FTL header not found.

0x000001900000-0x000002000000 : "NAND (RW) Writable User area"

ftl_cs: FTL header not found.

eLBC NAND device at 0xff800000, bank 1

fsl-espi ffe07000.spi: Freescale eSPI Controller driver at 0xf1116000 (irq = 59)

fsl_m25p80 spi32766.0: s25sl128b (16384 Kbytes)

Creating 5 MTD partitions on "SPIFLASH0":

0x000000000000-0x000000080000 : "SPI (RO) U-Boot Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000100000 : "SPI (RO) DTB Image"

ftl_cs: FTL header not found.

0x000000100000-0x000000500000 : "SPI (RO) Linux Kernel Image"

ftl_cs: FTL header not found.

How this happened? Is our dtb file not correct?

Thanks for your help, your advice really helps~

Regrads,

Hu

0x000000500000-0x000000900000 : "SPI (RO) Compressed RFS Image"

ftl_cs: FTL header not found.

0x000000900000-0x000001000000 : "SPI (RW) JFFS2 RFS"

ftl_cs: FTL header not found.

Fixed MDIO Bus: probed

marius_grigoras · ‎07-11-2013

Hi,

If your board is not a custom one, maybe is just a problem at NAND detection. Please make a try with flash programmer from CodeWarrior and let me know if the NAND works in this case.

Regards,

Marius

huyang · ‎07-12-2013

Hi,

We got another P2020RDB.dtb and reflash into NOR Flash, and problem solved.

Thank you. ^_^

Regards,

Hu

p2020rdb-pca u-boot console eTSEC problems

p2020rdb-pca u-boot console eTSEC problems

QorIQ P2 Devices