From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: Debugging VoCore2 ROM Startup
Date: Wed, 15 Jan 2020 11:48:25 +0100 [thread overview]
Message-ID: <76d66b59-5ace-05eb-3c64-a26a3ee1cba2@denx.de> (raw)
In-Reply-To: <33722d0a-db31-5b52-d0eb-1c169c6aad80@mclink.it>
Hi Mauro,
On 15.01.20 11:23, Mauro Condarelli wrote:
>>> I am surprised though as all I could find on differences between
>>> MT7628 and MT7688 are is a reference on Mediatek site:
>>> https://docs.labs.mediatek.com/resource/linkit-smart-7688/en/faq
>>>
>>> Q: What’s MT7628 and how is it different from MT7688AN?
>>>
>>> The MT7628 series are pin-to-pin compatible with the MT7688 series.
>>> However, MT7628 comes with a 2T2R antenna, while MT7688 only supports
>>> 1T1R antenna.
>>>
>>> (Incomplete!) comparison of the two datasheets did not show
>>> relevant differences.
> I have started an analysis of current register status (and I quickly hit
> limitation of the documentation I have):
>
> b0000008: 00010000 ....
> E-Fuse Configuration is not pristine, but I don't know what it my mean.
>
> b0000010: 00111144 D...
> System Configuration Register 0 ->0000 0000 0001 0001 0001 0001 1000 1000
Not correct:
System Configuration Register 0 ->0000 0000 0001 0001 0001 0001 0100 0100
>
> 00000000 TEST_CODE
> 000 *
> 100010001 BS_SHADOW
> 000 *
> 1 DBG_JTAG_MODE 1: Normal Boot-up
> 1 TEST_MODE_1 ??
> 0 XTAL_FREQ_SEL 0: 25MHz DIP ???
> 0 EXT_BG 0: BG clock from PMU
> 0 TEST_MODE_0 0: SUTIF
> 100 CHIP_MODE 100: SCAN mode
Not correct. You have here 010, so XTAL with 3-byte ADR
> 0 DRAM_TYPE 0: DDR2
>
> I am concerned by TEST_MODE_1,XTAL_FREQ_SEL and CHIP_MODE that might
> signal a different up/down pulling of Bootstrapping Pins.
> Could You cross check on LinkIt, please?
=> md b0000000
b0000000: 3637544d 20203832 00100000 00010102 MT7628 ........
b0000010: 00156156 02605500 00000000 00000000 Va...U`.........
b0000020: 10240000 00000000 00000071 0020100c ..$.....q..... .
b0000030: ffffffc0 04000000 c0030004 00fe00ff ................
b0000040: 00000000 0001ffff 00000000 00000000 ................
b0000050: 00000000 00000000 00000000 00000810 ................
b0000060: 50050404 05550551 00000000 00000000 ...PQ.U.........
SYSCFG0: 00156156
CHIP_MODE: 011: XTAL with 4-byte ADR.
Mainline U-Boot reports this:
CPU: MT7628 Rev 1.2 - Boot from XTAL (4-Byte SPI Addr)
and the new code from Weijie reports this:
CPU: MediaTek MT7688A ver:1 eco:2
Boot: DDR2, SPI-NOR 4-Byte Addr, CPU clock from XTAL
Clock: CPU: 580MHz, Bus: 193MHz, XTAL: 40MHz
One important difference which might explain a lot, it XTAL_FREQ_SEL
which is 0 in your case and 1 in my case.
IIUTC, then the new code from Weijie takes this XTAL selection
into account. Weijie might comment on this. I suggest that you give
this "u-boot-mtmips.bin" binary a try. Good luck. :)
Thanks,
Stefan
next prev parent reply other threads:[~2020-01-15 10:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 17:28 How to debug HW startup? Mauro Condarelli
2020-01-10 6:31 ` Stefan Roese
2020-01-10 9:06 ` Mauro Condarelli
2020-01-10 13:33 ` Stefan Roese
2020-01-11 19:00 ` Mauro Condarelli
2020-01-11 20:42 ` Sean Anderson
2020-01-11 21:38 ` Mauro Condarelli
2020-01-11 23:58 ` Sean Anderson
2020-01-12 0:22 ` Mauro Condarelli
2020-01-13 6:53 ` Stefan Roese
2020-01-13 10:24 ` Mauro Condarelli
2020-01-13 11:39 ` Stefan Roese
2020-01-13 12:24 ` Mauro Condarelli
2020-01-13 12:45 ` Stefan Roese
2020-01-13 14:14 ` Mauro Condarelli
2020-01-13 23:08 ` Mauro Condarelli
2020-01-14 11:03 ` Mauro Condarelli
2020-01-14 23:55 ` Debugging VoCore2 ROM Startup (was: How to debug HW startup?) Mauro Condarelli
2020-01-15 7:25 ` Debugging VoCore2 ROM Startup Stefan Roese
2020-01-15 9:04 ` Mauro Condarelli
2020-01-15 9:31 ` Stefan Roese
2020-01-15 9:51 ` Stefan Roese
2020-01-15 10:23 ` Mauro Condarelli
2020-01-15 10:48 ` Stefan Roese [this message]
2020-01-15 12:50 ` Mauro Condarelli
2020-01-15 15:04 ` Stefan Roese
2020-01-15 15:55 ` Mauro Condarelli
2020-01-15 16:20 ` Stefan Roese
2020-01-15 17:25 ` Mauro Condarelli
2020-01-16 6:33 ` Stefan Roese
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=76d66b59-5ace-05eb-3c64-a26a3ee1cba2@denx.de \
--to=sr@denx.de \
--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.