wrt32x bricked!!

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


Joined: 20 Jan 2019
Posts: 3910

PostPosted: Mon Jan 17, 2022 0:02    Post subject: Reply with quote
@Gameman Advanced Kid https://youtu.be/PZYXKAkuJ5w?t=525

@chirkoot1 Try connecting ground after power but do tell about this adapter/chip.

Try printenv. See if you can save or log the output. Then try disabling silent boot.

setenv silent
saveenv
reset

The reset command will reboot, be prepared to interrupt autoboot process again.
Sponsor
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 0:10    Post subject: Reply with quote
ok there some progress now.. Like you mentioned connected ground once get prompt.. and this time able to get promt working at the moment, here print env:

Quote:

Venom>> printenv
CASset=max
MALLOC_len=5
MPmode=SMP
SMT-2D=NJ2PH4401551X01
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=2
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 bootargs $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 $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_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootm $loadaddr;
bootdelay=3
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:C8:9F:88
eth1mtu=1500
eth2addr=60:38:E0:C8:9F:88
eth2mtu=1500
eth3addr=60:38:E0:C8:9F:88
eth3mtu=1500
ethact=egiga0
ethaddr=60:38:E0:C8:9F:88
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fileaddr=1000000
filesize=21E0000
firmwareName=venom.img
flash_alt_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $altKernAddr $altFwSize && nand write $defaultLoadAddr $altKernAddr $filesize
flash_pri_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $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:01:00:00
nandEcc=nfcConfig=4bitecc
nandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock6;nand read $defaultLoadAddr $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 $mtdparts_lgcy root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
update_both_images=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $priFwSize && nand erase $altKernAddr $altFwSize && nand write $defaultLoadAddr $priKernAddr $filesize && nand write $defaultLoadAddr $altKernAddr $filesize
usb0Mode=host
usbActive=0
usbType=2
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 4430/131068 bytes


following setenv silent and reset got better interface:

Quote:

Venom>> reset
resetting ...

BootROM - 1.73
Booting from NAND flash

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


U-Boot 2013.01 (May 18 2017 - 16:37:44) Marvell version: 2015_T1.QA.0p16

Boot version : v2.0.9

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


#### auto_recovery ####
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:1, boot_part:2, boot_part_ready:3

[boot_count_read] block:0x220000, size:128KB, records:64
[boot_count_read_record] boot_count:3, next_record:17

[auto_recovery_init] BOOT_COUNT_TO_RECOVERY
[boot_count_write] erase:0, auto_recovery->block_offset:0x220000 offset=0x228800

Updating boot_count ...
[boot_count_write] offset:0x228800 , length:2048
done

PCI-e 0 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0
PCI-e 1 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1
USB2.0 0: Host Mode
USB3.0 1: Host Mode
USB3.0 0: Host Mode

Map: Code: 0x1feaf000:0x1ff75960
BSS: 0x1ffef0dc
Stack: 0x1f9aef20
Heap: 0x1f9af000:0x1feaf000
U-Boot Environment: 0x00200000:0x00220000 (NAND)

Board configuration detected:
mvEthE6171SwitchBasicInit init
Net:
| port | Interface | PHY address |
|--------|-----------|--------------|
| egiga0 | RGMII | 0x01 |
| egiga1 | SGMII | 0x00 |
| egiga2 | SGMII | In-Band |
egiga0 [PRIME], egiga1, egiga2
Saving Environment to NAND...
Erasing Nand...
Writing to Nand... done
#### auto_recovery:1 ####
auto_recovery_check changes bootcmd: run nandboot
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x900000, size 0x600000
6291456 bytes read: OK
Bad Linux ARM zImage magic!
Venom>>
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 0:13    Post subject: Reply with quote
at the moment seems able to flash with factory.. not tested, but here output:

Quote:

Venom>>
Venom>> printenv ipaddr
ipaddr=192.168.1.1
Venom>> printenv serverip
serverip=192.168.1.254
Venom>> setenv serverip 192.168.1.2
Venom>> printenv serverip
serverip=192.168.1.2
Venom>> print netmask
netmask=255.255.255.0
Venom>> printenv firmwareName
firmwareName=venom.img
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'venom.img'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################
3.1 MiB/s
done
Bytes transferred = 10741760 (a3e800 hex)

NAND erase: device 0 offset 0x900000, size 0x7b00000
Erasing at 0x83e0000 -- 100% complete.
OK

NAND erase: device 0 offset 0x8400000, size 0x7b00000
Erasing at 0xfee0000 -- 100% complete.
OK

NAND write: device 0 offset 0x900000, size 0xa3e800
10741760 bytes written: OK

NAND write: device 0 offset 0x8400000, size 0xa3e800
10741760 bytes written: OK
Venom>>
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 0:18    Post subject: Reply with quote
seems not fully success yet:

get following
- Bad Linux ARM zImage magic!
- power LED still blinking

Kindly suggest what missing here or what options..
here venom.img is the current firmware (file renamed as venom.img) from linksys for WRT32x:
FW_WRT32X_1.0.180404.58.img


Quote:

Venom>> reset
resetting ...

BootROM - 1.73
Booting from NAND flash

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


U-Boot 2013.01 (May 18 2017 - 16:37:44) Marvell version: 2015_T1.QA.0p16

Boot version : v2.0.9

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


#### auto_recovery ####
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part == 1
[u_env] get boot_part_ready == 3
auto_recovery enabled:1, boot_part:1, boot_part_ready:3

[boot_count_read] block:0x220000, size:128KB, records:64
[boot_count_read_record] boot_count:1, next_record:18

[boot_count_write] erase:0, auto_recovery->block_offset:0x220000 offset=0x229000

Updating boot_count ...
[boot_count_write] offset:0x229000 , length:2048
done

PCI-e 0 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0
PCI-e 1 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1
USB2.0 0: Host Mode
USB3.0 1: Host Mode
USB3.0 0: Host Mode

Map: Code: 0x1feaf000:0x1ff75960
BSS: 0x1ffef0dc
Stack: 0x1f9aef20
Heap: 0x1f9af000:0x1feaf000
U-Boot Environment: 0x00200000:0x00220000 (NAND)

Board configuration detected:
mvEthE6171SwitchBasicInit init
Net:
| port | Interface | PHY address |
|--------|-----------|--------------|
| egiga0 | RGMII | 0x01 |
| egiga1 | SGMII | 0x00 |
| egiga2 | SGMII | In-Band |
egiga0 [PRIME], egiga1, egiga2
auto_recovery_check changes bootcmd: run nandboot
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x900000, size 0x600000
6291456 bytes read: OK
Bad Linux ARM zImage magic!
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3910

PostPosted: Mon Jan 17, 2022 0:20    Post subject: Reply with quote
flat-FW_WRT32X_1.0.180404.58.img rename this to venom.img
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 0:21    Post subject: Reply with quote
just o be sure what the difference with the file from linksys vs the one you have listed above?
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3910

PostPosted: Mon Jan 17, 2022 0:29    Post subject: Reply with quote
It is a flat file for serial flash recovery or official linksys wrt32x firmware properly converted by adi-brasov.

What is downloaded from linksys is not usable, only for openwrt sysupgrade. Work is already done for you.
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 0:36    Post subject: Reply with quote
ok look like that did the trick:

Will post more detail on steps, but at this point router boot and able to connect with webgui..

@blkt Any recommendation for best firmware option for WRT32x or similar router that give fast speed option for openvpn?
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 3:45    Post subject: Reply with quote
ok, here something off:

1) Can connect to router over wifi, but router fail to connect to internet.

2) tried to even reinstall factory firmware downloaded from linksys, it refuse it firmware failed to check and not install.

3) Router not able to reset even with reset button 10 sec press.

Issue: At this point not able to use router to connect to internet.

Able to ssh into it, any pointer what next can try:

Quote:
root@192.168.10.1's password:


BusyBox v1.24.2 () built-in shell (ash)

_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
DESIGNATED DRIVER (Bleeding Edge, 50140)
-----------------------------------------------------
* 2 oz. Orange Juice Combine all juices in a
* 2 oz. Pineapple Juice tall glass filled with
* 2 oz. Grapefruit Juice ice, stir well.
* 2 oz. Cranberry Juice
-----------------------------------------------------
root@netgateway:~# ls
root@netgateway:~# pwd
/root
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Mon Jan 17, 2022 18:12    Post subject: Reply with quote
as last resort:
- downloaded factory OEM version from linksys
- scp to the router
-installed with sysupgrade

sysupgrade -n -v /tmp/<firmwarefile>

and it finally working like it was before putting DDWRT.
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3910

PostPosted: Mon Jan 17, 2022 18:30    Post subject: Reply with quote
There is nothing wrong with that flat file for venom u-boot serial flash, also resulting installs are the same.

https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset <- This was only needed.

The reason sysupgrade works is because sysupgrade -n = do not save configuration over reflash, so reset.

Recommendation will always be a current build as of today for Marvell is New Build - 01/17/2022 - r48138.
chirkoot1
DD-WRT Novice


Joined: 16 Jan 2022
Posts: 15

PostPosted: Thu Jan 20, 2022 4:35    Post subject: Reply with quote
Why it so difficult to revert back from DDWRT to OEM?
Gameman Advanced Kid
DD-WRT Guru


Joined: 18 Nov 2012
Posts: 1048

PostPosted: Thu Jan 20, 2022 7:12    Post subject: Reply with quote
Its easy with some routers and hard with others.

Netgear is by, arguably, the EASIEST to flash to and from stock to dd-wrt and then back.

Linksys newer routers from what I have seen have made things a bit harder. Not sure what to say about the WRT series as I purposefully flashed both partitions and am definitely not going back to stock firmware.

But again, your mileage may, and the keyword here is "may", greatly vary.

_________________
For people who are new to the dd-wrt forums >> http://www.catb.org/~esr/faqs/smart-questions.html#rtfm

barryware wrote:
It takes a "community" to raise a router..


Internet Connection 1
Gateway Router > Linksys WRT32x

Internet connection 2
NAS-AP > Netgear Nighthawk R7800

DD-WRT non-official LIVE element/matrix chat

https://matrix.to/#/#dd-wrt_non_official:matrix.org
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 3910

PostPosted: Thu Jan 20, 2022 18:00    Post subject: Reply with quote
Linksys supplies only sysupgrade files for WRT32X, so a few good community people created workarounds.
One is compiled from GPL source by inteliboy, another is converted directly from sysupgrade by adi-brasov.

Marvell WRT series opted for dual partition failover instead of easy to recover TFTP, so serial recovery only.
DD-WRT configuration is not compatible with OpenWrt. Reset after entering any new firmware environment.

If you read the Marvell stickies, there is another way to go back to stock directly from DD-WRT Telnet/SSH.
But, if you choose the wrong file or mess up command syntax, typo etc. might need to switch boot partition
with the power toggle failover method. If you corrupt both firmware partitions only option is serial recovery.
Goto page Previous  1, 2 Display posts from previous:    Page 2 of 2
Post new topic   Reply to topic    DD-WRT Forum 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