Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WRT3200ACM corrupt bootloader recovery? #110

Closed
panda-mute opened this issue Jun 9, 2017 · 8 comments
Closed

WRT3200ACM corrupt bootloader recovery? #110

panda-mute opened this issue Jun 9, 2017 · 8 comments

Comments

@panda-mute
Copy link

https://github.com/Chadster766/McWRT/wiki/WRT1900AC-corrupt-bootloader-recovery not work in WRT3200ACM.
Is there any method to reflash uboot of WRT3200ACM?

@Chadster766
Copy link
Owner

Follow the instruction in the below link in the Armada 385 tabs:

https://wiki.openwrt.org/toh/linksys/wrt_ac_series#corrupt_environment_recovery

@panda-mute
Copy link
Author

I have try to follow the instruction:
./kwboot -t /dev/ttyUSB0 -b u-boot-a38x-spi-uart.bin -d
Sending debug message. Please reboot the target.../
Sending boot image...

Booting from NAND flash

mvBoardIdGet: TWSI Read for Marvell Board ID failed (57)
Using default board ID

General initialization - Version: 1.0.0
mvSysEnvIsFlavourReduced: TWSI Read of 'flavor' failed
Detected Device ID 6820
High speed PHY - Version: 2.0

Initialize DB-88F6820-BP board topology

Init DB board default topology
Device 6810/20 supports only 2 SATA interfaces: SATA Port 3 @ lane3 disabled
updateTopologySatR: TWSI Read of 'dbserdes1/2' failed
board SerDes lanes topology details:
| Lane # | Speed | Type |

| 0 | 03 | SATA0 |
| 1 | 05 | PCIe0 |
| 2 | 05 | PCIe1 |
| 4 | 05 | USB3 HOST0 |
| 5 | 05 | USB3 HOST1 |

:** Link is Gen1, check the EP capability
PCIe, Idx 0: Link upgraded to Gen2 based on client cpabilities
PCIe, Idx 1: detected no link
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.32.0
mvSysEnvGetTopologyUpdateInfo: TWSI Read failed
0 % [+xmodem: Protocol error

It seems the device not into uart boot stage? How to trigger the uart boot?

@Chadster766
Copy link
Owner

Chadster766 commented Jun 12, 2017

Try "./kwboot -t /dev/ttyUSB0 -b u-boot-a38x-spi-uart.bin " instead

@panda-mute
Copy link
Author

Sorry I don't have Skype now.

Try as your advice:
Sending boot message. Please reboot the target...|
Sending boot image...
0 % [+++++++++++++++++xmodem: Bad message

Is there any help for this message?

@Chadster766
Copy link
Owner

That looks good but it fails in the middle of the uart transfer.

Check you TTL leads are connecting well.

@panda-mute
Copy link
Author

The TTL connection is well, because it is working with another WRT3200ACM(input and output).
Anyway I change to another TTL to USB cable, the boot is hang, no uboot printout.
So can you advice which TTL to USB cable is work in WRT3200ACM?

@Chadster766
Copy link
Owner

I've asked the expert on this process to help with your boot loader recovery:

https://github.com/nitroshift/armada-38x-bootloader-recovery-files/issues/1

@sirentatsina
Copy link

panda-mute

have you solved the "WRT3200ACM corrupt bootloader recovery" yet?
Few days ago, I met the same problem.
Could you please tell me the solution?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants