no ip address, unable to access the NAS

[fvdw]

same as booting with no disks?

Yes exactly.
however I discovered that via serial cable I can interrupt the boot with ctrl-c

Do you get then a prompt lije this

Code: Select all

marvell>>

[danilomag]

marvell>>

yes

Do you get this directly after waiting for uboot so with the nas switched off, or does this start after starting the nas??
It is very strange output, never seen this before

after starting the nas, immediately after Waiting for LUMP (3)

[fvdw]

marvell>>

yes

That is good news that means we can use the uboot commands.
But lets first see uboot environment at the marvell prompt give command

Code: Select all

printenv

Do you get this directly after waiting for uboot so with the nas switched off, or does this start after starting the nas??
It is very strange output, never seen this before

after starting the nas, immediately after Waiting for LUMP (3)

Then there is something in your lan is broadcasting this info and its why fvdw-sl console cannot connect

[danilomag]

Code: Select all

Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
console=console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0(uboot)ro,0xff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
gatewayip=192.168.1.1
netmask=255.255.255.0
ipaddr=192.168.1.185
serverip=192.168.1.185
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
bootdelay=0
boot_fail=lump
kernel_addr=0x800000
productType_env=BIG5_KW
primaryPart=6
secondaryPart=A
boot_usb=usb start;usbboot 0x800000 0:1;bootm;
resetFlag_env=0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=PRO_KW
bootcmd=run disk_disk
mtdids=nand0=nand_mtd
mtdparts=mtdparts=nand_mtd:1m(u-boot),16m(uImage),-(root)
boot_nand=setenv bootargs console=ttyS0,115200 ${mtdparts} root=/dev/mtdblock2 ro reset=${resetFlag_env} productType=${productType_env}; nboot ${kernel_addr} uImage; bootm ${kernel_addr}
boot_disk10=if disk ${kernel_addr} 5:${primaryPart}; then setenv rootfs /dev/sde7; else run boot_nand; fi
boot_disk9=if disk ${kernel_addr} 6:${primaryPart}; then setenv rootfs /dev/sdd7; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 1:${primaryPart}; then setenv rootfs /dev/sdc7; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 2:${primaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 3:${primaryPart}; then setenv rootfs /dev/sda7; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 5:${secondaryPart}; then setenv rootfs /dev/sde7; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 6:${secondaryPart}; then setenv rootfs /dev/sdd7; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sdc7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 2:${secondaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 3:${secondaryPart}; then setenv rootfs /dev/sda7; else run boot_disk2; fi
boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_disk6; fi
disk_disk=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro reset=${resetFlag_env} productType=${productType_env}; bootm ${kernel_addr};
ethaddr=00:D0:4B:92:5C:A5
eth1addr=00:D0:4B:92:5C:A6
ethact=egiga0


[fvdw]

Oke, what is the ip address of your pc?

[danilomag]

192.168.1.185

[fvdw]

Oke start fvdw-sl console and choose action start tftp server.
When tftp server is running type in your serialbconsole at marvell prompt

Code: Select all

ide reset
tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-171-standalone

And see if the kernel is uploaded
To start it type

Code: Select all

bootm

[danilomag]

Code: Select all

Marvell>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Port Multiplier found @ 0 0. Vendor: 11ab ports: 4
[0 0 3]: Enable DMA mode
  Device 3 @ 0 0 3:
Model: WDC WD2003FZEX-00Z4SA0                   Firm: 01.01A01 Ser#:      WD-WMC5C0D5JEHR
            Type: Hard Disk
dev_desc->blksz = 512
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
Port Multiplier found @ 0 1. Vendor: 11ab ports: 4

Marvell>> tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-171-standalone
Using egiga0 device
TFTP from server 192.168.1.185; our IP address is 192.168.1.185
Filename 'UIMAGE-3142-KIRKWOOD-171-standalone'.
Load address: 0x800000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Marvell>>


[fvdw]

Seems ip adress that the nas has assigned to itself is 192.168.1.185 as well.So same as your pc.vthat won't work.
Need to see how to set ip address of the nas in uboot, one moment

[fvdw]

try this to get an ip

Code: Select all

setenv autoload no; dhcp;

and wait if it gets an ip