How to setup the ethernet interface inorder to connect to tftp server

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to setup the ethernet interface inorder to connect to tftp server

770 Views
naveedasmat
Contributor I

Hi,

I am trying to bootup the p2041rdb but unfortunately got stuck within the uboot and assigning the IP address. I haven't been able to assign the IP address so that i may be able to connect to the tftp server to upload the new kernel image on the flash.

I followed the steps provided in the QorIQ SDK 2.0 Documentation for p2041rdb.

The uboot log:

U-Boot 2015.01+SDKv1.9+geb3d4fc (May 06 2016 - 10:56:30)

CPU0:  P2041E, Version: 1.0, (0x82180110)

Core:  e500mc, Version: 2.2, (0x80230022)

Clock Configuration:

       CPU0:1500 MHz, CPU1:1500 MHz, CPU2:1500 MHz, CPU3:1500 MHz,

       CCB:750  MHz,

       DDR:666.667 MHz (1333.333 MT/s data rate) (Asynchronous), LBC:93.750 MHz

       FMAN1: 583.333 MHz

       QMAN:  375 MHz

       PME:   375 MHz

L1:    D-cache 32 KiB enabled

       I-cache 32 KiB enabled

Reset Configuration Word (RCW):

       00000000: 12600000 00000000 241c0000 00000000

       00000010: 249f40c0 c3c02000 fe800000 40000000

       00000020: 00000000 00000000 00000000 d0030f07

       00000030: 00000000 00000000 00000000 00000000

Board: P2041RDB, CPLD version: 3.0 vBank: 0

SERDES Reference Clocks: Bank1=100Mhz Bank2=125Mhz

I2C:   ready

SPI:   ready

DRAM:  Initializing....using SPD

Detected UDIMM UG51U6400N8SU-ACF

2 GiB left unmapped

Testing 0x00000000 - 0x7fffffff

Testing 0x80000000 - 0xffffffff

Remap DDR 2 GiB left unmapped

4 GiB (DDR3, 64-bit, CL=9, ECC off)

       DDR Chip-Select Interleaving Mode: CS0+CS1

POST memory PASSED

Flash: 128 MiB

L2:    128 KiB enabled

Corenet Platform Cache: 1 MiB enabled

SERDES: bank 3 disabled

SRIO1: disabled

SRIO2: disabled

NAND:  0 MiB

MMC:   FSL_SDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

PCIe1: disabled

PCIe2: Root Complex, no link, regs @ 0xfe201000

PCIe2: Bus 00 - 00

PCIe3: disabled

In:    serial

Out:   serial

Err:   serial

Net:   Initializing Fman

Fman1: DTSEC3 set to unknown interface 13

Fman1: Data at eff00000 is not a firmware

No ethernet found.

Hit any key to stop autoboot:

-----------------------------------------------------------------------------------

Printenv log is as follows:

baudrate=115200

bdev=sda3

bootargs=root=/dev/sda3 rw console=ttyS0,115200

bootcmd=setenv bootargs root=/dev/$bdev rw console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr

bootdelay=10

bootfile=uImage

consoledev=ttyS0

eth1addr=00:04:9F:02:01:FD

eth2addr=00:04:9F:02:02:FD

eth3addr=00:04:9F:02:03:FD

eth4addr=00:04:9F:02:04:FD

eth5addr=00:04:9F:02:05:FD

ethact=FM1@DTSEC5

ethaddr=00:04:9F:02:00:FD

ethprime=FM1@DTSEC5

fdtaddr=c00000

fdtfile=p2041rdb/p2041rdb.dtb

gatewayip=192.168.1.1

hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1;fsl_fm1_xaui_phy:xfi

ipaddr=192.168.1.100

loadaddr=1000000

netdev=eth0

netmask=255.255.0.0

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

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=2000000

ramdiskfile=p2041rdb/ramdisk.uboot

rootpath=/opt/nfsroot

serverip=192.168.1.34

severip=192.168.1.35

stderr=serial

stdin=serial

stdout=serial

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

usb_dr_mode=host

usb_phy_type=utmi

---------------------------------------------

=> mii device

MII devices: 'FSL_MDIO0' 'FM_TGEC_MDIO'

Current device: 'FSL_MDIO0'

==================================================

Main question is how to setup the ethernet interface inorder to connect to tftp server to upload the image?

I will be really grateful for any advice.

Best Regards

Naveed

Labels (1)
0 Kudos
2 Replies

510 Views
bpe
NXP Employee
NXP Employee

You are trying to boot an SDK 1.9 u-Boot on an unsupported chip revision.

Suggestions:

1. Check the document at the link below. Use an SDK version that supports your device or upgrade your hardware:

    https://freescale.sdlproducts.com/LiveContent/content/en-US/QorIQ_SDK/GUID-21A68B1F-4CD4-4959-9175-4...

2. Program a valid FMan microcode binary at the specified Flash memory address. Your chip network subsystem cannot work without it.

3. Undo any changes to the SDK original u-Boot configuration/source.

Have a great day,
Platon

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

510 Views
naveedasmat
Contributor I

Hi,

Many thanks for the reply.

Now i am trying to build yocto SDK 1.3 for P2041rdb-PA. I am getting error related to a m4 package:

"package m4-native-1.4.16-r2: task do_compile: Failed"

The sequence of commands :

. ./fsl-setup-poky -m p2041rdb

bitbake fsl-image-minimal

It first complains about the sanity.conf; which i found a workaround with:

touch conf/sanity.conf

But later after reruning the "bitbake fsl-image-minimal" ; it complains about
"package m4-native-1.4.16-r2: task do_compile: Failed"

The tail of the log is as follows:============================================================================

make  all-am
| make[3]: Entering directory `/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/work/x86_64-linux/m4-native-1.4.16-r2/m4-1.4.16/lib'
| \
| #    source='gl_avltree_oset.c' object='gl_avltree_oset.o' libtool=no
| \
| #    source='c-ctype.c' object='c-ctype.o' libtool=no
| gcc -std=gnu99  -I. -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c gl_avltree_oset.c
| gcc -std=gnu99  -I. -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c c-ctype.c
| \
| #    source='c-stack.c' object='c-stack.o' libtool=no
| gcc -std=gnu99  -I. -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c c-stack.c
| \
| #    source='clean-temp.c' object='clean-temp.o' libtool=no
| gcc -std=gnu99  -I.   -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_rERROR: Function failed: do_compile (see /home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/work/x86_64-linux/m4-native-1.4.16-r2/temp/log.do_compile.12254 for further information)
| elease/tmp/sysroots/x86_64-linux/usr/include -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c clean-temp.c
| In file included from clean-temp.h:22:0,
| from clean-temp.c:23:
| ./stdio.h:477:1: error: 'gets' undeclared here (not in a function)
|  _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
|  ^
| \
| #    source='close-hook.c' object='close-hook.o' libtool=no
| gcc -std=gnu99  -I.   -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -isystem/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -c close-hook.c
| make[3]: *** [clean-temp.o] Error 1
| make[3]: *** Waiting for unfinished jobs....
| make[3]: Leaving directory `/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/work/x86_64-linux/m4-native-1.4.16-r2/m4-1.4.16/lib'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/work/x86_64-linux/m4-native-1.4.16-r2/m4-1.4.16/lib'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/admin/QorIQ-SDK-V1.3-20121114-yocto/build_p2041rdb_release/tmp/work/x86_64-linux/m4-native-1.4.16-r2/m4-1.4.16'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
NOTE: package m4-native-1.4.16-r2: task do_compile: Failed
ERROR: Task 62 (/home/admin/QorIQ-SDK-V1.3-20121114-yocto/meta/recipes-devtools/m4/m4-native_1.4.16.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 37 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/admin/QorIQ-SDK-V1.3-20121114-yocto/meta/recipes-devtools/m4/m4-native_1.4.16.bb, do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

============================================================================

I couldn't find any substantial help on the internet. I tried to install lots of tools to resolve the dependancies but that didn't work.

I will be very grateful for any help/suggestion.

Many thanks

Naveed

0 Kudos