Then it stops, no further output from putty, it does not reach the point where it should say press any key to stop boot.
I had posted this on the end of another thread but thought i should make a fresh thread about the problem. It seems that i am not the only one that has experienced this but i have been unable to find any further information about the problem.
Any help would be really appreciated.
I have managed to get this to a command prompt now, Venom>>
i have downloaded the image from Linksys website its quite small 10,490 KB
I've started the TFTPD server pointed to the firmware etc,
then in the putty window i executed the commands
Venom>> setenv ipaddr 192.168.1.1
Venom>> setenv netmask 255.255.255.0
Venom>> setenv serverip 192.168.1.254
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'venom.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Any ideas?
i have also tried what was suggested on a youtube guide
setenv firewareName venom.img
also changing firmware_name as was suggested
also setenv firmware_name firmware_venom.img
but still get the retry count exceeded
its like the tftp server is not pushing it
What you're doing looks OK but evidently there's something being missed (or different)...
I just wanted to give you a possible way to at least get back to Linksys Firmware...
Have you tried to contact "CHADSTER" in the Linksys Community forum about this? He has some tools for other routers that will restore the bootloader,etc. I'm not sure if he's got anything for the 32x but just wanted to pass this along if you get stuck and a possible source to at least get it back to working status with Linksys firmware... _________________ WRT1900ACSv2
Thanks for your reply's i had read the above but missed the firmware thanks i will keep at it,
will the Serial Flashable Flat Venom Image flash via TFTP server? or do i need to get it in to the wrt32x /tmp folder and then follow that thread?
thanks again
Board: RD-NAS-88F6820-DDR3
SoC: MV88F6820 Rev A0
running 2 CPUs
CPU: ARM Cortex A9 MPCore (Rev 1) LE
CPU 0
CPU @ 1866 [MHz]
L2 @ 933 [MHz]
TClock @ 200 [MHz]
DDR3 @ 933 [MHz]
DDR3 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM: 512 MiB
NAND: 256 MiB
MMC: mv_sdh: 0
Venom>> setenv ipaddr 192.168.1.1
Venom>> setenv netmask 255.255.255.0
Venom>> setenv serverip 192.168.1.254
Venom>> setenv bootdelay 5
Venom>> setenv firmwareName venom.img
Venom>> save
Saving Environment to NAND...
Erasing Nand...
Writing to Nand... done
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'venom.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'venom.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Venom>> env print
CASset=max
MALLOC_len=5
MPmode=SMP
SMT-2D=NK90H500215CX01
altFwSize=0x7B00000
altKernAddr=0x8400000
altKernSize=0x0600000
altnandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock8;nand read $ defaultLoadAddr $altKernAddr $altKernSize; bootz $defaultLoadAddr
auto_recovery=yes
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
boot_part=1
boot_part_ready=3
bootargs_dflt=$console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serverip: $rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0 _params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=run nandboot
bootcmd_auto=stage_boot $boot_order
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv boo targs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip= $ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd. lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandE cc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$boo targs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_ena ble clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $ bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name;setenv bootargs $console $nandEcc $m tdparts_lgcy $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$boo targs_end video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd _panel=$lcd_panel; bootm $loadaddr;
bootdelay=5
cacheShare=no
console=console=ttyS0,115200
defaultLoadAddr=0x2000000
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=60:38:E0:CC:26:C8
eth1mtu=1500
eth2addr=60:38:E0:CC:26:C8
eth2mtu=1500
eth3addr=60:38:E0:CC:26:C8
eth3mtu=1500
ethact=egiga0
ethaddr=60:38:E0:CC:26:C8
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fileaddr=2000000
filesize=C20000
firmwareName=venom.img
flash_alt_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $altKernAd dr $altFwSize && nand write $defaultLoadAddr $altKernAddr $filesize
flash_pri_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAd dr $priFwSize && nand write $defaultLoadAddr $priKernAddr $filesize
ide_path=/
image_name=uImage
initrd_name=uInitrd
ipaddr=192.168.1.1
kernel_addr_r=2080000
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
limit_dram_size=yes
loadaddr=0x02000000
loads_echo=0
mtddevname=uboot
mtddevnum=0
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2048K(uboot)ro,128K(u_env),256K(s_env),256K@8064K( devinfo),123m@9m(firmware1),123m@132m(firmware2)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:db:f5:00
nandEcc=nfcConfig=4bitecc
nandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock6;nand read $def aultLoadAddr $priKernAddr $priKernSize; bootz $defaultLoadAddr
netbsd_en=no
netmask=255.255.255.0
netretry=no
partition=nand0,0
pcieTune=no
pexMode=RC
priFwSize=0x7B00000
priKernAddr=0x0900000
priKernSize=0x0600000
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rootpath=/srv/nfs/
run_script=no
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
sd_detection_dat3=no
serverip=192.168.1.254
silent=1
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdpa rts_lgcy root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x20000 00;
stderr=serial
stdin=serial
stdout=serial
update_both_images=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKer nAddr $priFwSize && nand erase $altKernAddr $altFwSize && nand write $defaultLoa dAddr $priKernAddr $filesize && nand write $defaultLoadAddr $altKernAddr $filesi ze
usb0Mode=host
usbActive=0
usbType=2
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
Environment size: 4429/131068 bytes
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'venom.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Venom>>
The Loading T's indicate retries, so U-Boot is having trouble accessing your TFTP server. You are at command prompt so I assume PuTTY's serial settings are correctly configured. Double check your network adapter's TCP/IP settings are properly set then check your TFTP is set in Server mode, bound to the same IP address and pointing to the correct directory containing the image.
Are you sure both partitions will not boot? I notice your silent variable is still set, so you are not seeing what is going on during the boot process.
Good news and bad...
Managed to get it to flash, the only thing i did differently (that may help others) was stopped windows firewall and when setting static ip in windows network connections i only set ip address and subnet mask didn't set the gateway address, one or the other maybe both fixed the TFTP server pushing firmware,
but sadly still not booting into stock, it gets further well, i now get to the press any key to stop boot which i didn't before,
output below:
General initialization - Version: 1.0.0
AVS selection from EFUSE disabled (Skip reading EFUSE values)
mvSysEnvIsFlavourReduced: TWSI Read of 'flavor' failed
Detected Device ID 6820
High speed PHY - Version: 2.0
Init RD NAS topology Serdes Lane 3 is USB3
Serdes Lane 4 is SGMII
board SerDes lanes topology details:
| Lane # | Speed| Type |
------------------------------|
| 0 | 6 | SATA0 |
| 1 | 5 | PCIe0 |
| 2 | 6 | SATA1 |
| 3 | 5 | USB3 HOST1 |
| 4 | 5 | PCIe1 |
| 5 | 0 | SGMII2 |
-------------------------------
:** Link is Gen1, check the EP capability
PCIe, Idx 0: Link upgraded to Gen2 based on client cpabilities
:** Link is Gen1, check the EP capability
PCIe, Idx 1: remains Gen1
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.46.0
mvSysEnvGetTopologyUpdateInfo: TWSI Read failed
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully
Not detected suspend to RAM indication
BootROM: Image checksum verification PASSED
mine says kernel1 & kernel2
but i see sufgi23 says linux and linux2
could this be causing a problem?
If i am correct could i try flashing dd-wrt from serial? if so which image the webflash gui .bin or the original FW_WRT32X_1.0.666_DDWRT.img
Yes the firewall was the problem. Your Ethernet adapter's TCP/IPv4 properties for TFTP: IP address is 192.168.1.254, Subnet is 255.255.255.0 and Gateway is 192.168.1.1 aka your router. Set DNS to use the following addresses and leave them blank to completely disable DHCP.
Can you access the web interface from Ethernet (after setting your properties back to obtain automatically)? If you can't, try a hard reset (with the router powered ON hold the reset button for at least 10 seconds).
The official Linksys FAQ says hold for a full 10 seconds, DD-WRT's Installation Sticky says 20 seconds and Linksys "experts" on their community forums say 30 seconds.
(i realised after i posted my last post about the MTD partition on mine were correct if i am on venom firmware, but was to late to edit the post).
i though it was the other way around to be honest but i have read that much about this wrt32x now lol
sadly no luck with a reset
pining 192.168.1.1 timed out
flashing power light still on router
tried power cycle x3 to switch partition
You may want to download venom.img again and compare the two with HashMyFiles from NirSoft (or equivalent free Windows utility) just to make sure you didn't get a corrupt download.
At this point I would try to reset the U-Boot bootloader environment variables and then reflash.
env default -a
saveenv
reset
After this, if you want to check the defaults you can use printenv and it will provide a full list. You can also do individual checks, for example printenv ipaddr, as the three ip settings might already be set. The same goes for firmwareName, I think it's already venom.img but you can check.
EDIT: Provide me a printenv list after the envar reset (above 3 commands) but before you setenv or flash!
Here's an example for flash. I threw in bootdelay because you did, and setenv silent removes the value allowing you to see what's going on.
Hi thank you so much for your help, where can i download the flat image from?
i originally downloaded it from a thread on dd-wrt here https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1136312#1136312 but no checksum
i have tried downloading the image with ie where as before i used chrome but still the same,
to save having long posts ive uploaded the txt doc to tinyupload- new output with some more printenv commands as well as your requested output
I've formatted all three of your environment lists (fixed the line breaks), compared them and referenced them with as many listings from stock WRT32X I can find online (not conversions). I can't find anything out of the ordinary.
I noticed this time it got farther along in the boot process? What's your current situation, still no SSH or Web GUI? I see a lot of exception stack and detected stalls on CPU in that log.
I forgot to ask if you received the router in this condition; what's the story behind this router?
The inteliboy image is identical to venom.img you downloaded from spuriousoffspring (guess who he got it from). It's also identical to the rango.img from the same thread (zippyshare).
