From: Dilyan Lazarov <dilianl@gmail.com>
To: u-boot@lists.denx.de
Subject: linksys wrt1900acs v2 boot problem
Date: Tue, 28 Sep 2021 22:01:40 +0300 [thread overview]
Message-ID: <CAAYUfvHJegq8Qwyqk5RdErkBkkYvj1HZXaOSodRZuOW8izs36A@mail.gmail.com> (raw)
Hi,
I have a problem with my linksys wrt1900acs.
My main question is this a hardware problem or software problem?
Is it possible to address?
I have started researching and have tried with "kwboot" under Windows VM -
Ubuntu 20 - Linux but I have a problem with usb serial connection. I have
tried several things but I understand that it isn't possible to start USB
to Serial on a Windows VM.
I will expect your response.
Thank you in advance.
All the best
Dilyan
I see the following Log from U-Boot with PuTTy under Windows 10:
BootROM - 1.73
Booting from NAND flash
General initialization - Version: 1.0.0
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 | 06 | SATA0 |
| 1 | 05 | PCIe0 |
| 2 | 06 | SATA1 |
| 3 | 05 | USB3 HOST1 |
| 4 | 05 | PCIe1 |
| 5 | 00 | 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.26.0
mvSysEnvGetTopologyUpdateInfo: TWSI Read failed
WL Supp: IF 0 busId 1 Failed !
WL Supp: IF 0 failed
ddr3TipDynamicWriteLevelingSupp failure
******** DRAM initialization Failed (res 0x1) ********
DDR3 run algorithm - FAILED 0x1
DDR3 Training Sequence - FAILED
********** DRAM initialization failed! ********
--
Dilyan
next reply other threads:[~2021-09-28 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:01 Dilyan Lazarov [this message]
2023-01-06 17:35 ` linksys wrt1900acs v2 boot problem Pali Rohár
2023-01-06 23:06 ` Tony Dinh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAYUfvHJegq8Qwyqk5RdErkBkkYvj1HZXaOSodRZuOW8izs36A@mail.gmail.com \
--to=dilianl@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).