From: Brice GIBOUDEAU <brice@pingus.org>
To: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: AP152 & TP-Link Archer C7
Date: Wed, 16 Mar 2022 08:09:48 +0000 [thread overview]
Message-ID: <1647418089408.87882@pingus.org> (raw)
In-Reply-To: <1647417788025.73815@pingus.org>
?Hello,
As I need to modify the boot environment I need to upgrade the fairly old Uboot-1.1.4 that you find on those quite popular device TP-Link Archer C7 (version 5 in my case).
After investigations I found that you have a support for the AP152 that is the base of that router. I just changed few things to enable the proper boot address and Ethernet support.
U-Boot work well but twhen OpenWRT boot it crash with random characters on the console during the PIEe initialization.
Did I missed something ? (a variabe to set somewhere ?) I added debug info below.
Regards,
MiNuS_89
?--------
Below the last line of the boot log from the console that show the issue.
[ 1.770010] 8021q: 802.1Q VLAN Support v1.8
[ 1.775142] PCI host bridge /ahb/pcie-controller@18250000 ranges:
[ 1.781508] MEM 0x0000000012000000..0x0000000013ffffff
[ 1.786923] IO 0x0000000000000000..0x0000000000000000
[[ 1.998826] rr724x-pci11825000..pcie-cnntrolee:: PCIe iink is oonn
244244 P htt iiggeoo ss 0::0
[[ .86557]ci_s 00:0: N bsnesurc fun fo rt us wl uee[b 00ff [ 2.884066pccbus 0000::rt s ssor [[mm 12000000x11fffff
[[ .8874] ctoys uabl toopen tc evic (rt0) 28758] pi_s 00:0 bsn_re [bs 0-f] d s pdtedto00
---------
My U-Boot version: U-Boot 2022.04-rc4 (Mar 15 2022 - 16:56:25 +0100)
---------
I cross compiled it with the OpenWRT SDK: openwrt-sdk-21.02.2-ath79-generic_gcc-8.4.0_musl.Linux-x86_64
--------
I'm booting OpenWRT 21.02.2 and it boot correctly with the original U-Boot that I recovered a couple of time to investigate.
parent reply other threads:[~2022-03-16 13:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1647417788025.73815@pingus.org>]
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=1647418089408.87882@pingus.org \
--to=brice@pingus.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.