Hi All,
I wanted to change initial u boot arguments/variables to enable Ethernet connection, but once I change them and save them, my board doesn't boot up any more. Here is the log:
I'm kinda new in these things, so if some of you guys with more experience could have a look and give me some clues.
I have changed:
ethprime
netmask
gatewayip
ipaddr
Thanks,
Vojislav
U-Boot 2014.07QorIQ-SDK-V1.7+g659b6a2 (Jan 02 2015 - 11:30:53)
CPU0: T2080E, Version: 1.1, (0x85380011)
Core: e6500, Version: 2.0, (0x80400120)
Clock Configuration:
CPU0:1799.820 MHz, CPU1:1799.820 MHz, CPU2:1799.820 MHz, CPU3:1799.820 M
CCB:666.600 MHz,
DDR:799.980 MHz (1599.960 MT/s data rate) (Asynchronous), IFC:166.650 MHz
FMAN1: 699.930 MHz
QMAN: 333.300 MHz
PME: 666.600 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 1406001b 15000000 00000000 00000000
00000010: 66150002 00000000 ec027000 c1000000
00000020: 00800000 00000000 00000000 000307fc
00000030: 00000000 00000000 00000000 00000004
Board: T2080RDB, Board rev: 0x01 CPLD ver: 0x03, boot from NOR vBank0
SERDES Reference Clocks:
SD1_CLK1=156.25MHZ, SD1_CLK2=100.00MHZ
SD2_CLK1=100.00MHZ, SD2_CLK2=100.00MHZ
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM 18KSF51272HZ-1G6K2
4 GiB (DDR3, 64-bit, CL=11, ECC on)
DDR Chip-Select Interleaving Mode: CS0+CS1
Flash: 128 MiB
L2: 2 MiB enabled
Corenet Platform Cache: 512 KiB enabled
Using SERDES1 Protocol: 102 (0x66)
Using SERDES2 Protocol: 21 (0x15)
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
PCIe1: Endpoint, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, x2 gen2, regs @ 0xfe250000
02:00.0 - 1957:0808 - Processor
PCIe2: Bus 01 - 02
PCIe3: disabled
PCIe4: Root Complex, no link, regs @ 0xfe270000
PCIe4: Bus 03 - 03
In: serial
Out: serial
Err: serial
Net: Fman1: Uploading microcode version 106.4.14
PHY reset timed out
PHY reset timed out
FM1@DTSEC3, FM1@DTSEC4, FM1@TGEC1, FM1@TGEC2, FM1@TGEC3, FM1@TGEC4
Hit any key to stop autoboot: 0
WARNING: adjusting available memory to 30000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=> printenv
baudrate=115200
bdev=sda3
bootargs=root=/dev/ram rw console=ttyS0,115200
bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootr
bootdelay=10
bootfile=uImage
consoledev=ttyS0
eth1addr=00:04:9F:03:49:B3
eth2addr=00:04:9F:03:49:AE
eth3addr=00:04:9F:03:49:AF
eth4addr=00:04:9F:03:49:B0
eth5addr=00:04:9F:03:49:B1
ethact=FM1@DTSEC3
ethaddr=00:04:9F:03:49:B2
ethprime=fm1-mac3
fdtaddr=0x00c00000
fdtfile=t2080rdb/t2080rdb.dtb
fman_ucode=eff00000
gatewayip=10.10.0.1
hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=auto;usb1:dr_mode=host,phy_typi
ipaddr=10.10.1.110
loadaddr=0x1000000
netdev=eth0
netmask=255.255.254.0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddrr
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootr
ramdiskaddr=0x02000000
ramdiskfile=t2080rdb/ramdisk.uboot
rootpath=/opt/nfsroot
stderr=serial
stdin=serial
stdout=serial
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erae
uboot="u-boot.bin"
ubootaddr=0xeff40000
Environment size: 1669/8188 bytes
Hi Vojislav,
I assumed you are try to boot Linux with ramdisk filesystem based on the environmental variable "root=/dev/ram"
If you wants to boot Linux with ramdisk filesystem change the bootarg and bootcmd as follows
=> setenv bootargs "'root=/dev/ram rw console=ttyS0,115200 ramdisk_size=<size of ramdisk>'"
=> setenv bootcmd "'bootm <starting address of Kernel> <starting address of ramdisk> <starting address of device tree>'"
Example:
Assume kernel image is in 0xE8020000, ramdisk rootfs is in 0xED300000 and Hardware device tree is in 0xE8800000 location then set the following environmental variable.
=> setenv bootcmd "'bootm 0xE8020000 0xED300000 0xE8800000'"
Regards
Karuanakaran R
u-Boot says your kernel image is broken, but it is not possible
to tell what exactly is wrong because your terminal truncated long lines
of the output of printenv command. Please configure your terminal to
wrap long lines, execute printenv and re-submit the output.