New Build 06-30-2019-r40167 * DONT USE THIS BUILD *

Post new topic   Reply to topic    DD-WRT Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Goto page Previous  1, 2, 3
Author Message
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 5700

PostPosted: Fri Nov 01, 2019 11:58    Post subject: Reply with quote
It appears your setenv firmwareName command is not correct so it's looking at a different environment variable for the filename, failing to locate and write the new firmware. You can check for the correct envar with printenv command.

I'm guessing it's looking at firmware_name instead; "printenv" will give you a full list and "printenv firmware_name" for example will return a single result.

So you have a choice either to rename the firmware image on your TFTP server to the filename matching blk-mamba.128mb.img or you can verify the correct environment variable to modify.

I believe "setenv firmwareName" with nothing typed afterward will remove the entry from the list.
Sponsor
davedarr
DD-WRT Novice


Joined: 05 Jan 2016
Posts: 12

PostPosted: Sat Nov 02, 2019 1:46    Post subject: Reply with quote
blkt wrote:
It appears your setenv firmwareName command is not correct so it's looking at a different environment variable for the filename, failing to locate and write the new firmware. You can check for the correct envar with printenv command.

I'm guessing it's looking at firmware_name instead; "printenv" will give you a full list and "printenv firmware_name" for example will return a single result.

So you have a choice either to rename the firmware image on your TFTP server to the filename matching blk-mamba.128mb.img or you can verify the correct environment variable to modify.

I believe "setenv firmwareName" with nothing typed afterward will remove the entry from the list.


Thank you for your response and suggestion. I have changed the name of the .img file to match the name that it was looking for.




I re-ran the process again in hopes that this time I would not get the "ERROR: can't get kernel image!", but it did not work.
As you can see upon running the inquiry command to see what its named it shows correct.



I had even ran "setenv firmwareName" to clear it first.

The below is a print out of when I ran the suggested printevn

Marvell>> printenv firmware_name
firmware_name=blk-mamba.128mb.img
Marvell>> printenv
CASset=min
MALLOC_len=5
MPmode=smp
alt_kern_addr=0x3200000
alt_kern_size=0x400000
altnandboot=run linksys_altnandboot
amp_enable=no
auto_recovery=yes
autoload=no
badcount=0
baudrate=115200
boot_order=hd_scr hd_img pxe net_img net_scr
boot_part=1
boot_part_ready=3
bootargs=console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),25 6K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m @53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) root=/dev/mtdblock5 ro rootfstype= jffs2 init=/sbin/init
bootargs_dflt=$console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.l cd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:DSMP:eth0:none
bootargs_root=root=/dev/nfs rw
bootbadcount=0
bootcmd=run nandboot
bootcmd_auto=stage_boot $boot_order
bootcmd_bak=stage_boot $boot_order
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; boo tm 0x2000000;
bootdelay=3
buffbadcount=0
cacheShare=no
console=console=ttyS0,115200
default_load_addr=0x2000000
default_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@ 9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_root fs),80m@10m(ubifs),-@90m(syscfg)
device=1
device_partition=0:1
disL2Cache=yes
disL2Prefetch=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=no
enaCpuStream=no
enaDCPref=yes
enaFPU=yes
enaICPref=yes
enaLPAE=no
enaWrAllo=no
eth1addr=00:50:43:02:00:00
eth1mtu=1500
eth2addr=00:50:43:00:00:02
eth2mtu=1500
eth3addr=00:50:43:00:02:02
eth3mtu=1500
ethact=egiga0
ethaddr=94:10:3E:8A:9B:3F
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fileaddr=2000000
filesize=0x1e00000
firmware_name=blk-mamba.128mb.img
flash_alt_image=tftp $default_load_addr $firmware_name; nand erase $alt_kern_add r 0x4000000;nand write $default_load_addr $alt_kern_addr ${filesize};
flash_pri_image=tftp $default_load_addr $firmware_name; nand erase $pri_kern_add r 0x4000000;nand write $default_load_addr $pri_kern_addr ${filesize};
flash_ubi_image=mw.b 0x2000000 0x00 0x1e00000;tftp $default_load_addr blk-mamba. 128mb.ubi.img; nand erase $pri_kern_addr 0x3600000; nand write $default_load_add r $pri_kern_addr 0x3600000
fs=ext2
fs_bootargs=console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env) ,256K(s_env),256K(devinfo),4M(Linux),31M(rootfs),4M(Linux2),31M(rootfs2),-(syscf g)
fs_bootargs_root=ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs rootflags=sync
fs_type=jffs2
ide_path=/
image_name=uImage
initrd_name=uInitrd
interface=ide
ipaddr=192.168.1.1
jffs2_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m (devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs ),80m@10m(ubifs),-@90m(syscfg)
kernel_addr_r=2080000
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
linksys_altnandboot=nand read $default_load_addr $alt_kern_addr $alt_kern_size; setenv bootargs $console $default_mtdparts root=/dev/mtdblock7 ro rootfstype=$fs _type init=/sbin/init; bootm $default_load_addr;
linksys_nandboot=nand read $default_load_addr $pri_kern_addr $pri_kern_size; set env bootargs $console $default_mtdparts root=/dev/mtdblock5 ro rootfstype=$fs_ty pe init=/sbin/init; bootm $default_load_addr;
loadaddr=0x02000000
loads_echo=0
mfg_fs_bootargs=console=ttyS0,115200 mtdparts=armada-nand:640k(uboot)ro,128k@640 k(u_env),128k@768k(s_env),3m@1m(kernel),16m@4m(rootfs),1m@20m(syscfg),4m@21m(dat a),3m@25m(alt_kernel),16m@28m(alt_rootfs),20m@44m(downloads)
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devin fo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@ 10m(ubifs),-@90m(syscfg)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:00:00:02
nandEcc=1bit
nandboot=run linksys_nandboot
netbsd_en=no
netmask=255.255.255.0
netretry=no
nfsboot=tftpboot $default_load_addr $image_name; setenv bootargs $fs_bootargs $b ootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNe tConfig; bootm $default_load_addr
openwrt_altnandboot=nand read $default_load_addr $alt_kern_addr $openwrt_fw_size ; setenv bootargs $console $default_mtdparts root=/dev/mtdblock7 ro rootfstype=$ fs_type init=/sbin/init; bootm $default_load_addr;
openwrt_fw_size=0x4000000
openwrt_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@ 9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_root fs),80m@10m(ubifs),-@90m(syscfg)
openwrt_nandboot=nand read $default_load_addr $pri_kern_addr $openwrt_fw_size; s etenv bootargs $console $default_mtdparts root=/dev/mtdblock5 ro rootfstype=$fs_ type init=/sbin/init; bootm $default_load_addr;
pcieTune=no
pexMode=rc
prefix=/boot/
pri_kern_addr=0xa00000
pri_kern_size=0x400000
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rcvrip=169.254.100.100
rootpath=/home/work/AXP/fs/rootfs
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
senvbadcount=0
serverip=192.168.1.254
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $mtdparts root= /dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
ubiboot=nand read $default_load_addr $pri_kern_addr $pri_kern_size; setenv boota rgs $console $jffs2_mtdparts root=ubi0:rootfs rw ubi.mtd=8 rootfstype=ubifs init =/sbin/init; bootm $default_load_addr;
uenvbadcount=0
update_both_images=run flash_pri_image;run flash_alt_image
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 5973/262140 bytes
Marvell>>
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 5700

PostPosted: Sat Nov 02, 2019 11:40    Post subject: Reply with quote
Did you set your Ethernet LAN adapter's IPv4 back to manual IP settings? Maybe double check filename, paths and restart TFTP.

Also make sure any security software and/or software firewall are disabled.

Maybe rename the file to something simple like linksys.img and set the firmware_name envar to match.

Your printenv shows serverip is set to 192.168.1.254 so either use that IP or set it to match the IP you have manually set to your Ethernet adapter and TFTP.
Goto page Previous  1, 2, 3 Display posts from previous:    Page 3 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum