From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Lars Pedersen <lapeddk@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Getting serial console output on new imx7d tqma7 board UART4
Date: Thu, 30 Jul 2020 09:25:26 +0200 [thread overview]
Message-ID: <ce3df13a-29aa-809f-f39c-1213da23038e@pengutronix.de> (raw)
In-Reply-To: <CAKd8=GvjdkC=mHYq3LpLwtaSi8WhYsn3e1VphTWefbzpq=_ZFA@mail.gmail.com>
On 7/30/20 8:58 AM, Lars Pedersen wrote:
> The DCD part now matches exactly for the top part (00000000 to
> 00000020) of it which i guess is the IVT header, which shouldn't be
> the same?
I mean the memory calibration and such. Not that your U-Boot port
does something in C code, which you are missing in your barebox
DCD.
>
> The following is xxd where barebox (left side) has been shifted 0x400
> to match u-boot part.
>
> /usr/bin/diff -y <(xxd barebox_stripped) <(xxd uboot_stripped)
I don't understand how to read this diff.
> So I guess that the DCD table part now should be correct. So the
> question is if this is and lowlevel.c/board.c boilerplate issue or
> maybe I need something in the Kconfig menu.
Enable CONFIG_DEBUG_LL and see how far barebox comes.
See the inline comment from my last mail.
>>> +
>>> +static inline void setup_uart(void)
>>> +{
>>> + imx7_early_setup_uart_clock();
>>> +
>>> + imx7_setup_pad(MX7D_PAD_SAI2_TX_BCLK__UART4_DCE_TX);
>>> +
>>> + imx7_uart_setup_ll();
>>> +
>>> + putc_ll('>');
>>
>> You've CONFIG_DEBUG_LL=y and you choose the correct UART port
>> in the i.MX menuconfig option?
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-07-30 7:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:52 Lars Pedersen
2020-07-29 17:22 ` Ahmad Fatoum
2020-07-30 6:58 ` Lars Pedersen
2020-07-30 7:25 ` Ahmad Fatoum [this message]
2020-07-30 10:16 ` Lars Pedersen
2020-07-30 13:55 ` Ahmad Fatoum
2020-08-03 7:56 ` Lars Pedersen
2020-08-03 21:51 ` Sascha Hauer
2020-08-04 12:53 ` Lars Pedersen
2020-08-03 10:10 ` Ahmad Fatoum
2020-08-04 13:07 ` Lars Pedersen
2020-08-04 16:15 ` Ahmad Fatoum
2020-08-04 19:21 ` Lars Pedersen
2020-08-05 8:49 ` Ahmad Fatoum
2020-08-05 9:37 ` Lars Pedersen
2020-08-05 9:48 ` Ahmad Fatoum
2020-08-05 11:12 ` Lars Pedersen
2020-08-05 12:30 ` Ahmad Fatoum
2020-08-05 15:00 ` Lars Pedersen
2020-08-10 8:00 ` Sascha Hauer
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=ce3df13a-29aa-809f-f39c-1213da23038e@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=lapeddk@gmail.com \
/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