WRT32x Bricked - Is There Any Hope?

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


Joined: 03 Nov 2016
Posts: 25

PostPosted: Wed Mar 15, 2023 17:50    Post subject: WRT32x Bricked - Is There Any Hope? Reply with quote
Had DD-WRT installed on one partition of a WRT32x. Tried to install OpenWRT on the other partition and it bricked it.

Picked up a TTL cable and followed the various instructions found here and elsewhere but not getting any results.

Here's a video of what's happening or not happening in this case.
https://youtu.be/FmdNxL3kvpU

The power light flashes when the TTL is not connected. As soon as the ground wire (black) makes contact, the light goes out. The only light is the ethernet port 1.

Is there anything at this point or is it a door stop?
Sponsor
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Wed Mar 15, 2023 18:36    Post subject: Reply with quote
Did you try the 3x power cycle trick to see if it will boot back to DD-WRT / the other partition?

WRT32X DD-WRT Installation Procedure

[SOLVED] WRT32X back to stock Firmware

_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Wed Mar 15, 2023 19:09    Post subject: Reply with quote
Yes, did the triple power recycle as power on, power light goes off, power off which is supposed to switch boot partitions iirc. Nothing.

Quite sure I read through that thread already but I'll read again.

The thing is not responsive. No IP, no SSH or Telnet, and TTL isn't responding.


dale_gribble39 wrote:
Did you try the 3x power cycle trick to see if it will boot back to DD-WRT / the other partition?

WRT32X DD-WRT Installation Procedure

[SOLVED] WRT32X back to stock Firmware
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14126
Location: Texas, USA

PostPosted: Wed Mar 15, 2023 20:09    Post subject: Reply with quote
It's been a hot minute since I did serial on one of my 3200s, but it's the same header on all WRT AC series. Remember, the TX on the router end goes to the RX on the USB UART TTL adapter and the RX on the router end goes to the TX on the USB UART TTL adapter. These things are s'posed to be recoverable, but I am not sure how OpenWRT flashes from factory. If you've overwritten u-boot or something extreme...

https://openwrt.org/toh/linksys/wrt32x#serial1

https://openwrt.org/toh/linksys/wrt_ac_series#serial_port (continue reading below this point about bootloader recovery, etc. if necessary)

https://forum.openwrt.org/t/bricked-wrt32x/27329/

https://github.com/Chadster766/McDebian/wiki/1.-USB-to-TTL-Serial-Connection

https://github.com/Chadster766/McDebian/wiki/C.-U%E2%80%90Boot-Recovery

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Wed Mar 15, 2023 23:19    Post subject: Reply with quote
Thank you everyone for the responses.

kernel-panic69
Sometimes one thing sparks a chain of thoughts that lead to a solution.

Turns out the the TX and RX wires are reversed on the cable I bought compared to the videos I had watched. The three videos I watched were all much the same, on the router, Pin 1 Black Gnd, Pin 2 White Lead TX, Pin 4 Green Lead RX. My cable TX and RX are reversed so, TX is Green and RX is White.

I hooked up that way and I have access via Putty. Yay!

Now I have to determine best flash to get this sorted out.


kernel-panic69 wrote:
It's been a hot minute since I did serial on one of my 3200s, but it's the same header on all WRT AC series. Remember, the TX on the router end goes to the RX on the USB UART TTL adapter and the RX on the router end goes to the TX on the USB UART TTL adapter. These things are s'posed to be recoverable, but I am not sure how OpenWRT flashes from factory. If you've overwritten u-boot or something extreme...

https://openwrt.org/toh/linksys/wrt32x#serial1

https://openwrt.org/toh/linksys/wrt_ac_series#serial_port (continue reading below this point about bootloader recovery, etc. if necessary)

https://forum.openwrt.org/t/bricked-wrt32x/27329/

https://github.com/Chadster766/McDebian/wiki/1.-USB-to-TTL-Serial-Connection

https://github.com/Chadster766/McDebian/wiki/C.-U%E2%80%90Boot-Recovery
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14126
Location: Texas, USA

PostPosted: Thu Mar 16, 2023 2:59    Post subject: Reply with quote
Things happen, although usually the color-coding doesn't change that I've noticed, but I could be oblivious to such things at times Rolling Eyes

You should be able to at least recover to stock firmware and proceed from there. I would pick which 3rd party firmware to use and stick with it - I wouldn't bother with trying to have DD-WRT and OpenWRT (or stock) co-exist.

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Thu Mar 16, 2023 18:18    Post subject: Reply with quote
Well, he thing is hung here;

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

^^^is where is stops.


Not sure what to do here.

Looked at this;
https://github.com/ValCher1961/McDebian_WRT3200ACM/tree/master/recovery-uboot

and this

https://github.com/ValCher1961/McDebian_WRT3200ACM/tree/master/recovery-uboot

... And about 1000 other things.

As well, several solutions ASSUME you have SSH and there isn't in this state and those are among the 'prescribed' solutions.

Then there's the VENOM Flat image stuff that's supposed to be the path back to factory. Reluctant to try for fear of potentially making it worse.

If I get pointed in a direction and I'll always figure it out. I'm a master searcher and find most everything I ever need to learn.

Finding the actual solution for this stuff is convoluted as F$%@!

Like someone else mentioned, there so many posts, with so many varied experiences and results, nearly no two things are the same, and your head starts to spin. You don't want to try anything for fear of making it worse.

i.e. Even in the examples above, there's no explanation of getting kwboot to actually function. Sure, copy it to a folder and run it. linux doesn't work that way. 24 hours later, a headache, no sleep, sore eyes and no further ahead. I grew up with CLI on Amiga Unix and linux is still a pain in the arse.
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 5660

PostPosted: Thu Mar 16, 2023 18:21    Post subject: Reply with quote
WRT32X silent boot is enabled, so it will not tell you to "press any key" or any indication to interrupt boot process.

BTW if you did not overwrite both partitions triple power toggle to switch partitions should still be an option YMMV.

Power ON and when LAN LED is blinking immediately turn it OFF then wait at least three seconds, repeat.
Then power it on a third time and let it run.

Another visual cue is power LED blinks a few times then turns off for about 2 seconds, switch power OFF.

flat-FW_WRT32X_1.0.180404.58.img <--- rename venom.img and yes this is correct file for serial flash.
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Thu Mar 16, 2023 20:25    Post subject: Reply with quote
I'm 98% sure I overwrote both partitions. Tried the power toggle thing. It worked until I bricked this thing.

I'm quite certain I tried that file but will give it another go.

I did see a post (maybe yours) about silent mode and will try that again as well.


blkt wrote:
WRT32X silent boot is enabled, so it will not tell you to "press any key" or any indication to interrupt boot process.

BTW if you did not overwrite both partitions triple power toggle to switch partitions should still be an option YMMV.

Power ON and when LAN LED is blinking immediately turn it OFF then wait at least three seconds, repeat.
Then power it on a third time and let it run.

Another visual cue is power LED blinks a few times then turns off for about 2 seconds, switch power OFF.

flat-FW_WRT32X_1.0.180404.58.img <--- rename venom.img and yes this is correct file for serial flash.
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Thu Mar 16, 2023 23:55    Post subject: Reply with quote
Well, since I likely don't have much to lose at this point, I tried this;

https://forum.openwrt.org/t/stock-firmware-of-wrt3200acm-on-wrt32x/40653/15?page=2
* I used the files for the 32x not the ACM first and I finally got a Venom prompt
** I also tried the wrt3200acm that some have done and I got a Marvell prompt

and this;

https://github.com/ValCher1961/McDebian_WRT3200ACM/tree/master/recovery-uboot
* I used the files for the 32x not the ACM

and this;

https://github.com/Chadster766/McDebian/wiki/C.-U%E2%80%90Boot-Recovery
* This one I did the PC version with TFTPD and Putty instead of Tera Term and I also did kwboot from linux.

All of these things at least got the thing booting but I either end up with 5 second or 1 second reboot loops or I get a Bad Linux ARM zImage magic!
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Fri Mar 17, 2023 0:33    Post subject: Reply with quote
Printenv;

Marvell>> printenv
CASset=max
MALLOC_len=5
MPmode=SMP
altFwSize=0x5000000
altKernAddr=0x5a00000
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=console=ttyS0,115200 root=/dev/mtdblock6
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:C7:B3:A8
eth1mtu=1500
eth2addr=60:38:E0:C7:B3:A8
eth2mtu=1500
eth3addr=60:38:E0:C7:B3:A8
eth3mtu=1500
ethact=egiga0
ethaddr=60:38:E0:C7:B3:A8
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
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=/
imageName=rango.img
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
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:20:19: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
pcieTune=no
pexMode=RC
priFwSize=0x5000000
priKernAddr=0x0a00000
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.2
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: 4375/131068 bytes
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14126
Location: Texas, USA

PostPosted: Fri Mar 17, 2023 2:17    Post subject: Reply with quote
Your prompt should be Venom. Or use the files for 3200ACM, but I'd advise reverting back to Venom.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Fri Mar 17, 2023 3:17    Post subject: Reply with quote
I tried both the 3200acm and wrt32x. Here's the printenv for the WRT32x;

Venom>> printenv
CASset=max
MALLOC_len=5
MPmode=SMP
altFwSize=0x5000000
altKernAddr=0x5a00000
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=console=ttyS0,115200 root=/dev/mtdblock6
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:C7:B3:A8
eth1mtu=1500
eth2addr=60:38:E0:C7:B3:A8
eth2mtu=1500
eth3addr=60:38:E0:C7:B3:A8
eth3mtu=1500
ethact=egiga0
ethaddr=60:38:E0:C7:B3:A8
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
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=/
imageName=venomflat.img
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
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:20:19: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
pcieTune=no
pexMode=RC
priFwSize=0x5000000
priKernAddr=0x0a00000
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.2
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
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 5660

PostPosted: Fri Mar 17, 2023 6:16    Post subject: Reply with quote
GDTech wrote:
Well, since I likely don't have much to lose at this point, I tried this;
Major fail x 3. All you had to do was power on, press keyboard keys to interrupt boot process for a venom prompt.
Now you will have to restore u-boot to WRT32X, also hope you made printenv backup before making any changes.

Help required Please on Linksys WRT32X not booting

wrt32x uboot firmware flash help pls

Bricked WRT32X

WRT 32X Bricked but unable to boot into firmware

Wr32x corrupt bootloader recovery [kwboot won't work]

Flash WRT32X with WRT3200ACM to help revert a mess

wrt32x bricked!!

Serial number on DD-WRT UI - WRT32X

Original firmware
GDTech
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 25

PostPosted: Sat Mar 18, 2023 6:53    Post subject: Reply with quote
I figured it out.

So, attached is a photo of my WRT32x as itself.

There's a second photo of my WRT32x now running as a WRT3200ACM.

Most of the U-Boot recovery tutorials posted here and elsewhere all reference the same 0x200000 or 0x2000000 address references as write 'destinations'. Each attempt I made, everything responded as it should, erasures and writes were showing successful but it wasn't working. I then found one other reference with a some different and extra commands, along with a different write to address. That is what got it working. I understand what it was doing, I just haven't been able to find the answer as to why the particular address is chosen or used.

Either way, it booted up as a WRT32x. I know what it did and does and the other set of files for the WRT3200ACM are no different in that they program the same hardware in a different way.

It reminds me of SmartCards, Free To Air, that kind of thing. You are instructing the environment to load a binary or program to an address or address range. Then you make a call to write/install that to another location or with smart cards and that kind of thing, you can also run small bits of program code.

I've put the device back to WRT32x and I'll likely put a DD-WRT on Partition 2. For most purposes, the WRT32x does what one needs. The Wi-Fi is solid, at least in my experience. I do not have a bone stock 32x to compare so I don't know if the Venom Flat image made any changes but I can SSH into the factory 'stock' router at this point.

With my stock 3200ACM, I cannot.

With the 32x, I like the apparent ability to SSH in either way so I can Putty in, change my boot partition, reboot and bounce back and forth between factory and DD-WRT as I choose or need.


Last edited by GDTech on Sat Mar 18, 2023 9:07; edited 2 times in total
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
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